From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 14826] New: jdm-20002 reiserfs_xattr_get: Invalid hash for xattr
Date: Thu, 17 Dec 2009 09:00:22 GMT [thread overview]
Message-ID: <bug-14826-695@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=14826
Summary: jdm-20002 reiserfs_xattr_get: Invalid hash for xattr
Product: File System
Version: 2.5
Kernel Version: 2.6.32
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ReiserFS
AssignedTo: reiserfs-devel@vger.kernel.org
ReportedBy: lists@nerdbynature.de
Regression: Yes
Note: this has been reported on reiserfs-devel by me as well:
http://www.spinics.net/lists/reiserfs-devel/msg02009.html
After upgrading to 2.6.32, the following messages appear in the logs:
REISERFS warning (device xvda3): jdm-20002 reiserfs_xattr_get: Invalid hash for
xattr
(user.{http:%2F%2Ftwistedmatrix.com%2Fxml_namespace%2Fdav%2F}getcontentmd5)
associated with [765 43775 0x0 SD]
The filesystem has been created a long time ago, the mountoptions haven't
changed either:
$ grep reiser /proc/mounts
/dev/xvda3 /var reiserfs rw,nosuid,nodev,noexec,relatime,user_xattr,notail 0 0
So far, the messages are not flooding the logs but are triggered a few times a
day:
$ uptime
09:32:48 up 2 days, 6:30, 10 users, load average: 0.95, 0.31, 0.11
$ dmesg | grep -c jdm-20002
35
A full dmesg and the .config is available on:
http://nerdbynature.de/bits/2.6.33-git/jdm-20002/
Although cosmetical (right?) and and probably fixable by removing/resetting the
xattr flags, this should not happen.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2009-12-17 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 9:00 bugzilla-daemon [this message]
2009-12-17 9:01 ` [Bug 14826] jdm-20002 reiserfs_xattr_get: Invalid hash for xattr bugzilla-daemon
2010-02-14 0:37 ` bugzilla-daemon
2010-03-18 13:22 ` bugzilla-daemon
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=bug-14826-695@http.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).