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

Snipe3000 wrote:
Hey guys, I started running into this stalling issue at about 85% and pretty much can't add anymore data to the device. Sounds like I'm going to have to remove all the data before I can fix it correct? I'm a bit new to this, but how do I convert the file format to ext3? Is that done within the web interface? Thanks

for me i did the below to get it to work better for me (after removing/backing up data on the drives)

1) Update firmware to 5.3.7
2) in the webGUI under System -> Settings -> Performance untick "Enable disk write cache"
3) use enable root ssh addon http://www.readynas.com/?p=4203
4) ssh into nas and edit /etc/fstab (vi /etc/fstab)
   change: EXT4 to EXT3 for mountpoint /c and save file (:wq)
5) reboot
6) mkfs.ext3 -m 0 /dev/c/c
7) tune2fs -O ^dir_index /dev/c/c
8) reboot
9) copy files to nas

effectivly that's what it summates to of all of what i've done to the device since getting it to get it to the point today where i could fill it untill it had ~30mb left free
still have an issue with delays in starting to copy larger files to the drive when it's 85%+ full, but it let me fill the drive.

hauser wrote:

Found another bug/glitch/weirdness with the unit, if i've got a backup of my firefox cache folder on the nas (47.9 MB (50,267,577 bytes), 529 Files, 2,799 Folders) IOWait goes really high continously and times out some times. Removing this collection of folders and copy starts again at the normal speed. maybe there's an issue with number of folders on EXT3 or the file system driver in use in the firmware. i've got about ~1.13mil files and about 137k folders on the drive currently. currently i've gotten to 94% used (336G free of 5.5Tb) still trying to see how far i can fill the unit before it has an issue again. currently with the nas modifyed as below Firmware: 5.3.7 Write Cache=OFF /dev/c/c formatted as EXT3 tune2fs -O ^dir_index /dev/c/c tune2fs -O ^dir_index turns off B-tree indexing for the volume. so far it's never had any real advatages to file systems unless you are reading only and you know the file in a directory you haven't browsed to yet and are directly accessing that file. dir_index can be turned on again by tune2fs -O dir_index /dev/c/c umount /dev/c/c e2fsck -fD /dev/c/c seems to be working a little better for me than stock so far. waiting to see how full i can get before any more issues, if i an fill to <1gb free i'll be happyer. but if there is a limit to the number of folders able to be stored on the nas, as with having my Firefox profile backup it pushes total folder count over 140k. EXT3 has a limit of 31,998 sub-directories in any single folder so it shouldn't be that and there is still heaps of free inodes (89,921,695 of 91,185,152 used) it would seem like there is yet another bug with NETGEAR's firmware. EDIT: with all the above changes i've just been able to fill the drive to ~30mb free. at which point (expectably IOWait skyrockets) but during the last ~15% of filling the drive IOWaits have been getting quite long when starting to write largish files (1-3gb)

Wau, so extreme case :lol:, but turning off directory index and write cache isn't good... this must hurt normal performance so much.
30MB free on volume is absolutely crazy situation.

Anyway you can try droping journal in filesystem and mount it as ext2 (without data loss). :rofl:

yeah, i could drop journal as i am running it via UPS, but it's working atm. 30mb was filling as a test to see if i can fill without it freezing like before.

"normal" performance for me currently is ~25mb/sec write ~65mb/sec read. might be nice to have faster write, but for my useage pattern it's enough for now.

hauser wrote:

Snipe3000 wrote: Hey guys, I started running into this stalling issue at about 85% and pretty much can't add anymore data to the device. Sounds like I'm going to have to remove all the data before I can fix it correct? I'm a bit new to this, but how do I convert the file format to ext3? Is that done within the web interface? Thanks for me i did the below to get it to work better for me (after removing/backing up data on the drives) 1) Update firmware to 5.3.7 2) in the webGUI under System -> Settings -> Performance untick "Enable disk write cache" 3) use enable root ssh addon http://www.readynas.com/?p=4203 4) ssh into nas and edit /etc/fstab (vi /etc/fstab) change: EXT4 to EXT3 for mountpoint /c and save file (:wq) 5) reboot 6) mkfs.ext3 -m 0 /dev/c/c 7) tune2fs -O ^dir_index /dev/c/c 8) reboot 9) copy files to nas effectivly that's what it summates to of all of what i've done to the device since getting it to get it to the point today where i could fill it untill it had ~30mb left free still have an issue with delays in starting to copy larger files to the drive when it's 85%+ full, but it let me fill the drive.

