fsck.reiser4 errors

fsck.reiser4 errors

[Jedi Ninja]

trinity root # fsck.reiser4 /dev/hda8
 *** note about $25 support *** 

Fscking the /dev/hda8 block device.
Will check the consistency of the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Will use (default) params.
Continue?
(Yes/No): Yes
Fatal: Device operation "read" isn't implemented.
Fatal: Can't read master super block.
Fatal: Failed to open teh master super block.
Fatal: Cannot open the FileSystem on (/dev/hda8).
Segmentation fault 

trinity root # ls -l /dev/hda8
lr-xr-xr-x    1 root ... /dev/hda8 -> ide/host0/bus0/target0/lun0/part8
trinity root # ls -l /dev/ide/host0/bus0/target0/lun0/part8
brw-------    1 root ... /dev/ide/... 

 

I get the same errors if I try to fsck the long (devfs-style) device. 

 --check
 --fix
 --build-sb
 --build-fs 

None of these work, though --build-sb says it can't find the superblock 
(after the error about read not being implemented) and offers to make a new 
one. 

I can read from the device, even make a backup, but mounting it causes 
problems (mount hangs forever).  I know I'm not supposed to keep important 
stuff there, and I do make backups, but there's still several hours of work 
on that partition.  I'm certainly willing to spend the $25 if you think you 
can get this back.  (In truth, I'd kind of rather break out the hex editor 
or a grep of the raw filesystem than nuke that partition.) 

(No PGP signature because keyring was on that partition.)

Re: fsck.reiser4 errors

[Vitaly Fertman]

Hello, 

On Saturday 13 December 2003 21:02, Jedi Ninja wrote:
> trinity root # fsck.reiser4 /dev/hda8
>  *** note about $25 support ***
>
> Fscking the /dev/hda8 block device.
> Will check the consistency of the Reiser4 SuperBlock.
> Will check the consistency of the Reiser4 FileSystem.
> Will use (default) params.
> Continue?
> (Yes/No): Yes
> Fatal: Device operation "read" isn't implemented.
> Fatal: Can't read master super block.
> Fatal: Failed to open teh master super block.
> Fatal: Cannot open the FileSystem on (/dev/hda8).
> Segmentation fault

hm, this is strange. what reiser4progs do you use?
there are a lot of fixes have been made recently, I will send 
you the uptodate code in the next email, you should try it first.

-- 
Thanks,
Vitaly Fertman

Re: fsck.reiser4 errors

[David Masover]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vitaly Fertman wrote:

> ...
>
>hm, this is strange. what reiser4progs do you use?
>there are a lot of fixes have been made recently, I will send 
>you the uptodate code in the next email, you should try it first.
>  
>

I have the latest from the website, as of November 11, I think.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBP953kwisZLIF6uqOAQKeDQ//ToJDCWFnfU8ZabPMZ3ayFYr0MkqQZc0O
qAtfjkfZpY9wSJhaqOvgJCkZf+GEMB8JZW5FneDc/CYjRnGQGUXREsRTAwvRgXM3
/qCaQebp0IUCToHpXcJDPed0V2FwIFT1uzk3s+05V24aZkuRg9wfByRHfTdy7gXE
da+59j4zvg+hg5rVzbWxkDq1m6AjOk4o7LgMgsqmG3eedgrkGQFTFxUOiuREshQF
wmGybLqppWE1TG83k0n+D8gOcGhvvQtBO4MsGm2bcE4pguC3HqNeTRAdx5KUr2D5
wN9uojQHA0UL3ie2ybiKkkOZ9IVYUoa2lPk6gDvERZiuF2h+C/ba8f2kcYmgmRAg
JVRtpCxib8MWTy9VNjkdQwUke3ReQiL3UchDUR3ECeA9cQW+H+HXa7LectrcEDpL
nX7mOobLs/uj2dbJ6JIhow6G+Mg/cM/drPABb9udY6mZRIV678kVDrbMzu8fwu4d
Etz/sFMSBD+8/acybrNWQuspsqNsBoXGgKb4iFugcR/1fDewbSxhrkETDPTe+WcH
MpRflfR7MtSo7Q1QnxR+Skj7+2IPkz6GfMj2MzzitjmrXQ9peSwbDF+EIu1SOurw
WCVx0lyP5/DMsxx0lm8A2X899CW5ooL8ld0D0iZWnJ4OmETxbnkRjcN/aAYiSWgP
O/1J99wuNKE=
=oRGf
-----END PGP SIGNATURE-----

Re: fsck.reiser4 errors

[Hans Reiser]

