Recovering files from ext2/3
Chris Murphy
lists at colorremedies.com
Sat Sep 20 01:16:42 UTC 2014
On Sep 19, 2014, at 11:49 AM, jd1008 <jd1008 at gmail.com> wrote:
>
> On 09/19/2014 08:39 AM, Robert Nichols wrote:
>> On 09/18/2014 10:57 PM, jd1008 wrote:
>>> I ran mkfs.ext3 -S /dev/sdc7
>>> then ran fsck.ext3 -y /dev/sdc7
>>> it blew away EVERYTHING :)
>>>
>>> Back to square one and re-dd original to test drive
>>> and start over.
>>
>> Ouch! That _used_ to work. Trying it just now, "mke3fs -S" seems
>> to clear a substantial portion of the inodes, which the manpage
>> specifically says it should _not_ do, and then /fsck/ completes the
>> destruction by moving all of the remaining inodes to lost+found.
>>
>> Sorry about that.
>>
> Can raise a bug against it?
Chances are this is an upstream bug, or a misunderstanding. You should post your reproduce steps to the ext4 list, what you expect to happen based on man page, and what actually happens.
http://vger.kernel.org/vger-lists.html#linux-ext4
Chris Murphy
More information about the users
mailing list