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
| ||
|
Message-ID: <CA+qGm=-tSOFyWJFTwB3HWpS_WdGekXyWUVMP8RN33sciwkafMQ@mail.gmail.com> Date: Sat, 14 Sep 2013 09:25:35 +0000 From: Alexander Harrowell <a.harrowell@...il.com> To: "Theodore Ts'o" <tytso@....edu> Cc: linux-ext4@...r.kernel.org Subject: Re: ext4 recovery, the saga of 16777215 continues dump_inode 2937950 /media/usbdisk/dump On Sat, Sep 14, 2013 at 2:18 AM, Theodore Ts'o <tytso@....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 -- 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
Powered by blists - more mailing lists