deleting file crashes kernel 2.6.8 / reiserfs 3.6

deleting file crashes kernel 2.6.8 / reiserfs 3.6

[Hannes Krueger]

Hi,

I have two files on my reiserfs, which I cannot delete. "rm" these files 
immidiately locks the kernel, no messages. I already tried reiserfsck 
--fix-fixable, but it doesn't help.

I can move these files, and copy them. I can also remove the copies. But 
overwriting or deleting results in the kernel lockup, the machine freezes.

I think these files were written during  a system crash. But how to get rid of 
them? Is the filesystem still OK? 

Any suggestions?

Its a SuSE 9.2  (2.6.8-24.20-default)



Below I inserted the output of debgreiserfs:


Filesystem state: consistency is not checked after last mounting

Reiserfs super block in block 16 on 0x303 of format 3.6 with standard journal
Count of blocks on the device: 5893776
Number of bitmaps: 180
Blocksize: 4096
Free blocks (count of blocks - used [journal, bitmaps, data, reserved] 
blocks): 1570082
Root block: 533794
Filesystem is NOT clean
Tree height: 5
Hash function used to sort names: "r5"
Objectid map size 294, max 972
Journal parameters:
        Device [0x0]
        Magic [0x1765aa13]
        Size 8193 blocks (including 1 for journal header) (first block 18)
        Max transaction length 1024 blocks
        Max batch size 900 blocks
        Max commit age 30
Blocks reserved by journal: 0
Fs state field: 0x0:
sb_version: 2
inode generation number: 1438830
UUID: d7713a05-8e46-444a-a4a3-4606023f3e01
LABEL:
Set flags in SB:
        ATTRIBUTES CLEAN

Re: deleting file crashes kernel 2.6.8 / reiserfs 3.6

[Hans Reiser]

Jeff, is this attrs related?

Hans

Hannes Krueger wrote:

>Hi,
>
>I have two files on my reiserfs, which I cannot delete. "rm" these files 
>immidiately locks the kernel, no messages. I already tried reiserfsck 
>--fix-fixable, but it doesn't help.
>
>I can move these files, and copy them. I can also remove the copies. But 
>overwriting or deleting results in the kernel lockup, the machine freezes.
>
>I think these files were written during  a system crash. But how to get rid of 
>them? Is the filesystem still OK? 
>
>Any suggestions?
>
>Its a SuSE 9.2  (2.6.8-24.20-default)
>
>
>
>Below I inserted the output of debgreiserfs:
>
>
>Filesystem state: consistency is not checked after last mounting
>
>Reiserfs super block in block 16 on 0x303 of format 3.6 with standard journal
>Count of blocks on the device: 5893776
>Number of bitmaps: 180
>Blocksize: 4096
>Free blocks (count of blocks - used [journal, bitmaps, data, reserved] 
>blocks): 1570082
>Root block: 533794
>Filesystem is NOT clean
>Tree height: 5
>Hash function used to sort names: "r5"
>Objectid map size 294, max 972
>Journal parameters:
>        Device [0x0]
>        Magic [0x1765aa13]
>        Size 8193 blocks (including 1 for journal header) (first block 18)
>        Max transaction length 1024 blocks
>        Max batch size 900 blocks
>        Max commit age 30
>Blocks reserved by journal: 0
>Fs state field: 0x0:
>sb_version: 2
>inode generation number: 1438830
>UUID: d7713a05-8e46-444a-a4a3-4606023f3e01
>LABEL:
>Set flags in SB:
>        ATTRIBUTES CLEAN
>
>
>  
>

Re: deleting file crashes kernel 2.6.8 / reiserfs 3.6

[Jeff Mahoney]

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

Hans Reiser wrote:
> Jeff, is this attrs related?

No. The kernel version is 2.6.8. The attrs changes weren't introduced
until mid-2.6.15. Also, the lockup is definitely not the pattern we've
been seeing with attrs-related problems.

Hannes -

Can you please run the following command and post (or send to me) the
resultant file? The list will most certainly not allow a file of that
size through, but it should get to me just fine.

debugreiserfs -p <dev> | gzip -c > fsmetadata.gz

This exports the metadata tree from your file system. No data will be
sent with it. Having an image of your file system should help debugging.

- -Jeff

- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFECedmLPWxlyuTD7IRAmt6AJsE5wwQpJhKaPz/qtaDUKj+i7RyPgCeOjFY
ATuy+ntmSepWooi6xj0/ga0=
=acGV
-----END PGP SIGNATURE-----