i've recently purchased one of the Netgear ReadyNAS NV+ V2 units and have become very unhappy with it. it started out ok and could copy files to it at good rate, now that the unit is over 80% full i've been coming accross the smbd stall on IO Wait issue that seems to plague this unit :(after coming to these fourms i found that there are many other users with the same issues and none of the solutions they have had for them posted around converting to EXT3 has made the copy issues any better for me.i have linked the other topics i could find with same issues that have been plagueing me so far. i have logged a support case (20047616) with netgear but their "remote access policy" is very bad and i can't agree to it. viewtopic.php?f=21&t=63992 viewtopic.php?f=21&t=64739 viewtopic.php?f=21&t=67310 viewtopic.php?f=21&t=66731

Converting to EXT3 helps, does it? And what do you do if you already have all your disks in EXT3???!!!Netgear have never impressed me on quality nor performance, but the Sw engineering quality control really hits the bottom. Have they ever heard of version control? Have in gods name can an old bug pass through to a subsequent release - albeit a Beta???!!!This was the final blow for me- getting in to my car to go and by a Synology or Qnap - whatever bet never again Netgear and Readynas!

Converting to EXT3 will help. Again thank you NETGEAR for quality control.You need to download your data because it will be wiped (from what I've been told). Yes, you need to give them root OR add drives to get below 80%.. I did both ...

I'm looking into this issue, from the logs I see that you converted to ext3 yourself, and you're still running into the issue, right? I'm chasing down a few things, could you confirm, are you storing a large amount of small files on the device (checked volume stat, if my math is correct, average of 3.5MB per file)?Are you only using CIFS/SMB to copy files to the NAS?

Skywarp wrote:I'm looking into this issue, from the logs I see that you converted to ext3 yourself, and you're still running into the issue, right? I'm chasing down a few things, could you confirm, are you storing a large amount of small files on the device (checked volume stat, if my math is correct, average of 3.5MB per file)?Are you only using CIFS/SMB to copy files to the NAS?I have same problems... converting volume to ext3 solve everything. This problem is related only to filesystem itself not to anything else.This is propably kernel bug, somewhere at journaling code. I found it on Synology and QNAP forums and people are very angry because of this.There's nothing in logs only IOWaits raises to 100% after any write is performed and system is not responsive for some seconds/speed drops to 10MB/s or lower.Maybe disabling journaling in ext4 can help, but I don't trust this filesystem for now.I saw this problem when volume is aprox. 85% full and I have a lot small files on it.When you format ext3 volume you can switch to ext4 driver and in that situation everything goes wrong.Journal must be recreated while you are going back to ext3 - if not, ext3 have same problems as ext4 (100% IOWaits).Perfomace with nearly full volume on ext3 is ~50MB/s write ~80MB/s read - not bad for ARM platform.

Skywarp wrote:I'm looking into this issue, from the logs I see that you converted to ext3 yourself, and you're still running into the issue, right? I'm chasing down a few things, could you confirm, are you storing a large amount of small files on the device (checked volume stat, if my math is correct, average of 3.5MB per file)?Are you only using CIFS/SMB to copy files to the NAS?yeah i converted to ext3 myself "mkfs.ext3 -m 0 /dev/c/c" and still have the issue, last night i upgraded to 5.3.7 as it adds an option in the web GUI to disable write caching and am trying to fill drive again past 80% and hopefully to 99% but am not very hopefull.yeah im fairly sure most of my files are farily small, only a few larger files. im only using CIFS/SMB to copy via the lan, im using rsync for some remote backup from another site to here.have been trying to figgure out if NCQ is enabled on the device as `cat /sys/block/sda/device/queue_depth` results "31" (suggesting it's on) and trying to set it to "1" results in error.also trying to figgure out why/how to stop the segate drives "chirping" as they load/unload the heads periodaccly as after ~1month my Load Cycle Count is over 10k for each drive as reported in smart.EDIT:Currently with firmware 5.3.7 and write cache turned off via the GUI i've managed to copy about 180gb more to the drive with some acceptable speed but after that mark im getting about 1minute of IO Wait before starting to copy a file and then more IO Wait during copying the file to the drive. the test set of data have files between 1gb to 3gb files. currently at about 875GB free space reported.

NV+ V2 stalling when 80%+ full (20047616)

197 Replies

Replies have been turned off for this discussion

aks
Virtuoso
May 06, 2013
What was the successful resolution then?
BTW, without trying to stir things up, merchantable quality, fit for purpose, etc, all apply to UK irrespective of warranty, so in theory we could still demand a replacement.
Tokfan
Aspirant
May 06, 2013
Best sollution would be a 100% refund or a new machine from a different brand. :)
de_niro
Guide
May 06, 2013
Hello guys,we confirmed this issue has been fixed in 5.3.8 and it will be released soon enough,we hope for your understanding and sorry for so much trouble.
de_niro
Guide
May 06, 2013
Actually 5.3.8-T20 is able to fix this issue,we've merged all patches in but..... if it doesn't work for you,please backup data and factory default your volume,the reason is your volume could be badly fragmented and the file system needs to be rebuilt once again.
chirpa
Luminary
May 06, 2013
But even with a factory default (not possible for many people), what happens when they hit fragmentation down the road again? Seems like a short term solution.

