Re: Dumpe2fs output with primary and backup superblock are different?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jan 16, 2014 at 04:14:14PM +0530, Subranshu Patel wrote:
> I am using dumpe2fs command using primary superblock (default) and
> backup superblock. In both the cases the output is different.

Yes, this is expected.  It's too expensive to be constantly updating
all of the backup block group descriptors every time we allocate or
deallocate a block or inode.  What is important to be kept in the
backup block group descriptors is where to find the inode table and
allocation bitmaps.  E2fsck can reconstruct the information which is
not updated in the backup block group descriptors and backup
superblock, and that's what you are seeing which is different.

Regards,

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux