From: Jeff Mahoney <jeffm@suse.com>
To: "Jörg Spilker" <js@jetsys.de>
Cc: reiserfs-list@namesys.com
Subject: Re: warning: Invalid hash for xattr (system.posix_acl_access) associated with [1070 1541 0x0 SD] after extending device
Date: Sun, 21 Nov 2004 12:31:05 -0500 [thread overview]
Message-ID: <41A0D0D9.70306@suse.com> (raw)
In-Reply-To: <200411210905.36202.js@jetsys.de>
-----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-----
prev parent reply other threads:[~2004-11-21 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 18:31 warning: Invalid hash for xattr (system.posix_acl_access) associated with [1070 1541 0x0 SD] after extending device Jörg Spilker
2004-11-17 22:12 ` Jeff Mahoney
2004-11-21 8:05 ` Jörg Spilker
2004-11-21 17:06 ` Hans Reiser
2004-11-21 17:31 ` Jeff Mahoney [this message]
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=41A0D0D9.70306@suse.com \
--to=jeffm@suse.com \
--cc=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.