From: Theodore Ts'o <tytso@mit.edu>
To: Alexander Harrowell <a.harrowell@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 recovery, the saga of 16777215 continues
Date: Sat, 14 Sep 2013 07:42:53 -0400 [thread overview]
Message-ID: <20130914114253.GA11574@thunk.org> (raw)
In-Reply-To: <CA+qGm=-tSOFyWJFTwB3HWpS_WdGekXyWUVMP8RN33sciwkafMQ@mail.gmail.com>
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
prev parent reply other threads:[~2013-09-14 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 15:40 ext4 recovery, the saga of 16777215 continues Alexander Harrowell
2013-09-14 2:18 ` Theodore Ts'o
2013-09-14 9:25 ` Alexander Harrowell
2013-09-14 11:42 ` Theodore Ts'o [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130914114253.GA11574@thunk.org \
--to=tytso@mit.edu \
--cc=a.harrowell@gmail.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).