Yeah I did the trap thing wrong it seems, I will fix that up and back out all of the related changes, thanks. I didn't change the test, I just had to change the golden output. I was running it agains
..... `dmsetup suspend` ends up in dm_suspend(). This calls lock_fs(), which calls freeze_bdev().... If you do `dmsetup suspend --nolockfs` then it won't freeze the filesystem during the suspend... E
Ok so I think I'll just make this test do all the iterations of the fsync tester with and without --nolockfs, since without --nolockfs I'm still seeing problems, does that sound reasonable? No kiddin
Btw its test 19 O_DIRECT that gives me a 0 length file, the buffered case is fine. The test just does a randomly sized sub-block sized write over and over again for a random number of times and fsync
Interesting - it only runs fsync every 8 iterations of the loop. Can you check that it is running enough loops to execute a fsync? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
If the loop doesn't fsync it still fsyncs before the program exits. Side note I once wasted a week because Chris's fsync tester _didn't_ fsync() before exit so it would tell you a md5sum of a file th
Doh! I noticed that yesterday but forgot about it. Not enough coffee. I'll have a closer look, then. I think we've all made mistakes like that at least once.... :/ Cheers, Dave. -- Dave Chinner david