Hi,
Theodore Tso a écrit :
> 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
>
I'm at home and I have tested (there is a problem):
so I'm under X I do (/dev/hda6 is mounted, it's my home):
18:54 [EMAIL PROTECTED] /home/giggz/Aide # tune2fs -l /dev/hda6
tune2fs 1.40.3 (05-Dec-2007)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: a514636f-6d5d-4709-8b7e-cb632bca6aa1
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal dir_index filetype needs_recovery
sparse_super
Filesystem flags: signed directory hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 524288
Block count: 1024135
Reserved block count: 30724
Free blocks: 559580
Free inodes: 471505
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Filesystem created: Mon Sep 27 19:16:54 2004
Last mount time: Mon Dec 10 18:41:59 2007
Last write time: Mon Dec 10 18:41:59 2007
Mount count: 9
Maximum mount count: 20
Last checked: Sat Dec 8 19:52:47 2007
Check interval: 15552000 (6 months)
Next check after: Thu Jun 5 20:52:47 2008
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: ed5a0da0-92b5-41db-9616-a60f12d2fc8c
Journal backup: inode blocks
So I change the maximum count :
18:59 [EMAIL PROTECTED] /home/giggz/Aide # tune2fs -C 100 /dev/hda6
tune2fs 1.40.3 (05-Dec-2007)
Initialisation du nombre courant de montages à 100
then I do a 'tune2fs -l /dev/hda6' to verify.
18:59 [EMAIL PROTECTED] /home/giggz/Aide # tune2fs -l /dev/hda6
tune2fs 1.40.3 (05-Dec-2007)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: a514636f-6d5d-4709-8b7e-cb632bca6aa1
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal dir_index filetype needs_recovery
sparse_super
Filesystem flags: signed directory hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 524288
Block count: 1024135
Reserved block count: 30724
Free blocks: 559578
Free inodes: 471503
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Filesystem created: Mon Sep 27 19:16:54 2004
Last mount time: Mon Dec 10 18:41:59 2007
Last write time: Mon Dec 10 18:59:14 2007
Mount count: 100
Maximum mount count: 20
Last checked: Sat Dec 8 19:52:47 2007
Check interval: 15552000 (6 months)
Next check after: Thu Jun 5 20:52:47 2008
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: ed5a0da0-92b5-41db-9616-a60f12d2fc8c
Journal backup: inode blocks
And I reboot. And I get that :
19:04 [EMAIL PROTECTED] ~ % cat /var/log/fsck/checkfs
Log of fsck -C -V -R -A -a
Mon Dec 10 19:01:31 2007
fsck 1.40.3 (05-Dec-2007)
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /home] fsck.ext3 -a -C0 /dev/hda6
/dev/hda6 primary superblock features different from backup, check forced.
/dev/hda6: 52781/524288 files (4.7% non-contiguous), 464551/1024135 blocks
[/sbin/fsck.ext3 (1) -- /donnees] fsck.ext3 -a -C0 /dev/hda4
DONNEES: clean, 6768/3071168 files, 1643181/3070423 blocks
fsck died with exit status 1
Mon Dec 10 19:01:58 2007
----------------
So there is a problem. After this, If I reboot I don't have any problem.
My system is quite old. I'm under SID since woody. Last yest I did this
changes on my partitions because I read that this flag was enabled yet
by default :
tune2fs -O dir_index /dev/hda6
fsck -fD -C0 /dev/hda6
Could this change have a relation with my problem ?
Thx a lot
Guillaume
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
