Re: Fsck repair takes very long for 1,761 inodes containing multiply-claimed blocks on ext4

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

 



On Fri, Apr 17, 2015 at 04:05:04PM -0400, Akos Csete wrote:
> 
> Could I then just wipe the inodes of the older files (and restore them
> later from backup) and let the new file claim those blocks? Or are the
> new file's claim to those blocks suspect?

OK, if the mod times are different, then it probably wasn't a case of
an inode getting written to the wrong place on disk.  What probably
did happen is the block allocation bitmaps got corrupted, and so
blocks that were in use (and should have been marked in use) were not,
so they got used for some other inode.

So yes, you can try wiping the inodes for the older files, and hope
for the best, but it may be that some of the newer files may end up
getting corrupted.  So you might want to do some spot checks
afterwards.  And if you have backups, this might be a good time to
consider going to your backup tapes....

						- 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