warning: Invalid hash for xattr (system.posix_acl_access) associated with [1070 1541 0x0 SD] after extending device

warning: Invalid hash for xattr (system.posix_acl_access) associated with [1070 1541 0x0 SD] after extending device

[Jörg Spilker]

Hello,

i recently extended a LVM device and also resized the reiserfs. Now i find 
lots of messages like this in my log:

Nov 17 04:08:59 lotus kernel: ReiserFS: dm-5: warning: Invalid hash for xattr 
(system.posix_acl_access) associated with [1070 1541 0x0 SD]
Nov 17 04:08:59 lotus kernel: ReiserFS: dm-5: warning: Invalid hash for xattr 
(system.posix_acl_access) associated with [1070 1541 0x0 SD]

they don't seem to cause any harm. reiserfsck doesn't report any errors. Can i 
fix the problem without reformatting the whole device?

Kernel is the original kernel from SuSE 9.2 (with all available patches 
2.6.8-24.3) and the reiserfs tools coming with the distribution.

Greetings, Jörg

Re: warning: Invalid hash for xattr (system.posix_acl_access) associated with [1070 1541 0x0 SD] after extending device

[Jeff Mahoney]

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

Jörg Spilker wrote:
| Hello,
|
| i recently extended a LVM device and also resized the reiserfs. Now i
find
| lots of messages like this in my log:
|
| Nov 17 04:08:59 lotus kernel: ReiserFS: dm-5: warning: Invalid hash
for xattr
| (system.posix_acl_access) associated with [1070 1541 0x0 SD]
| Nov 17 04:08:59 lotus kernel: ReiserFS: dm-5: warning: Invalid hash
for xattr
| (system.posix_acl_access) associated with [1070 1541 0x0 SD]
|
| they don't seem to cause any harm. reiserfsck doesn't report any
errors. Can i
| fix the problem without reformatting the whole device?
|
| Kernel is the original kernel from SuSE 9.2 (with all available patches
| 2.6.8-24.3) and the reiserfs tools coming with the distribution.
|
| Greetings, Jörg
|

It's definately fixable without reformatting.

When I designed the on-disk ACL/xattr format, I built in a magic number
and a checksum to catch things like corrupted entries wreaking havoc on
the system. That's what you're hitting.

Somehow, an entry wasn't fully written to disk or was corrupted somehow.
~ Whether it was part of the extending process or not, I couldn't tell you.

You can use debugreiserfs to track down the file with that key by using
debugreiserfs -d <device> and looking for the objectid. Once you find
the directory listing with that key, you should be able to find the file.

When you've located the filename, a setfattr -x system.posix_acl_access
<file> followed by the appropriate setfacl command will reset the ACL.

- -Jeff


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

iD8DBQFBm8zLLPWxlyuTD7IRAss6AJ9ELG9BbPjgqF78dG5aXrgZ4MQpGQCeLZ7o
pmbxrva+nXv6MU3w0UQ1Y78=
=wpwc
-----END PGP SIGNATURE-----

Re: warning: Invalid hash for xattr (system.posix_acl_access) associated with [1070 1541 0x0 SD] after extending device

[Jörg Spilker]

Am Mittwoch, 17. November 2004 23:12 schrieben Sie:

Hello Jeff,

> You can use debugreiserfs to track down the file with that key by using
> debugreiserfs -d <device> and looking for the objectid. Once you find
> the directory listing with that key, you should be able to find the file.
>
> When you've located the filename, a setfattr -x system.posix_acl_access
> <file> followed by the appropriate setfacl command will reset the ACL.

thanks for your help. I could fix the problem using debugreiserfs

Greetings, Jörg

btw: your email is bouncing (unknown user).

Re: warning: Invalid hash for xattr (system.posix_acl_access) associated with [1070 1541 0x0 SD] after extending device

[Hans Reiser]

Jörg Spilker wrote:

>Am Mittwoch, 17. November 2004 23:12 schrieben Sie:
>
>Hello Jeff,
>
>  
>
>>You can use debugreiserfs to track down the file with that key by using
>>debugreiserfs -d <device> and looking for the objectid. Once you find
>>the directory listing with that key, you should be able to find the file.
>>
>>When you've located the filename, a setfattr -x system.posix_acl_access
>><file> followed by the appropriate setfacl command will reset the ACL.
>>    
>>
>
>thanks for your help. I could fix the problem using debugreiserfs
>
>Greetings, Jörg
>
>btw: your email is bouncing (unknown user).
>
>
>  
>
I am concerned that this constitutes ignoring a bug report by fixing the 
symptoms and not finding the bug.

Re: warning: Invalid hash for xattr (system.posix_acl_access) associated with [1070 1541 0x0 SD] after extending device

[Jeff Mahoney]

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

Jörg Spilker wrote:
| Am Mittwoch, 17. November 2004 23:12 schrieben Sie:
|
| Hello Jeff,
|
|
|>You can use debugreiserfs to track down the file with that key by using
|>debugreiserfs -d <device> and looking for the objectid. Once you find
|>the directory listing with that key, you should be able to find the file.
|>
|>When you've located the filename, a setfattr -x system.posix_acl_access
|><file> followed by the appropriate setfacl command will reset the ACL.
|
|
| thanks for your help. I could fix the problem using debugreiserfs

Great!

| btw: your email is bouncing (unknown user).

Yeah, it seems that my @novell.com address has been a black hole for the
past few days. Hopefully it will be fixed soon.

- -Jeff

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

iD8DBQFBoNDZLPWxlyuTD7IRAhxEAJ44ZkvDQTlBkJ91DNPIYBlE1qARLgCcC3yy
hafHa02Cn1GtoxCrvUndHGE=
=5gv3
-----END PGP SIGNATURE-----