Transfering bugs/writespeeds

[andershb]

Hi guys!

So, I'm having a annoying problem. I have a freenas system running as a plain fileserver setup in ZFS, where all my media .R3D footage and other footage is archived.
PS; Yes, I know redundency, yes i know everything can crash etc but I have external drives for each project I'm doing, so no matter what I won't be able to loose the material. The freenas works more as a "Do you have that file?" and I can grab it quickly and export it kindof thing.

Anyhow.. I'm experiencing some trouble when transfering files to the NAS system.

When I'm transfering each .RDM folder (that in the end is around 128gb pr folder) with clips consists from 40mb to ~3gb, I get an network error:
Error 0x8007003B: An unexpected network error occured.

My transfer speeds lies around 100mb/s in the begining, then dropping to around 40mb/s, then up again, and then down again to around 10mb/s or lower, then I get prompet with the "try again" button. When I click try again, it just continues with the transfering like nothing have happend, goes on for a minute or two, or sometimes more, then I get prompet with that window again.

I see my disk usage corrolates with when the drops are happening, seems like the disks kindof fall to sleep.

My freenas system:
AMD Phenom X4 955 4cores
14GB of memory
8TB or so ZFS pool where the four disks are together in ONE pool using vdisk
External NIC card (I think it's intel)

I've tried searching for the similar problem, but nothing seems to work. For me it seems like I'm filling up either RAM or similar and it's just too much for the ram or drives or something.

Right now I'm transfering a 128gb project, and it didnt happen the first 5 minutes, then it happend kindof every 2-3 min, and right now as I'm writing this it has been stable for 10 minutes at 113mb/s and no errors.

If anything is unclear, I will try my best to provide more info or explain..

Best regards

 

[Chris Moore]

External NIC card (I think it's intel)

This matters, especcialy when the error you are having is a network error. Also, what model system board is it?

The problem you are describing sounds like a hardware problem. It is just a matter of determining the cause. What kind of disks are they, brand and model, and if you could share the output of the command zpool status it might help isolate the problem.
That should look like this:

Code:

  pool: Backup
state: ONLINE
status: One or more devices is currently being resilvered.  The pool will
    continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
  scan: resilver in progress since Sat Mar  9 08:30:11 2019
    8.98T scanned at 2.35G/s, 4.70T issued at 1.41G/s, 15.7T total
    56.2G resilvered, 29.88% done, 0 days 02:13:15 to go
config:

    NAME                                            STATE     READ WRITE CKSUM
    Backup                                          ONLINE       0     0     0
      raidz1-0                                      ONLINE       0     0     0
        gptid/2e919d3d-2c1a-11e9-af8b-00074306773b  ONLINE       0     0     0
        gptid/2f292da6-2c1a-11e9-af8b-00074306773b  ONLINE       0     0     0
        gptid/2fb95d07-2c1a-11e9-af8b-00074306773b  ONLINE       0     0     0
        gptid/30514e6b-2c1a-11e9-af8b-00074306773b  ONLINE       0     0     0
      raidz1-1                                      ONLINE       0     0     0
        gptid/41d3312f-2c1a-11e9-af8b-00074306773b  ONLINE       0     0     0
        gptid/426b7b47-2c1a-11e9-af8b-00074306773b  ONLINE       0     0     0
        gptid/43029d18-2c1a-11e9-af8b-00074306773b  ONLINE       0     0     0
        gptid/af54c9c6-4277-11e9-af8b-00074306773b  ONLINE       0     0     0  (resilvering)

errors: No known data errors

You could even have a faulty disk as that will slow everything down while the faulty disk retries to complete the task.

 

[andershb]

This matters, especcialy when the error you are having is a network error. Also, what model system board is it?

The problem you are describing sounds like a hardware problem. It is just a matter of determining the cause. What kind of disks are they, brand and model, and if you could share the output of the command zpool status it might help isolate the problem.
That should look like this:

Code:

  pool: Backup
state: ONLINE
status: One or more devices is currently being resilvered.  The pool will
    continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
  scan: resilver in progress since Sat Mar  9 08:30:11 2019
    8.98T scanned at 2.35G/s, 4.70T issued at 1.41G/s, 15.7T total
    56.2G resilvered, 29.88% done, 0 days 02:13:15 to go
config:

    NAME                                            STATE     READ WRITE CKSUM
    Backup                                          ONLINE       0     0     0
      raidz1-0                                      ONLINE       0     0     0
        gptid/2e919d3d-2c1a-11e9-af8b-00074306773b  ONLINE       0     0     0
        gptid/2f292da6-2c1a-11e9-af8b-00074306773b  ONLINE       0     0     0
        gptid/2fb95d07-2c1a-11e9-af8b-00074306773b  ONLINE       0     0     0
        gptid/30514e6b-2c1a-11e9-af8b-00074306773b  ONLINE       0     0     0
      raidz1-1                                      ONLINE       0     0     0
        gptid/41d3312f-2c1a-11e9-af8b-00074306773b  ONLINE       0     0     0
        gptid/426b7b47-2c1a-11e9-af8b-00074306773b  ONLINE       0     0     0
        gptid/43029d18-2c1a-11e9-af8b-00074306773b  ONLINE       0     0     0
        gptid/af54c9c6-4277-11e9-af8b-00074306773b  ONLINE       0     0     0  (resilvering)

errors: No known data errors

You could even have

Thanks for the quick reply!

If you meant mobo: Gigabyte GA-MA790XT-UD4P, Socket-AM3
The NIC: TP-LINK TG-3468 PCIe Gigabit Adapter
Harddrives: Seagate Barracuda

Code:

root@freenas:~ # zpool status
  pool: filserver
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
        still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.
  scan: scrub repaired 0 in 0 days 01:48:16 with 0 errors on Sun Feb 10 01:48:17 2019
config:

        NAME                                          STATE     READ WRITE CKSUM
        filserver                                     ONLINE       0     0     0
          gptid/e1141c7a-f91b-11e6-b8fd-7071bc604152  ONLINE       0     0     0

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:07:36 with 0 errors on Thu Mar  7 03:52:36 2019
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          da0p2     ONLINE       0     0     0

errors: No known data errors

  pool: usett
 state: ONLINE
  scan: none requested
config:

        NAME                                          STATE     READ WRITE CKSUM
        usett                                         ONLINE       0     0     0
          gptid/fd74c6ba-32d1-11e9-b280-503eaa06a7ea  ONLINE       0     0     0
          gptid/01e037db-32d2-11e9-b280-503eaa06a7ea  ONLINE       0     0     0
          gptid/052fcb74-32d2-11e9-b280-503eaa06a7ea  ONLINE       0     0     0
          gptid/07349a86-32d2-11e9-b280-503eaa06a7ea  ONLINE       0     0     0

errors: No known data errors
root@freenas:~ #

 

[Chris Moore]

mobo

That is not a word at all, and has no meaning that I am aware of and I have been working full time as a computer professional since 1996.

Gigabyte GA-MA790XT-UD4P

Is a system board, or sometimes called motherboard, or even main logic board. I don't recognize the term you used. The network interface of the system board uses a Realtek chipset and is not suitable for use with FreeNAS as the drivers are not provided by the chip manufacturer and do not work very well.

The NIC: TP-LINK TG-3468 PCIe Gigabit Adapter

Is also not well supported in FreeBSD Unix. It would be best if you chose a network adapter from the list of known working adapters in our hardware guide:

Hardware Recommendations Guide Rev. 1e) 2017-05-06
https://forums.freenas.org/index.php?resources/hardware-recommendations-guide.12/

Hardware Recommendations by @cyberjock - from 26 Aug 2014 - and still valid
https://forums.freenas.org/threads/hardware-recommendations-read-this-first.23069/

 

[andershb]

That is not a word at all, and has no meaning that I am aware of and I have been working full time as a computer professional since 1996.

Is a system board, or sometimes called motherboard, or even main logic board. I don't recognize the term you used. The network interface of the system board uses a Realtek chipset and is not suitable for use with FreeNAS as the drivers are not provided by the chip manufacturer and do not work very well.

Is also not well supported in FreeBSD Unix. It would be best if you chose a network adapter from the list of known working adapters in our hardware guide:

Hardware Recommendations Guide Rev. 1e) 2017-05-06
https://forums.freenas.org/index.php?resources/hardware-recommendations-guide.12/

Hardware Recommendations by @cyberjock - from 26 Aug 2014 - and still valid
https://forums.freenas.org/threads/hardware-recommendations-read-this-first.23069/

Let's not go in discussion what words or not was used in 1996..

So the external NIC is not well supported, that maybe explains it. I do not use the onboard NIC.

Thanks