problem with reiser3

problem with reiser3

[Marcos Dione]

    hi all. I'm having problems checking a reiser3 filesystem.
reiserfsck says: 

bread: Cannot read the block (27887610): (Input/output error).

    I passed badblocks over the partition and found 61 bad sectors
(which I know is bad), then run reiserfsck -B with the bad blocks file
and got the same, but also this:

create_badblock_bitmap: block number (111550463) points out of fs size (39072080).

    any hints?

Re: problem with reiser3

[Marcos Dione]

On Mon, Aug 21, 2006 at 07:24:21PM -0300, Marcos Dione wrote:
>     hi all. I'm having problems checking a reiser3 filesystem.
> reiserfsck says: 
> 
> bread: Cannot read the block (27887610): (Input/output error).
> 
>     I passed badblocks over the partition and found 61 bad sectors
> (which I know is bad), then run reiserfsck -B with the bad blocks file
> and got the same, but also this:
> 
> create_badblock_bitmap: block number (111550463) points out of fs size (39072080).
> 
>     any hints?

    forgot to mention: I tried to resize the fs to the partition size
and got this:

$ sudo resize_reiserfs /dev/sda1
resize_reiserfs 3.6.19 (2003 www.namesys.com)

/dev/sda1 already is of the needed size. Nothing to be done

Re: problem with reiser3

[Edward Shishkin]

Marcos Dione wrote:
>     hi all. I'm having problems checking a reiser3 filesystem.
> reiserfsck says: 
> 
> bread: Cannot read the block (27887610): (Input/output error).
> 
>     I passed badblocks over the partition and found 61 bad sectors
> (which I know is bad), 


did you specify reiserfs block size (via option -b) when creating a list
of bad blocks?


then run reiserfsck -B with the bad blocks file
> and got the same, but also this:
> 
> create_badblock_bitmap: block number (111550463) points out of fs size (39072080).
> 
>     any hints?
> 

it would be better to create a backup on a spare bigger partition
using dd_rescue (pad not recoverable zones with zeroes), then run
fsck on the created image.

Re: problem with reiser3

[Marcos Dione]

On Tue, Aug 22, 2006 at 03:38:40AM +0400, Edward Shishkin wrote:
> Marcos Dione wrote:
> >    hi all. I'm having problems checking a reiser3 filesystem.
> >reiserfsck says: 
> >
> >bread: Cannot read the block (27887610): (Input/output error).
> >
> >    I passed badblocks over the partition and found 61 bad sectors
> >(which I know is bad), 
> 
> 
> did you specify reiserfs block size (via option -b) when creating a list
> of bad blocks?

    dunno which is the block size. tried to figure it out, but (from
dmesg trying to mount the partition):
    
ReiserFS: sda1: journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

    and:

$ sudo reiserfstune /dev/sda1
reiserfstune: Filesystem looks not cleanly umounted, check the consistency first.

    I assume it's the 8192 the kernel reports...

> it would be better to create a backup on a spare bigger partition
> using dd_rescue (pad not recoverable zones with zeroes), then run
> fsck on the created image.

    unluckly I can't. it's a 160 GiB partition and I don't have spare
space.

Re: problem with reiser3

[David Masover]

Marcos Dione wrote:

>> it would be better to create a backup on a spare bigger partition
>> using dd_rescue (pad not recoverable zones with zeroes), then run
>> fsck on the created image.
> 
>     unluckly I can't. it's a 160 GiB partition and I don't have spare
> space.

How much spare space do you have?  You may be able to do some tricks 
with dm_snapshot...

Re: problem with reiser3

[Marcos Dione]

On Mon, Aug 21, 2006 at 08:23:30PM -0500, David Masover wrote:
> >>it would be better to create a backup on a spare bigger partition
> >>using dd_rescue (pad not recoverable zones with zeroes), then run
> >>fsck on the created image.
> >
> >    unluckly I can't. it's a 160 GiB partition and I don't have spare
> >space.
> 
> How much spare space do you have?  You may be able to do some tricks 
> with dm_snapshot...

    right now, I have 45 MiB of space in my spare disk. I *could*
(should?) make more space, but can't guarrantee anythung.

Re: problem with reiser3

[David Masover]

Marcos Dione wrote:
> On Mon, Aug 21, 2006 at 08:23:30PM -0500, David Masover wrote:
>>>> it would be better to create a backup on a spare bigger partition
>>>> using dd_rescue (pad not recoverable zones with zeroes), then run
>>>> fsck on the created image.
>>>    unluckly I can't. it's a 160 GiB partition and I don't have spare
>>> space.
>> How much spare space do you have?  You may be able to do some tricks 
>> with dm_snapshot...
> 
>     right now, I have 45 MiB of space in my spare disk. I *could*
> (should?) make more space, but can't guarrantee anythung.

That won't be enough.  Worst case, decide whether the data on that 160 
gig partition is worth buying a cheap 200 or 300 gig drive for this backup.

Re: problem with reiser3

[Edward Shishkin]

Marcos Dione wrote:
> On Tue, Aug 22, 2006 at 03:38:40AM +0400, Edward Shishkin wrote:
> 
>>Marcos Dione wrote:
>>
>>>   hi all. I'm having problems checking a reiser3 filesystem.
>>>reiserfsck says: 
>>>
>>>bread: Cannot read the block (27887610): (Input/output error).
>>>
>>>   I passed badblocks over the partition and found 61 bad sectors
>>>(which I know is bad), 
>>
>>
>>did you specify reiserfs block size (via option -b) when creating a list
>>of bad blocks?
> 
> 
>     dunno which is the block size. tried to figure it out, but (from
> dmesg trying to mount the partition):
> 


debugreiserfs /dev/sda1
then look at Blocksize it the output


> ReiserFS: sda1: journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
> 
>     and:
> 
> $ sudo reiserfstune /dev/sda1
> reiserfstune: Filesystem looks not cleanly umounted, check the consistency first.
> 
>     I assume it's the 8192 the kernel reports...
> 
> 
>>it would be better to create a backup on a spare bigger partition
>>using dd_rescue (pad not recoverable zones with zeroes), then run
>>fsck on the created image.
> 
> 
>     unluckly I can't. it's a 160 GiB partition and I don't have spare
> space.
> 
>