From: Jeff Mahoney <jeffm@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Alexander Zarochentsev <zam@namesys.com>,
reiserfs-list@namesys.com, Graham Leggett <minfrin@sharp.fm>
Subject: Re: Undeletable files...
Date: Mon, 17 Apr 2006 11:26:05 -0400 [thread overview]
Message-ID: <4443B38D.1010103@suse.com> (raw)
In-Reply-To: <44445AED.6080905@namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hans Reiser wrote:
> Jeffrey Mahoney wrote:
>
>> Hans Reiser wrote:
>>
>>
>>> Sounds like acls or acl bugs.
>>>
>>>
>> Or not, since ACLs weren't enabled on the mount.
>
> What happens if acls are used on one mount and not on another?
To clarify, ACLs are a per-super feature. For this example, there
weren't multiple mount points with different options, so per-super and
per-mount are one and the same.
If you mean if ACLs are enabled on one file system and not on another,
nothing unusual will happen. The behavior for copying from one FS to
another is defined.
- From ACL fs to non-ACL fs, the ACLs will be lost.
- From non-ACL fs to ACL fs, unless "preserve permissions" is set, the
files will inherit from an optional default ACL.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEQ7ONLPWxlyuTD7IRAqzPAJwLuf5BX2IlUuAnMJ0eAyqRO1lFCgCgkaPg
eugu4Q/rk56Qryz6JQ8bJEg=
=urun
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-04-17 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 19:14 Undeletable files Graham Leggett
2006-04-15 19:58 ` Alexander Zarochentsev
[not found] ` <444353D7.5000302@namesys.com>
2006-04-16 21:10 ` Jeffrey Mahoney
[not found] ` <44445AED.6080905@namesys.com>
2006-04-17 15:26 ` Jeff Mahoney [this message]
[not found] ` <44450FCE.4060608@namesys.com>
2006-04-18 4:58 ` Jeff Mahoney
[not found] ` <44452C44.9040000@namesys.com>
2006-04-18 13:53 ` 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=4443B38D.1010103@suse.com \
--to=jeffm@suse.com \
--cc=minfrin@sharp.fm \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=zam@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.