Hello hello :) I have this strange problem with an AUFS mount which is read-only, used to aggregate a bunch of media files for sharing over CIFS. The fstab mount is:
none /Archive aufs ro,noauto,nofail,xino=/run/aufs.xino.archive,br=/titanic/Ripped/Processed=ro:/titanic/Volumes/XD001=ro:/titanic/Volumes/XD002=ro:/titanic/Volumes/XD003=ro:/titanic/Volumes/XD004=ro:/titanic/Volumes/XD005=ro:/titanic/Volumes/XD006=ro:/titanic/Volumes/XD007=ro:/titanic/Volumes/XD008=ro:/titanic/Volumes/XD009=ro:/titanic/Volumes/XD010=ro:/titanic/Volumes/XD011=ro:/titanic/Volumes/XD012=ro:/titanic/Volumes/XD013=ro:/titanic/Volumes/XD014=ro:/titanic/Volumes/XD015=ro:/titanic/Volumes/XD016=ro:/titanic/Volumes/XD017=ro:/titanic/Volumes/XD018=ro:/titanic/Volumes/XD019=ro:/titanic/Volumes/XD020=ro:/titanic/Volumes/XD021=ro:/titanic/Volumes/XD022=ro:/titanic/Volumes/XD023=ro:/titanic/Volumes/XD024=ro:/titanic/Volumes/XD025=ro:/titanic/Volumes/XD026=ro:/titanic/Volumes/XD027=ro:/titanic/Volumes/XD028=ro:/titanic/Volumes/XD029=ro:/titanic/Volumes/XD030=ro:/titanic/Volumes/XD031=ro:/titanic/Volumes/XD032=ro:/titanic/Volumes/XD033=ro:/titanic/Volumes/XD034=ro:/titanic/Volumes/XD035=ro:/titanic/Vo lumes/XD036=ro:/titanic/Volumes/XD037=ro:/titanic/Volumes/XD038=ro:/titanic/Volumes/XD039=ro:/titanic/Volumes/XD040=ro:/titanic/Volumes/XD041=ro:/titanic/Volumes/XD042=ro:/titanic/Volumes/XD043=ro:/titanic/Volumes/XD044=ro:/titanic/Volumes/XD045=ro:/titanic/Volumes/XD046=ro:/titanic/Volumes/XD047=ro:/titanic/Volumes/XD048=ro:/titanic/Volumes/XD049=ro:/titanic/Volumes/XD050=ro:/titanic/Volumes/XD051=ro:/titanic/Volumes/XD052=ro:/titanic/Volumes/XD053=ro:/titanic/Volumes/XD054=ro:/titanic/Volumes/XD055=ro:/titanic/Volumes/XD056=ro:/titanic/Volumes/XD057=ro:/titanic/Volumes/XD058=ro:/titanic/Volumes/XD059=ro:/titanic/Volumes/XD060=ro:/titanic/Volumes/XD061=ro:/titanic/Volumes/XD062=ro:/titanic/Volumes/XD063=ro:/titanic/Volumes/XD064=ro:/titanic/Volumes/XD065=ro:/titanic/Volumes/XD066=ro:/titanic/Volumes/XD067=ro:/titanic/Volumes/XD068=ro:/titanic/Volumes/XD069=ro 0 0 Note that all resources are explicitly read-only, as is the mount itself. In these folders are music files, and I was setting up foobar2000 on my Mac to collect files from all of these places via NFS. That is, not via the AUFS mount (smb:/Archive/Music/*), but via explicit paths from the underlying volumes as exported by NFS via /titanic (nfs:/titanic/Volumes/XD063/Music, etc.). This went alright with the XD??? shares, but when I wanted to add nfs:/titanic/Ripped/Processed/Music to foobar2000, I could not access it. Trying to ls it in a terminal gave me a "stale nfs file handle" message. Obviously, I then assumed it was a problem with NFS, and started scouring the net for help. Tried noac on the client, tried restarting the server, tried rebooting the Mac, but nothing helped. The only thing that did help was to umount my aufs /Archive mountpoint on the server. I can then start samba and nfs-kernel-server and access everything just fine. If I mount /Archive again, the "Processed" folder on the underlying filesystem is once again "locked" and inaccessible via NFS. It's perfectly accessible on the server itself, though, so I'm really puzzled about what this is all about. Has any one of you experienced this? I would assume that a read-only mount would not in any way modify or lock the underlying resources... Or is there some specific mount option to ensure that? All underlying folders are on ZFS (latest native, not FUSE), and the one thing that makes the "Processed" folder different from the other ones is that is has POSIX ACLs enabled (because I rip my media from both Windows, Linux and Mac, and ACLs make it easy to make sure that everyone can read and modify what ends up there). I'm wondering if there's some incompatibility there... Btw, this is on Ubuntu 14.10, kernel 3.16.0-29-generic x64, aufs-tools 3.2+20130722-1.1 Cheerio hohohoho :) ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet
