ons 2026-08-19 klockan 12:27 -0500 skrev Paul Gilmartin: > On Wed, 19 Aug 2026 16:34:11 +0200, MANCINI Frederic > <[email protected]> wrote: > > > > > When you mount the filesystem, its root directory "replaces" the > > mount > > point, as if it where overlayed on it. > > > > You should first mount the filesystem, then set the acl. > > > I'm a novice here. What's the scope of an ACL entry? > o File? > o Directory? > o Filesystem? > o Other (specify)? > > I can have hard links to a file from multiple directories, one > searchable and > another not, according to mode bits. Then access to the file depends > on > the path I use. Do ACLs have similar behavior? > > Where is ACL information stored? > 0 In the filesystem root? > o In the inode of the directory? > o In a link to the directory? > o In a separate database? > o Other (specify)?
At least in the case of XFS on Linux, a short ACL is stored in the inode for a file (or a directory.) A list which is too long for the inode is stored in auxiliary structures as a B+-tree (and the inode has a ref to the tree.) Hard link is multiple references from entries in a directory 'file/ describing block' to the same inode (contains the same inode number.) The inode doesn't contain any information about the file or directory's 'name' Hard links is also local file system only. Radoslaw's question: yes, the info for the root directory in the file system will replace what is set on the mount point. The ACL should reappear as soon as the FS is un-mounted. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
