[Rather obscure bug in ext3 on 2.4.20 kernels. Either (1) don't use 2.4.20, (2) Don't use the configurations that trigger the bug, (3) patch with the patch given in the mail or (4) wait for 2.4.21 -- Raju]
http://www.uwsg.iu.edu/hypermail/linux/kernel/0212.0/0010.html In 2.4.20-pre5 an optimisation was made to the ext3 fsync function which can very easily cause file data corruption at unmount time. This was first reported by Nick Piggin on November 29th (one day after 2.4.20 was released, and three months after the bug was merged. Unfortunate timing) This only affects filesystems which were mounted with the `data=journal' option. Or files which are operating under `chattr -j'. So most people are unaffected. The problem is not present in 2.5 kernels. The symptoms are that any file data which was written within the thirty seconds prior to the unmount may not make it to disk. A workaround is to run `sync' before unmounting. [snip] Regards, -- Raju -- Raju Mathur [EMAIL PROTECTED] http://kandalaya.org/ It is the mind that moves ================================================ To unsubscribe, send email to [EMAIL PROTECTED] with unsubscribe in subject header. Check archives at http://www.mail-archive.com/ilugd%40wpaa.org
