* ext4 recovery, the saga of 16777215 continues
@ 2013-09-13 15:40 Alexander Harrowell
2013-09-14 2:18 ` Theodore Ts'o
0 siblings, 1 reply; 4+ messages in thread
From: Alexander Harrowell @ 2013-09-13 15:40 UTC (permalink / raw)
To: linux-ext4
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?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ext4 recovery, the saga of 16777215 continues
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
0 siblings, 1 reply; 4+ messages in thread
From: Theodore Ts'o @ 2013-09-14 2:18 UTC (permalink / raw)
To: Alexander Harrowell; +Cc: linux-ext4
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ext4 recovery, the saga of 16777215 continues
2013-09-14 2:18 ` Theodore Ts'o
@ 2013-09-14 9:25 ` Alexander Harrowell
2013-09-14 11:42 ` Theodore Ts'o
0 siblings, 1 reply; 4+ messages in thread
From: Alexander Harrowell @ 2013-09-14 9:25 UTC (permalink / raw)
To: Theodore Ts'o; +Cc: linux-ext4
dump_inode 2937950 /media/usbdisk/dump
On Sat, Sep 14, 2013 at 2:18 AM, Theodore Ts'o <tytso@mit.edu> wrote:
> 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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ext4 recovery, the saga of 16777215 continues
2013-09-14 9:25 ` Alexander Harrowell
@ 2013-09-14 11:42 ` Theodore Ts'o
0 siblings, 0 replies; 4+ messages in thread
From: Theodore Ts'o @ 2013-09-14 11:42 UTC (permalink / raw)
To: Alexander Harrowell; +Cc: linux-ext4
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-09-14 11:42 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).