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

hauser wrote:
process i used to drop to ext3: vi /etc/fstab -- changed: ext4 to ext3 for mountpoint /c reboot mkfs.ext3 -m 0 /dev/c/c reboot so i would assume that it's a fully fresh ext3 volume journal included as that's what mkfs does -m 0 just sets the root reserved blocks to 0% at time of creation so don't have to tune2fs it down to 0% from the default of 5%

That's what I do and after that I have IOWaits on values I posted.

My original path:
First I saw this problem on default ext4 so I reformat it to ext3 and it worked ... after that for testing purposes I mount ext3 with ext4 driver and then system is bad as default.
Okay I'm clever and remounted this volume as ext3 back, but problem persist. WTF - I think ... Why? Then I drop journal and recreate him and voala problem disappeared.

I'm not sure, but I think that there is some bug in journaling, because hardrive permanently writing something (i can hear it by myself HDD LED is flashing) -> high IOWaits
When I touch this volume anyway with ext4 driver I have utilization IOWaits on 100% even when I go back to ext3.

Part with recreating journal I tried many times just to be sure.
default:
ext4 -> problem 100%IO
modified/reformatted:
ext3 driver 5%IO-> ext4 driver 100%IO -> ext3 driver 100%IO (shock for me)
removing journal -> ext3 -> ok 5%IO -> ... and again and again / same results

10% CPU, 66% System, 3% IO Waits / 50MB/s constant writing (3GB data) so this is what I have now with ext3, but of course filescan taking ages.
Maybe NAS can do even more, but with my HDD this is maximum when I benchmarked this HDD in my PC than I have (~120MB/s read, ~50MB/s write)
-> before it's like this 6% CPU, 10% System, 99% IO Waits (not exactly data just what I remember - I don't want to test it again)