Re: ext4 bug and/or e2fsck hole

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

 



On Tue, Apr 07, 2009 at 04:58:35PM -0700, Andreas Dilger wrote:
> On Apr 08, 2009  09:09 +0930, Kevin Shanahan wrote:
> > hermes:~# debugfs -c -R 'imap 383' /dev/dm-0
> > debugfs 1.41.3 (12-Oct-2008)
> > /dev/dm-0: catastrophic mode - not reading inode or group bitmaps
> > 383: File not found by ext2_lookup 
> > hermes:~# debugfs -c -R 'imap <383>' /dev/dm-0
> > debugfs 1.41.3 (12-Oct-2008)
> > /dev/dm-0: catastrophic mode - not reading inode or group bitmaps
> > Inode 383 is part of block group 0
> >         located at block 312, offset 0x0e00
> 
> In the meantime you can use "debugfs -w /dev/dm-0", "clri {filename}"
> to zero out the inode, "freei {filename}" to mark the inode unused,
> and "rm {filename}" to remove the file from the directory.

Thanks, I'll do this tonight when I can unmount the filesystem
again. If you think of anything other information I should gather
before I do that, let me know in the next 6-7 hours ;)

Cheers,
Kevin.
--
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