Re: heads up about filesystem troubles
On Wed, Apr 12, 2006 at 04:49:29PM +0200, Jonathan Thornburg wrote: > Hi, > > >The window of danger was booting a kernel from any time _after_ 2 > >weeks ago and running a fsck from any time _before_ 4 days ago. If > >you have booted a new kernel, do not use the old fsck. > > Do I infer correctly from the following paragraph > >I have backed out the new superblock changes. The next snapshot will > >not upgrade the superblock and will simply use the old format. You > >are encouraged to move away from any snapshot installed in the last 2 > >weeks. > that these changes *only* went into -current, and did *not* go into > -stable? Yes. -Ray-
Re: heads up about filesystem troubles
Hi, The window of danger was booting a kernel from any time _after_ 2 weeks ago and running a fsck from any time _before_ 4 days ago. If you have booted a new kernel, do not use the old fsck. Do I infer correctly from the following paragraph I have backed out the new superblock changes. The next snapshot will not upgrade the superblock and will simply use the old format. You are encouraged to move away from any snapshot installed in the last 2 weeks. that these changes *only* went into -current, and did *not* go into -stable? thanks, ciao, -- -- Jonathan Thornburg <[EMAIL PROTECTED]> Max-Planck-Institut fuer Gravitationsphysik (Albert-Einstein-Institut), Golm, Germany, "Old Europe" http://www.aei.mpg.de/~jthorn/home.html "Washing one's hands of the conflict between the powerful and the powerless means to side with the powerful, not to be neutral." -- quote by Freire / poster by Oxfam
heads up about filesystem troubles
As part of the work to integrate FFS2 support, there have been several changes to the filesystem code. Unfortunately, there are cases where it may cause data corruption. The problematic change was altering the format of the on disk superblock. FFS2 uses a slightly different superblock than FFS1 used. As of two weeks ago, the kernel would automatically upgrade the superblock to the new format, setting a flag that it had done so. Several fields in the block became redundant. The userland utilities were not updated to work with this new format, but instead would remove the flag, meaning the kernel would again read the old fields and upgrade. The problem is that fsck was not taught to remove the flag until several days after the kernel was taught to upgrade. Meaning booting a new kernel but running old fsck could result in superblock corruption because they were operating on different structures. The window of danger was booting a kernel from any time _after_ 2 weeks ago and running a fsck from any time _before_ 4 days ago. If you have booted a new kernel, do not use the old fsck. I have backed out the new superblock changes. The next snapshot will not upgrade the superblock and will simply use the old format. You are encouraged to move away from any snapshot installed in the last 2 weeks.
