Re: Recovering a damaged ext4 fs - revisited.

[Eric Sandeen <sandeen@redhat.com>]

J.D. Bakker wrote:
> At 22:02 -0600 05-02-2009, Eric Sandeen wrote:
>> J.D. Bakker wrote:
>>  >    Error writing block 1 (Attempt to write block from filesystem
>>>  resulted in short write).  Ignore error? no
>>>     Error writing block 2 (Attempt to write block from filesystem
>>>  resulted in short write).  Ignore error? no
>>>     Error writing block 3 (Attempt to write block from filesystem
>>>  resulted in short write).  Ignore error? no
>>>     [...]
>>>     Error writing block 231 (Attempt to write block from filesystem
>>>  resulted in short write).  Ignore error? no
>>>     Error writing block 232 (Attempt to write block from filesystem
>>>  resulted in short write).  Ignore error? no
>>>
>>>  (full log at http://lartmaker.nl/ext4/e2fsck-md0.txt)
>> Those seem a bit odd; why are these write failing?  Anything in the
>> kernel logs when this happens?  I'm just wondering if there could be
>> some underlying storage problem?
> 
> No, nothing in the logs.
> 
> Isn't this a side-effect of me passing the -n option to e2fsck? I 
> haven't traced the full path in the e2fsprogs-source, but it would 
> appear that the -n option sets E2F_OPT_NO, which sets 
> E2F_OPT_READONLY, which clears EXT2_FLAG_RW, which (in a few places) 
> clears IO_FLAG_RW, which appears to open the fs RO (as expected).

oh, perhaps.  I'll have to look more closely; I'd hope (I thought...)
that running it in test mode wouldn't issue such dire error messages :)

-Eric