jdm-20002 reiserfs_xattr_get: Invalid hash for xattr

jdm-20002 reiserfs_xattr_get: Invalid hash for xattr

[Christian Kujau]

Hi there,

I've just noticed the following in my logs:

REISERFS warning (device xvda3): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr 
(user.{http:%2F%2Ftwistedmatrix.com%2Fxml_namespace%2Fdav%2Fprivate%2F}quota-used) 
associated with [765 72063 0x0 SD]

and one minute later:

REISERFS warning (device xvda3): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr 
(user.{http:%2F%2Ftwistedmatrix.com%2Fxml_namespace%2Fdav%2Fprivate%2F}quota-used) 
associated with [765 72063 0x0 SD]

# find /var/ -inum 72063
/var/spool/caldavd/calendars/__uids__/afebe2f1-f51a-5859-af15-f22312ad6634

# grep xvda3 /proc/mounts
/dev/xvda3 /var reiserfs rw,nosuid,nodev,noexec,relatime,user_xattr,notail 0 0

Accessing the filesystem is still fine (lsattr(1) fails, but it's 
supposed to fail anyway, right?). This is a x86-64 Xen DomU running 
2.6.32-rc8 with:

CONFIG_REISERFS_FS=m
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y

Thanks,
Christian.
-- 
BOFH excuse #382:

Someone was smoking in the computer room and set off the halon systems.

Re: jdm-20002 reiserfs_xattr_get: Invalid hash for xattr

[Christian Kujau]

On Mon, 14 Dec 2009 at 14:44, Christian Kujau wrote:
> REISERFS warning (device xvda3): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr 
> (user.{http:%2F%2Ftwistedmatrix.com%2Fxml_namespace%2Fdav%2Fprivate%2F}quota-used) 
> associated with [765 72063 0x0 SD]

Oh, of course the archives have them as well:

http://www.mail-archive.com/reiserfs-list@namesys.com/msg16215.html

But being an old posting (from 2004) I thought I should post anyway, as 
it's still an issue with 2.6.32, apparently. I take it that reiserfs can't 
do anything about it, right? However, it should be noted that there were 
no device errors logged - and I wonder *why* reiserfs was unable to write 
the xattr entry to disk / what corrupted the xattr entry in the first 
place.

Christian.
-- 
BOFH excuse #382:

Someone was smoking in the computer room and set off the halon systems.

Re: jdm-20002 reiserfs_xattr_get: Invalid hash for xattr

[Christian Kujau]

On Mon, 14 Dec 2009 at 14:52, Christian Kujau wrote:
> > REISERFS warning (device xvda3): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr 
> > (user.{http:%2F%2Ftwistedmatrix.com%2Fxml_namespace%2Fdav%2Fprivate%2F}quota-used) 
> > associated with [765 72063 0x0 SD]

FWIW, reiserfsck-3.6.21 did not report any errors - I assume it's safe to 
ignore this warning, right?

Christian.
-- 
BOFH excuse #93:

Feature not yet implemented

Re: jdm-20002 reiserfs_xattr_get: Invalid hash for xattr

[Christian Kujau]

On Mon, 14 Dec 2009 at 19:12, Christian Kujau wrote:
> REISERFS warning (device xvda3): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr 
> (user.{http:%2F%2Ftwistedmatrix.com%2Fxml_namespace%2Fdav%2Fprivate%2F}quota-used) 
> associated with [765 72063 0x0 SD]

Hm, the filesystem has been created a long time ago, the mountoptions 
haven't changed but since upgrading to 2.6.32 these messages appear quite 
frequently. Does anyone have an idea how to stop them? (Apart from ripping 
out the reiserfs_warning(), I mean)

Thanks,
Christian.
-- 
BOFH excuse #403:

Sysadmin didn't hear pager go off due to loud music from bar-room speakers.

Re: jdm-20002 reiserfs_xattr_get: Invalid hash for xattr

[Jeff Mahoney]

On 12/16/2009 12:31 AM, Christian Kujau wrote:
> On Mon, 14 Dec 2009 at 19:12, Christian Kujau wrote:
>> REISERFS warning (device xvda3): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr 
>> (user.{http:%2F%2Ftwistedmatrix.com%2Fxml_namespace%2Fdav%2Fprivate%2F}quota-used) 
>> associated with [765 72063 0x0 SD]
> 
> Hm, the filesystem has been created a long time ago, the mountoptions 
> haven't changed but since upgrading to 2.6.32 these messages appear quite 
> frequently. Does anyone have an idea how to stop them? (Apart from ripping 
> out the reiserfs_warning(), I mean)

