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: Fri, 13 Sep 2013 22:18:18 -0400 [thread overview]
Message-ID: <20130914021818.GA1112@thunk.org> (raw)
In-Reply-To: <CA+qGm=_vV3xv8ip6JfuW7hDo3ZgR5Bj4oA_1r0BPD33rAso0Jg@mail.gmail.com>
On Fri, Sep 13, 2013 at 03:40:47PM +0000, Alexander Harrowell wrote:
> OK, so after updating e2fsprogs and doing a bunch of hacking around, I
> was eventually able to find the inode that returns hundreds of MB of
> 16777215 in the multiply-claimed blocks pass.
>
> Dumping it out with debugfs, the output file reached 28 GB before the
> device receiving ran out of space. I thought inodes were of defined
> size?
What do you mean by "dumping it out"? What precise debugfs command
were you using?
stat? dump? something else?
- Ted
next prev parent reply other threads:[~2013-09-14 2:18 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 [this message]
2013-09-14 9:25 ` Alexander Harrowell
2013-09-14 11:42 ` Theodore Ts'o
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=20130914021818.GA1112@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).