From: Jeff Mahoney <jeffm@suse.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: ReiserFS Development List <reiserfs-devel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.30-rc2: reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)
Date: Fri, 17 Apr 2009 15:26:21 -0400 [thread overview]
Message-ID: <49E8D7DD.7080907@suse.com> (raw)
In-Reply-To: <a4423d670904161223r2e026b6u903137c709318551@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alexander Beregalov wrote:
> Hi Jeff
>
> The kernel prints this message every 20seconds
> [ 836.973100]
> [ 836.983494] REISERFS warning (device sda2): jdm-20004
> reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)
> [ 836.983496]
> [ 894.203634] REISERFS warning (device sda2): jdm-20004
> reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)
> [ 894.203636]
> [ 894.205784] REISERFS warning (device sda2): jdm-20004
> reiserfs_delete_xattrs: Couldn't delete all xattrs (-13)
>
> commit a41f1a4715
>
> CONFIG_REISERFS_FS=y
> # CONFIG_REISERFS_CHECK is not set
> # CONFIG_REISERFS_PROC_INFO is not set
> # CONFIG_REISERFS_FS_XATTR is not set
>
> I did not enable XATTR before,
> should I enable it now ?
Thanks for the report. I'm taking a look at it now.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkno19wACgkQLPWxlyuTD7L9dQCeODUthInHguXbxmpmjKf2KpZB
3BAAmwTFgx4u/YlIoftrWy+x9nd8DrDO
=rdNj
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-04-17 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 19:23 2.6.30-rc2: reiserfs_delete_xattrs: Couldn't delete all xattrs (-13) Alexander Beregalov
2009-04-17 19:26 ` Jeff Mahoney [this message]
2009-04-20 14:13 ` Jeff Mahoney
2009-04-20 14:25 ` Alexander Beregalov
2009-04-20 20:42 ` Alex Romosan
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=49E8D7DD.7080907@suse.com \
--to=jeffm@suse.com \
--cc=a.beregalov@gmail.com \
--cc=linux-kernel@vger.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