linux-ext4 - Re: ext4 bug and/or e2fsck hole

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <20090407235835.GI3204@webber.adilger.int>
Date:	Tue, 07 Apr 2009 16:58:35 -0700
From:	Andreas Dilger <adilger@....com>
To:	Kevin Shanahan <kmshanah@...b.org.au>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: ext4 bug and/or e2fsck hole

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.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

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