On Sat, Dec 08, 2007 at 12:27:00PM +0100, giggz wrote:
> Package: e2fsprogs
> Version: 1.40.3-1
> Severity: normal
>
> Since the yesterday upgrade of e2fs* i get this message when the pc
> checks my filesystem :
> "primary superblock features different from backup, check forced"
> This appear on all the ext partitions that I check.
>
> What can I do to avoid that ?
> Is there a bug or is it because my system comes from woody and I
> change 2 flags of my partitions by myself with tune2fs ?
This is a one-time occurence. In order to make the usage of the
backup superblocks more robust, we now make sure that when the primary
superblock values change, that they get backed up in the backup
superblocks.
This become especially a problem with the usage of online resize
operations, which change the number of blocks in the filesystem in the
primary superblock, but *not* in the backup superblocks. However, I
didn't want to just automatically backup the data to the primary
superblock to the backup superblocks, since the information in the
primary superblock could be incorrect, and you don't want to blow away
the information in the backup superblocks in that case.
Hence, in the situation where the primary and superblocks contain
different values for certain key configuration parameters for the
filesystem (i.e., the filesystmem features bitmasks, the number of
blocks and number of inodes, etc.), e2fsck forces a check, and then
once it is sure everything is clean, it will copy the changes to the
backup superblock.
So it should only do this *once*; after that, the backup superblocks
will be in synch with the primary superblock, and then you shouldn't
see that message again.
Are you seeing more than once, after a filesystem check has been
successfully completed? If you are that's a bug, and it would be good
if you could send me the output of these two commands:
dumpe2fs -h /dev/sdXXX
(to print out the information of the primary superblock)
dumpe2fs -ob32768 -oB4096 -h /dev/sdXXX
(to print out the information of the backup superblock)
(or if you have a 1k block filesystem, replace the first two arguments
with "-ob8193 -oB1024"; and of course, replace /dev/sdXXX with the
device on which your filesystem is stored).
If you are only seeing that message once, then it's normal operation
and there is no bug.
Regards,
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