janforman

Aspirant

May 06, 2013

de niro wrote:
Actually 5.3.8-T20 is able to fix this issue,we've merged all patches in but..... if it doesn't work for you,please backup data and factory default your volume,the reason is your volume could be badly fragmented and the file system needs to be rebuilt once again.

de niro wrote:
Actually 5.3.8-T20 is able to fix this issue,we've merged all patches in but..... if it doesn't work for you,please backup data and factory default your volume,the reason is your volume could be badly fragmented and the file system needs to be rebuilt once again.

That's strange. Can you describe what is exactly patched? It's some tweaks to default values or C source is modified somehow? Anyway I don't have any problems with ext3 and I can write 50MB/s constantly without any problems.

hauser1
Aspirant
May 06, 2013
chirpa wrote:
But even with a factory default (not possible for many people), what happens when they hit fragmentation down the road again? Seems like a short term solution.

exactly and for me fragmentation should be low as I've hit this problem just in copying data back to the device from one computer with single thread copy after a factory default many times....

normally fragmentation is "bad" if you copy & delete files randomly large amounts of files over time.

chirpa wrote:
But even with a factory default (not possible for many people), what happens when they hit fragmentation down the road again? Seems like a short term solution.

janforman

Aspirant

May 06, 2013

hauser wrote:
chirpa wrote:
But even with a factory default (not possible for many people), what happens when they hit fragmentation down the road again? Seems like a short term solution.

exactly and for me fragmentation should be low as I've hit this problem just in copying data back to the device from one computer with single thread copy after a factory default many times....

normally fragmentation is "bad" if you copy & delete files randomly large amounts of files over time.

You are right, and when I try it with switchover ext3 <> ext4 with absolutely identical data (i mean 100%) - ext4 driver always lockup NAS completely.
There is no fragmentation and volume is mounted in backward compatibility with ext3 then IO kills all! So I can remount same partition with ext3 driver back and problem is gone.
That's why I am asking what is changed, because I saw some new kernel patches to ext4.

a) it's a driver bug
b) 256MB is not enough for ext4 of this volume size

if it's b) then some tuning may solve this problem.
But I don't understand why ext4 driver fails when have absolutely same conditions as ext3 (disabled extents, same data, everything is 100% same...)

hauser1

Aspirant

May 08, 2013

janforman wrote:
hauser wrote:
chirpa wrote:
But even with a factory default (not possible for many people), what happens when they hit fragmentation down the road again? Seems like a short term solution.

exactly and for me fragmentation should be low as I've hit this problem just in copying data back to the device from one computer with single thread copy after a factory default many times....

normally fragmentation is "bad" if you copy & delete files randomly large amounts of files over time.

You are right, and when I try it with switchover ext3 <> ext4 with absolutely identical data (i mean 100%) - ext4 driver always lockup NAS completely.
There is no fragmentation and volume is mounted in backward compatibility with ext3 then IO kills all! So I can remount same partition with ext3 driver back and problem is gone.
That's why I am asking what is changed, because I saw some new kernel patches to ext4.

a) it's a driver bug
b) 256MB is not enough for ext4 of this volume size

if it's b) then some tuning may solve this problem.
But I don't understand why ext4 driver fails when have absolutely same conditions as ext3 (disabled extents, same data, everything is 100% same...)

there might be kernel patches to the main kernel src but iirc T20 didn't include a new kernel, they have just changed mount settings / scripts.

tarkeen
Aspirant
May 08, 2013
That no fix. Do factory default mean all data loss. When you have proper fix ready? 5.3.8 T21? 5.3.9?

Forum Discussion

NV+ V2 stalling when 80%+ full (20047616)

197 Replies

Related Content

Stalls from WAC730

Firmware update stalls for EX3700

Nighthawk AC1750 setup stalls at routerlogin

RN214 File transfers stall

ReadyNAS RN214 check root fs - booting 47% - stalled

NETGEAR Academy

ProSupport for Business