On Tuesday 16 December 2003 06:10, David Masover wrote:
> Vitaly Fertman wrote:
> > ...
> >
> >hm, this is strange. what reiser4progs do you use?
> >there are a lot of fixes have been made recently, I will send
> >you the uptodate code in the next email, you should try it first.
>
> I have the latest from the website, as of November 11, I think.
Sounds like Vitaly needs to release a new snapshot.  Nikita, aren't we overdue 
for a new snapshot for the kernel code also?

Re: fsck.reiser4 errors

[Nikita Danilov]

Hans Reiser writes:
 > On Tuesday 16 December 2003 06:10, David Masover wrote:
 > > Vitaly Fertman wrote:
 > > > ...
 > > >
 > > >hm, this is strange. what reiser4progs do you use?
 > > >there are a lot of fixes have been made recently, I will send
 > > >you the uptodate code in the next email, you should try it first.
 > >
 > > I have the latest from the website, as of November 11, I think.
 > Sounds like Vitaly needs to release a new snapshot.  Nikita, aren't we overdue 
 > for a new snapshot for the kernel code also?

Probably. But reiser4 is not stable enough right now to release it.

 > 

Nikita.

Re: fsck.reiser4 errors

[Vitaly Fertman]

On Tuesday 16 December 2003 06:28, Hans Reiser wrote:
> On Tuesday 16 December 2003 06:10, David Masover wrote:
> > Vitaly Fertman wrote:
> > > ...
> > >
> > >hm, this is strange. what reiser4progs do you use?
> > >there are a lot of fixes have been made recently, I will send
> > >you the uptodate code in the next email, you should try it first.
> >
> > I have the latest from the website, as of November 11, I think.
>
> Sounds like Vitaly needs to release a new snapshot.  Nikita, aren't we
> overdue for a new snapshot for the kernel code also?

right, but I still have a pair of not fixed bugs. and Yura has some also.
debugging...

-- 
Thanks,
Vitaly Fertman

Re: fsck.reiser4 errors

[Hans Reiser]

Vitaly Fertman wrote:

>On Tuesday 16 December 2003 06:28, Hans Reiser wrote:
>  
>
>>On Tuesday 16 December 2003 06:10, David Masover wrote:
>>    
>>
>>>Vitaly Fertman wrote:
>>>      
>>>
>>>>...
>>>>
>>>>hm, this is strange. what reiser4progs do you use?
>>>>there are a lot of fixes have been made recently, I will send
>>>>you the uptodate code in the next email, you should try it first.
>>>>        
>>>>
>>>I have the latest from the website, as of November 11, I think.
>>>      
>>>
>>Sounds like Vitaly needs to release a new snapshot.  Nikita, aren't we
>>overdue for a new snapshot for the kernel code also?
>>    
>>
>
>right, but I still have a pair of not fixed bugs. and Yura has some also.
>debugging...
>
>  
>
Ok, then let us try for next Monday, if the code is ready by then.

-- 
Hans

Re: fsck.reiser4 errors

[Jedi Ninja]

I recently reproduced the same bug, once in /tmp, and later in /home (ack).  
I have time to (try to) debug it now.  It's possible that I have some bad 
blocks, though.  How do I check for that? 

As of this writing, reiser4progs won't compile. 

If I configure without --disable-Werror (as in, -Werror is enabled), I get 
warnings that become errors about implicit, redundant, and then previous 
definitions of aal_exception_error. 

If I configure with --disable-Werror, make gives me errors about 
EXCEPTION_FATAL, EXCEPTION_YESNO, and EXCEPTION_NO being undefined in 
format40_repair.c 

I can't paste the exact errors just now, as I am writing this from lynx (my 
/home was blown away). 

This is depressing.  I'm off to the PS2 for a day or so, then I'll re-clone 
and try again. 