Sorry for the late response. I"m catching up to all the old messages.

The way to fix this is to remove the xattr. There's no way to sync it
back up.

-Jeff

-- 
Jeff Mahoney
SUSE Labs

Re: jdm-20002 reiserfs_xattr_get: Invalid hash for xattr

[Christian Kujau]

On Wed, 10 Feb 2010 at 16:13, Jeff Mahoney wrote:
> > Hm, the filesystem has been created a long time ago, the mountoptions 
> > haven't changed but since upgrading to 2.6.32 these messages appear quite 
> > frequently. Does anyone have an idea how to stop them? (Apart from ripping 
> > out the reiserfs_warning(), I mean)
> 
> Sorry for the late response. I"m catching up to all the old messages.
> 
> The way to fix this is to remove the xattr. There's no way to sync it
> back up.


You mean "to remove the xattr from the files in question" or "to remove 
xattr from ReiserFS because it's buggy? ;-)

Sure, I'll remove the xattrs from the files, but new warnings for other 
files will appear and reiserfsck still doesn't find anything wrong with 
the filesystem. I'm not sure how to reproduce this reliably and no one 
seems to know why these messages appear in the first place...

Thanks,
Christian.
-- 
BOFH excuse #95:

Pentium FDIV bug

Re: jdm-20002 reiserfs_xattr_get: Invalid hash for xattr

[Jeff Mahoney]

On 02/10/2010 07:53 PM, Christian Kujau wrote:
> On Wed, 10 Feb 2010 at 16:13, Jeff Mahoney wrote:
>>> Hm, the filesystem has been created a long time ago, the mountoptions 
>>> haven't changed but since upgrading to 2.6.32 these messages appear quite 
>>> frequently. Does anyone have an idea how to stop them? (Apart from ripping 
>>> out the reiserfs_warning(), I mean)
>>
>> Sorry for the late response. I"m catching up to all the old messages.
>>
>> The way to fix this is to remove the xattr. There's no way to sync it
>> back up.
> 
> 
> You mean "to remove the xattr from the files in question" or "to remove 
> xattr from ReiserFS because it's buggy? ;-)
> 
> Sure, I'll remove the xattrs from the files, but new warnings for other 
> files will appear and reiserfsck still doesn't find anything wrong with 
> the filesystem. I'm not sure how to reproduce this reliably and no one 
> seems to know why these messages appear in the first place...

Well "buggy" depends on whether you're seeing this problem on new xattrs
or just ones that have been around for some time. A while ago, I changed
the xattr code to be entirely journaled so that it isn't sensitive to
unexpected poweroffs, etc. If you're seeing corruption on new xattrs,
then that needs to be looked into.

There probably should be support in reiserfsck for xattrs, but I just
haven't had the time for it.

To locate all the broken xattrs on your system, run this as root and
then check your log afterwards:

getfattr -d -R -m '.*' /

-Jeff

-- 
Jeff Mahoney
SUSE Labs

Re: jdm-20002 reiserfs_xattr_get: Invalid hash for xattr

[Christian Kujau]

On Thu, 11 Feb 2010 at 09:36, Jeff Mahoney wrote:
> Well "buggy" depends on whether you're seeing this problem on new xattrs
> or just ones that have been around for some time.

When I started to see the problem (Dec 2009) I removed the xattrs from the 
files in question - only to see new warnings for other files reported. 
However, I cannot tell *when* these xattr have been assigned to these 
files. For that to track I could probably monitor the filesystem, generate 
a daily list of files-with-xattrs and then wait if one of these files gets 
reported with "Invalid hash for xattr" later on.

> To locate all the broken xattrs on your system, run this as root and
> then check your log afterwards:
> getfattr -d -R -m '.*' /

Yes, thanks. I just used "find" to look for the reported inodes that were 
included in the error message and getfattr did not generate any more 
warnings after I removed those xattrs.

Thanks,
Christian.
-- 
BOFH excuse #351:

PEBKAC (Problem Exists Between Keyboard And Chair)