sideswipe001
Cadet
- Joined
- Jan 28, 2019
- Messages
- 5
Hello all! I just set up FreeNAS for the first time for use in my home. It's basically working, but I've noticed one odd annoyance, and I'm trying to figure out how to resolve it. So first, information about my system:
FreeNAS-11.2-RELEASE-U1
Intel(R) Celeron(R) CPU G3930
Supermicro Micro ATX DDR4 LGA 1151 Motherboards X11SSM-F-O
16 GB ECC RAM
7x 3TB WD Red HDD, single pool (RAIDZ1)
1x 1Gbit NIC
Generally, this is made to be a low-power NAS, primarily used for Plex, and other home use storage (documents, pictures, etc). The Plex server is NOT running on the NAS, it simply connects to the shares.
Here's the odd thing I've noticed:
While messing around re-encoding some of my movies, I found that I could make the SMB shares totally unresponsive by deleting a movie while simultaneously copying a different one over. Often this was from two different clients, but it happens from the same one as well. Generally it would happen like this:
1) Begin to copy over a large-ish movie file (15GB or so) from a Windows client computer. Usually maxes out the 1Gbit connection pretty stably.
2) You can still browse the shares fine, so go find a different movie (about the same size) and delete it off the NAS, from the client.
3) All the shares hang now. Within a few seconds, the currently active transfer stops copying. If any reads from the server are active, they stop. The file does not appear to be deleted yet. You can no longer browse any shares on the NAS. I believe the web interface still responds at this time.
4) Between 10 and 60 seconds later (this fluctuates) the file disappears (the delete happens) and the transfer starts up again. The NAS becomes responsive again.
This is very reproduce-able on my system.
So my question is:
Is this due to insufficient hardware (Not enough RAM, slow processor, slow HDDs) or is this a configuration issue? I haven't really done much except install the OS and set up the pool/shares, so things should basically be at default configuration. Anyone seen this and have an idea what I can do to fix it? It doesn't affect my normal daily usage, but it can get annoying when doing any serious work to my library.
FreeNAS-11.2-RELEASE-U1
Intel(R) Celeron(R) CPU G3930
Supermicro Micro ATX DDR4 LGA 1151 Motherboards X11SSM-F-O
16 GB ECC RAM
7x 3TB WD Red HDD, single pool (RAIDZ1)
1x 1Gbit NIC
Generally, this is made to be a low-power NAS, primarily used for Plex, and other home use storage (documents, pictures, etc). The Plex server is NOT running on the NAS, it simply connects to the shares.
Here's the odd thing I've noticed:
While messing around re-encoding some of my movies, I found that I could make the SMB shares totally unresponsive by deleting a movie while simultaneously copying a different one over. Often this was from two different clients, but it happens from the same one as well. Generally it would happen like this:
1) Begin to copy over a large-ish movie file (15GB or so) from a Windows client computer. Usually maxes out the 1Gbit connection pretty stably.
2) You can still browse the shares fine, so go find a different movie (about the same size) and delete it off the NAS, from the client.
3) All the shares hang now. Within a few seconds, the currently active transfer stops copying. If any reads from the server are active, they stop. The file does not appear to be deleted yet. You can no longer browse any shares on the NAS. I believe the web interface still responds at this time.
4) Between 10 and 60 seconds later (this fluctuates) the file disappears (the delete happens) and the transfer starts up again. The NAS becomes responsive again.
This is very reproduce-able on my system.
So my question is:
Is this due to insufficient hardware (Not enough RAM, slow processor, slow HDDs) or is this a configuration issue? I haven't really done much except install the OS and set up the pool/shares, so things should basically be at default configuration. Anyone seen this and have an idea what I can do to fix it? It doesn't affect my normal daily usage, but it can get annoying when doing any serious work to my library.