On Mon, Dec 10, 2007 at 10:14:31AM +0100, Giggz wrote:
> I'm at work. I can't test it. But if I remember correctly, when I do
> 'tune2fs -C 100 /dev/hda1', then I reboot I get the "primary superblock
> features different from backup superblock" message ( :( ). Then fsck died
> with exit 1.
Fsck "dieing" with exit 1 is normal. That just means that the
filesystem has been modified ("filesystem errors are corrected") and
this isn't an error condition. Note also that the logs from the
current boot are available at /var/log/fsck/checkfs and
/var/log/fsck/checkroot. So you can see what happened at the last reboot.
Unfortunately the init scripts are buggy here. When fsck exits with
an exit code of 1 or 3, it shouldn't use usb the init script helper
function log_action_end_msg (since it prints a red "failed") message.
Instead they should use log_warning_msg to indicate that a full
filesystem check had happened and some non-trivial change (such
backing up the filesystem superblock) had taken place.
I've checked again, though, and both experimentally and by looking at
the sources, if the *only* change you had made was changing the mount
count via tune2fs -C, you shouldn't be seeing the change. The only
things which will trigger a superblock backup are changes in the
superblock feature bitmaps (i.e., tune2fs -O, tune2fs -j, or tune2fs
-s), or changing the number of blocks or inodes (doing an on-line
resize), or changing the uuid (via tune2fs -U).
Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
