linux-ext4 - Re: ext4 recovery, the saga of 16777215 continues

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20130914114253.GA11574@thunk.org>
Date:	Sat, 14 Sep 2013 07:42:53 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Alexander Harrowell <a.harrowell@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: ext4 recovery, the saga of 16777215 continues

On Sat, Sep 14, 2013 at 09:25:35AM +0000, Alexander Harrowell wrote:
> dump_inode 2937950 /media/usbdisk/dump

That writes the contents of that inode to a disk.  So your question of
"inodes having a defined size" doesn't make much sense.  An inode is a
fixed size, usually 128 or 256 bytes.  But the contents of the inode
(file) is anything up to 16TB....

In general if we're looking at a potentially corrupted file system,
the first thing you want to do is to look at it via the stat command
and make sure it looks at least vaguely sane.  You do this via the command
"stat <2937950>".

							- Ted
--
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