Recovering files from ext2/3

jd1008 jd1008 at gmail.com
Sun Sep 21 16:51:34 UTC 2014


On 09/21/2014 03:18 AM, Tom H wrote:
> On Sat, Sep 20, 2014 at 9:41 PM, Joe Zeff <joe at zeff.us> wrote:
>> On 09/20/2014 06:30 PM, jd1008 wrote:
>>> / posted it to the ext3 maling list (turns out they also know ext4)
>>> and they admitted about undocumented effects of using the -S
>>> option, and that one must NEVER use it unless they know the intrinsics
>>> of the FS so well, that the user knows exactly what effects it will
>>> have. /
>> It sounds to me that one of you should go to Bugzilla and file an RFE asking
>> that the documentation be updated.
>  From the "-S" section of the mkfs.extX man page:
>
> "It is critical to specify the correct filesystem blocksize when using this
> option, or there is no chance of recovery."
>
> The "-S" command posted earlier didn't have that - and it's probably
> at least part of what uptream means by "know the intrinsics."
So, if super blocks are damaged, then -b MUST be specified since
fsck cannot discern the blocksize from the super block(s) ??



More information about the users mailing list