(I'm new to bk, so I guessed:  bk clone bk://somewhere?) 

Vitaly Fertman writes: 

> On Monday 15 December 2003 16:35, Vitaly Fertman wrote:
>> Hello, 
>>
>> On Saturday 13 December 2003 21:02, Jedi Ninja wrote:
>> > trinity root # fsck.reiser4 /dev/hda8
>> >  *** note about $25 support ***
>> >
>> > Fscking the /dev/hda8 block device.
>> > Will check the consistency of the Reiser4 SuperBlock.
>> > Will check the consistency of the Reiser4 FileSystem.
>> > Will use (default) params.
>> > Continue?
>> > (Yes/No): Yes
>> > Fatal: Device operation "read" isn't implemented.
>> > Fatal: Can't read master super block.
>> > Fatal: Failed to open teh master super block.
>> > Fatal: Cannot open the FileSystem on (/dev/hda8).
>> > Segmentation fault 
>>
>> hm, this is strange. what reiser4progs do you use?
>> there are a lot of fixes have been made recently, I will send
>> you the uptodate code in the next email, you should try it first.
> 
> ah, would you clone our  bk://bk.namesys.com/bk/reiser4progs
> and  bk://bk.namesys.com/bk/libaal repositories? The code is 
> much better than in the last snapshot. 
> 
> you will need to run the following for the libaal:
> ./prepare
> ./configure
> make
> make install
> ldconfig 
> 
> and 
> ./prepare
> ./configure
> make 
> 
> for the reiser4progs 
> 
> clean the previously installed libaal version first. 
> 
> email me about the results please. 
> 
> -- 
> Thanks,
> Vitaly Fertman
 

Re: fsck.reiser4 errors

[Vitaly Fertman]

On Saturday 20 December 2003 20:24, Jedi Ninja wrote:
> I recently reproduced the same bug, once in /tmp, and later in /home (ack).

what same bug? That mounting hands forever? Or smth with fsck.reiser4?

> I have time to (try to) debug it now.  It's possible that I have some bad
> blocks, though.  How do I check for that?

/sbin/badblocks can reveal them.

> As of this writing, reiser4progs won't compile.
>
> If I configure without --disable-Werror (as in, -Werror is enabled), I get
> warnings that become errors about implicit, redundant, and then previous
> definitions of aal_exception_error.

you should install the latest libaal first. And the recent version has
--enable-Werror instread, it is disabled by default now.

> If I configure with --disable-Werror, make gives me errors about
> EXCEPTION_FATAL, EXCEPTION_YESNO, and EXCEPTION_NO being undefined in
> format40_repair.c
>
> I can't paste the exact errors just now, as I am writing this from lynx (my
> /home was blown away).
>
> This is depressing.  I'm off to the PS2 for a day or so, then I'll re-clone
> and try again.
>
> (I'm new to bk, so I guessed:  bk clone bk://somewhere?)

bk clone bk://something, it will be created in the current directory.

bk clone bk://bk.namesys.com/bk/libaal
bk clone bk://bk.namesys.com/bk/reiser4progs

-- 
Thanks,
Vitaly Fertman

fsck.reiser4 errors

[Bob Vincent]

I've been playing around with reiser4 on a non-critical machine at work,
and managed to corrupt a 20-gig reiser4 partition.

I've run fsck.reiser4 several times to no avail; finally downloaded
and compiled the 2.6.3-internal-testing-going-on version of the utils.

(much later...)

Well, unlike the other versions; this one completed the fsck okay.

Just wondering what the following message means?

  Warning: Can't find stat data extension plugin by its id 0x4.

I see it quite often.

-- 
Robert August Vincent, II
(pronounced "Bob" or "Bob-Vee")
The web is like usenet, but
the elephants are untrained.

Re: fsck.reiser4 errors

[Vitaly Fertman]

Hello,

On Wednesday 25 February 2004 02:41, Bob Vincent wrote:
> I've been playing around with reiser4 on a non-critical machine at work,
> and managed to corrupt a 20-gig reiser4 partition.
>
> I've run fsck.reiser4 several times to no avail; finally downloaded
> and compiled the 2.6.3-internal-testing-going-on version of the utils.
>
> (much later...)
>
> Well, unlike the other versions; this one completed the fsck okay.
>
> Just wondering what the following message means?
>
>   Warning: Can't find stat data extension plugin by its id 0x4.
>
> I see it quite often.

If an object is created with some non standard plugins, their ids 
are stored in the special extention of the object stat data. But this 
extention plugin is not ready in the progs yet.

-- 
Thanks,
Vitaly Fertman

Re: fsck.reiser4 errors

[Hans Reiser]

Vitaly Fertman wrote:

>Hello,
>
>On Wednesday 25 February 2004 02:41, Bob Vincent wrote:
>  
>
>>I've been playing around with reiser4 on a non-critical machine at work,
>>and managed to corrupt a 20-gig reiser4 partition.
>>
>>I've run fsck.reiser4 several times to no avail; finally downloaded
>>and compiled the 2.6.3-internal-testing-going-on version of the utils.
>>
>>(much later...)
>>
>>Well, unlike the other versions; this one completed the fsck okay.
>>
>>Just wondering what the following message means?
>>
>>  Warning: Can't find stat data extension plugin by its id 0x4.
>>
>>I see it quite often.
>>    
>>
>
>If an object is created with some non standard plugins, their ids 
>are stored in the special extention of the object stat data. But this 
>extention plugin is not ready in the progs yet.
>
>  
>
Why is fsck finding non-standard plugins on his computer?

-- 
Hans

Re: fsck.reiser4 errors

[Vitaly Fertman]

On Wednesday 25 February 2004 16:35, Hans Reiser wrote:
> Vitaly Fertman wrote:
> >Hello,
> >
> >On Wednesday 25 February 2004 02:41, Bob Vincent wrote:
> >>I've been playing around with reiser4 on a non-critical machine at work,
> >>and managed to corrupt a 20-gig reiser4 partition.
> >>
> >>I've run fsck.reiser4 several times to no avail; finally downloaded
> >>and compiled the 2.6.3-internal-testing-going-on version of the utils.
> >>
> >>(much later...)
> >>
> >>Well, unlike the other versions; this one completed the fsck okay.
> >>
> >>Just wondering what the following message means?
> >>
> >>  Warning: Can't find stat data extension plugin by its id 0x4.
> >>
> >>I see it quite often.
> >
> >If an object is created with some non standard plugins, their ids
> >are stored in the special extention of the object stat data. But this
> >extention plugin is not ready in the progs yet.
>
> Why is fsck finding non-standard plugins on his computer?

fsck found 4th bit set in the extension mask for this file, not non-standard 
plugins. 

As I know Bob could call ioctl(UNPACK) on this file, probably smth else?
Another reason is a corruption.

-- 
Thanks,
Vitaly Fertman

Re: fsck.reiser4 errors

[Hans Reiser]

Vitaly Fertman wrote:

>On Wednesday 25 February 2004 16:35, Hans Reiser wrote:
>  
>
>>Vitaly Fertman wrote:
>>    
>>
>>>Hello,
>>>
>>>On Wednesday 25 February 2004 02:41, Bob Vincent wrote:
>>>      
>>>
>>>>I've been playing around with reiser4 on a non-critical machine at work,
>>>>and managed to corrupt a 20-gig reiser4 partition.
>>>>
>>>>I've run fsck.reiser4 several times to no avail; finally downloaded
>>>>and compiled the 2.6.3-internal-testing-going-on version of the utils.
>>>>
>>>>(much later...)
>>>>
>>>>Well, unlike the other versions; this one completed the fsck okay.
>>>>
>>>>Just wondering what the following message means?
>>>>
>>>> Warning: Can't find stat data extension plugin by its id 0x4.
>>>>
>>>>I see it quite often.
>>>>        
>>>>
>>>If an object is created with some non standard plugins, their ids
>>>are stored in the special extention of the object stat data. But this
>>>extention plugin is not ready in the progs yet.
>>>      
>>>
>>Why is fsck finding non-standard plugins on his computer?
>>    
>>
>
>fsck found 4th bit set in the extension mask for this file, not non-standard 
>plugins. 
>
>As I know Bob could call ioctl(UNPACK) on this file, probably smth else?
>Another reason is a corruption.
>
>  
>
Find the reason and fix it, or get someone else to fix it.

-- 
Hans

Re: fsck.reiser4 errors

[Vitaly Fertman]

On Wednesday 25 February 2004 22:01, Hans Reiser wrote:
> Vitaly Fertman wrote:
> >On Wednesday 25 February 2004 16:35, Hans Reiser wrote:
> >>Vitaly Fertman wrote:
> >>>Hello,
> >>>
> >>>On Wednesday 25 February 2004 02:41, Bob Vincent wrote:
> >>>>I've been playing around with reiser4 on a non-critical machine at
> >>>> work, and managed to corrupt a 20-gig reiser4 partition.
> >>>>
> >>>>I've run fsck.reiser4 several times to no avail; finally downloaded
> >>>>and compiled the 2.6.3-internal-testing-going-on version of the utils.
> >>>>
> >>>>(much later...)
> >>>>
> >>>>Well, unlike the other versions; this one completed the fsck okay.
> >>>>
> >>>>Just wondering what the following message means?
> >>>>
> >>>> Warning: Can't find stat data extension plugin by its id 0x4.
> >>>>
> >>>>I see it quite often.
> >>>
> >>>If an object is created with some non standard plugins, their ids
> >>>are stored in the special extention of the object stat data. But this
> >>>extention plugin is not ready in the progs yet.
> >>
> >>Why is fsck finding non-standard plugins on his computer?
> >
> >fsck found 4th bit set in the extension mask for this file, not
> > non-standard plugins.
> >
> >As I know Bob could call ioctl(UNPACK) on this file, probably smth else?
> >Another reason is a corruption.
>
> Find the reason and fix it, or get someone else to fix it.

Bob, would you run
	debugfs.reiser4 -P /dev/xxx | bzip2 -c > xxx.bz2 
on a reiser4 fs and provide it for downloading when fsck.reiser4 will report 
about such unknown stat data extentions on this fs? If you did not perform any
unusual action (like the mentioned ioctl) with your files we can probably find
some bugs there.

-- 
Thanks,
Vitaly Fertman