From: Jeff Mahoney <jeffm@suse.com>
To: Joachim Reichelt <Reichelt@gbf.de>
Cc: reiserfs-list@namesys.com
Subject: Re: Lost ACL
Date: Fri, 13 Feb 2004 13:44:54 -0500 [thread overview]
Message-ID: <402D1B26.3040009@suse.com> (raw)
In-Reply-To: <402CE469.4010809@gbf.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Joachim Reichelt wrote:
| Dear all,
|
| on SuSE 8.1 we have a fileserver with acl's on 500GB on a hardware raid.
| Now we had to powerdown the system. The controler seems to have not
| properly written all data to disk. So i had to do a
| reiserfsck --fix-fixable /dev/sda8
|
| This did nearly the whole job, but left me with a tree
| ./.reiserfs_privat/xattr/ (size of dir is ~38MB)
| The files thereis seems to be two hex numbers seperated by a dot e.g.
| 12E63C.24C58
| and no acl.
| What can I do to get acl back?
|
The .reiserfs_priv/xattr hierarchy is how my xattr/acl code stores the
ACLs without a disk format change. The hex numbers are
<objectid>.<generation number>, and then the individual xattrs are
stored inside that directory with their name as the filenames.
This directory is hidden (and used to find ACLs) when ACLs or xattrs are
enabled. Is your filesystem mounted with -oacl?
- -Jeff
- --
Jeff Mahoney
SuSE Labs
jeffm@suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFALRslLPWxlyuTD7IRApbCAJ9f3B9rMpyv0Q56SRsMWsWuyTBA8ACgk6Uc
wp668pLEYc8+fFvKFqzJ27M=
=nqru
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-02-13 18:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 14:51 Lost ACL Joachim Reichelt
2004-02-13 18:44 ` Jeff Mahoney [this message]
2004-02-13 18:48 ` Nikita Danilov
2004-02-13 20:47 ` Jeff Mahoney
2004-02-19 16:56 ` Joachim Reichelt
2004-02-19 17:13 ` Jeff Mahoney
2004-02-19 17:33 ` Jeff Mahoney
2004-02-20 8:03 ` Joachim Reichelt
2004-02-20 8:07 ` Joachim Reichelt
2004-02-16 7:38 ` Joachim Reichelt
2004-02-19 17:29 ` 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=402D1B26.3040009@suse.com \
--to=jeffm@suse.com \
--cc=Reichelt@gbf.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.