Cool, It will be a little bit before I can try this, I have to get some new hard drives to backup the NAS (7 TB).
What is dropping the journal? is that something I should do as well?

dropping the journal is something you should only do if you understand the risks involved. most notably if you loose power while writing data to the drive you can risk loosing more than just the file you are writing to at that time. at least with a journal typically you only loose data that hasn't been safely commited to the journal/file system as it creates effectivly a audit trail of what data got changed so the system can replay after power outage to get back to a healthy system.

simplest way woudl be to use ex2 instead of ex3 or you could tell mkfs to not create a journal, but it's probably better to just keep the journal unless your prepaird to nurse a faulty file system back to health yourself as none of what's suggested in this thread is supported by NETGEAR afaik.

info posted within this thread is based on personal experinces and your experince following any of this may not result in the same outcomes that we had. so if your not confident in what your doing and you could somehow "trust" NEGEAR's terrible "remote access policy" they might be able to assist or fix it for you.

hauser wrote:

dropping the journal is something you should only do if you understand the risks involved. most notably if you loose power while writing data to the drive you can risk loosing more than just the file you are writing to at that time. at least with a journal typically you only loose data that hasn't been safely commited to the journal/file system as it creates effectivly a audit trail of what data got changed so the system can replay after power outage to get back to a healthy system. simplest way woudl be to use ex2 instead of ex3 or you could tell mkfs to not create a journal, but it's probably better to just keep the journal unless your prepaird to nurse a faulty file system back to health yourself as none of what's suggested in this thread is supported by NETGEAR afaik. info posted within this thread is based on personal experinces and your experince following any of this may not result in the same outcomes that we had. so if your not confident in what your doing and you could somehow "trust" NEGEAR's terrible "remote access policy" they might be able to assist or fix it for you.

Thanks for the explanation. I'll forget about the journal then.

I have the same issue which has been elevated to Level 3 support still waiting for a reply. From what is reported here I can expect the answer to be "allow root access and let us set the file system up as ext3" So I have started this myself following the "instructions" in this post. I assume that XRAID 2 expansion operates as normal with an ext3 partition on the V2?

davexyz wrote:
I have the same issue which has been elevated to Level 3 support still waiting for a reply. From what is reported here I can expect the answer to be "allow root access and let us set the file system up as ext3" So I have started this myself following the "instructions" in this post. I assume that XRAID 2 expansion operates as normal with an ext3 partition on the V2?

As I know there are always EXT4 on V2 (ARM) devices... only system partitions are EXT3.

davexyz wrote:
I have the same issue which has been elevated to Level 3 support still waiting for a reply. From what is reported here I can expect the answer to be "allow root access and let us set the file system up as ext3" So I have started this myself following the "instructions" in this post. I assume that XRAID 2 expansion operates as normal with an ext3 partition on the V2?

as far as i know XRAID-2 and Flex-RAID should work the same as it's a low level disk raid format and doesn't care what's stored on it, im never planning on putting bigger disks in this nas so i've just gone with Flex-RAID. i figgure i've had this much trouble with it so far im not going to be spending more money on it when a drive fails. that and i'll never be buying another NETGEAR anything after this unit...

hauser wrote:

davexyz wrote: I have the same issue which has been elevated to Level 3 support still waiting for a reply. From what is reported here I can expect the answer to be "allow root access and let us set the file system up as ext3" So I have started this myself following the "instructions" in this post. I assume that XRAID 2 expansion operates as normal with an ext3 partition on the V2? as far as i know XRAID-2 and Flex-RAID should work the same as it's a low level disk raid format and doesn't care what's stored on it, im never planning on putting bigger disks in this nas so i've just gone with Flex-RAID. i figgure i've had this much trouble with it so far im not going to be spending more money on it when a drive fails. that and i'll never be buying another NETGEAR anything after this unit...

But who...? I have IBM Enterprise San, Synology-Rack-NAS and everything seems like joke to me :D
Thanks to full SSH access to Netgear products - I can fix it by myself :) - no problem... for this price it's not that bad.