From: "Jörg Spilker" <js@jetsys.de>
To: reiserfs-list@namesys.com
Subject: warning: Invalid hash for xattr (system.posix_acl_access) associated with [1070 1541 0x0 SD] after extending device
Date: Wed, 17 Nov 2004 19:31:49 +0100 [thread overview]
Message-ID: <200411171931.52943.js@jetsys.de> (raw)
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
next reply other threads:[~2004-11-17 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 18:31 Jörg Spilker [this message]
2004-11-17 22:12 ` warning: Invalid hash for xattr (system.posix_acl_access) associated with [1070 1541 0x0 SD] after extending device Jeff Mahoney
2004-11-21 8:05 ` Jörg Spilker
2004-11-21 17:06 ` Hans Reiser
2004-11-21 17:31 ` Jeff Mahoney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200411171931.52943.js@jetsys.de \
--to=js@jetsys.de \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.