Thanks, I have some code which fixes this, causes some other strange behavior though (including corruption in other ways), so it needs work. Basically the file data is on disk, and before remounting
This should be fixed in the 2.4 cvs tree now (or within the hour), I will push it into 2.6 tomorrow. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@xxx
Hi Steve, I downloaded the 2.4 cvs tree, built a kernel, and tested my script on the same system that failed before. The script worked as expected. Thanks for fixing this problem so quickly! -blair
Thanks, I have some code which fixes this, causes some other strange behavior though (including corruption in other ways), so it needs work. Basically the file data is on disk, and before remounting
This should be fixed in the 2.4 cvs tree now (or within the hour), I will push it into 2.6 tomorrow. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@xxx
Hi Steve, I downloaded the 2.4 cvs tree, built a kernel, and tested my script on the same system that failed before. The script worked as expected. Thanks for fixing this problem so quickly! -blair
I have a simple shell script that writes numbers to a file and every 10 numbers does a sync and after 40 does a reboot. I've attached the script to this email. If the file is written to an EXT3 file
I have a simple shell script that writes numbers to a file and every 10 numbers does a sync and after 40 does a reboot. I've attached the script to this email. If the file is written to an EXT3 files
[snip] What buffles me a bit is that he does a "reboot -f" and, according to the man page on my RedHat 7.3 system, reboot should sync the filesystems prior to reboot. If he'd done a "reboot -fn" (-n
Hi, It is even worse. He does sync after write of every 10 numbers. So after writing 40 he does sync (!) and afterward he reboots. So after next booting he should see this "40", and it shouldn't be d
Hi Klaus Thanks for the pointer. I'm probably just naive, but I thought a sync call forced the data to secondary storage. Maybe sync doesn't guaruntee that: NAME sync - flush filesystem buffers SYNOP
Hi Simon, et al, I used stock kernel.org sources with SGI's XFS patches: for XFS 1.1, I used the 2.4.18 kernel for XFS 1.2, I used the 2.4.19 kernel for XFS 1.3pre, I used the 2.4.21 kernel I thought
Its a bug, not sure what it is yet, those subsequent syncs should be working. In testing sync and reboot I was untaring a linux kernel doing sync followed by immediate reset of the box. I can build t
I have a simple shell script that writes numbers to a file and every 10 numbers does a sync and after 40 does a reboot. I've attached the script to this email. If the file is written to an EXT3 file
I have a simple shell script that writes numbers to a file and every 10 numbers does a sync and after 40 does a reboot. I've attached the script to this email. If the file is written to an EXT3 files
[snip] What buffles me a bit is that he does a "reboot -f" and, according to the man page on my RedHat 7.3 system, reboot should sync the filesystems prior to reboot. If he'd done a "reboot -fn" (-n