Hot answers tagged

7

All union filesystems with read-only and read-write branches use some form of "whiteout" marker on a read-write branch to suppress a file that exists on a read-only branch. AUFS is no different. For AUFS, the whiteout markers are files called: .wh.<filename> located in the same directory where the deleted file used to live, and where <filename>...


3

Fedora tries to not deviate very far from the "mainline" upstream kernel from kernel.org. AuFS isn't in that kernel, so it isn't in Fedora. We do, however, have an option: OverlayFS. Upstream documentation is available on kernel.org, and here's some quick examples on Fedora. And, as pretty much always, the Arch Linux documentation is excellent and (as ...


3

Aufs is very old, the today's variant is overlayfs. mount -t overlay overlay -o lowerdir=/mnt/dd1/1/:/mnt/dd2/1/ /var/www/3/ It will be read only.


2

In an aufs union-mount, a branch and the mountpoint cannot be the same. Use this: mount -t aufs -o dirs=/mnt/home/lucyvanpelt=rw:/home/schroeder=ro none /path/to/mountpoint Normally if you want to merge 2 directories, you have to specify what should happen if something is written on it. As you can see, you can specify each branch with rw (readwrite) or ro (...


2

Each underlying filesystem is assigned a precedence. If there are duplicate filenames, the one from the higher precedence filesystem is the visible one, the others are hidden. See https://superuser.com/questions/326190/how-does-unionfs-work


2

Here are some thoughts - I am still learning this and will update this as I go. How to choose the union filesystem There are two ways to look at this: How do the features of each one compare? For some common use cases, which one should I choose? I'll compare unionfs / unionfs-fuse / overlayfs / aufs / mergerfs, the latter being a replacement for mhddfs. ...


1

You could use MergerFS for this. With this you need to mount your disks as you would do normally and use MergerFS to mount one on top of another. Excellent podcast episode with the developer of MergerFS


1

The command to mount an aufs filesystem is mount. The filesystem type (shown in /proc/mounts or in the output of mount with no arguments) is aufs, not fuse. This shows that aufs is a filesystem of its own, it doesn't use FUSE. It's implemented with its own kernel driver, not through the FUSE kernel driver. If you want to use aufs as a non-root user, root ...


1

In researching this the answer appears to be: no. In looking at the man page for aufs I don't see any options that would allow it to mount as anything but the root user. In looking at the filesystems that libfuse supports I don't see aufs listed there either. Lastly if you look at the userspace filesystems it's not listed their either: Filesystem in ...


1

Answering to: 'Is there some way to make the cache work properly?' (well to actually make aufs writes work properly) when mounting the aufs, it seems to ONLY work properly if we use -o sync toguether with br like in -o sync,br="..." now it is finally working great concerning making write updates ready, even timestamps! PS.: The problem still happens at ...


1

Transform the input into the required syntax and splice it into the command line with a command substitution. dirs_with_photos="$(<~/dirs_with_photos.txt tr '\n' :)" if [ -n "$dirs_with_photos" ]; then unionfs-fuse "${dirs_with_photos%:}" /photos fi With mount_unionfs you need to issue one mount command per directory. You can use a loop around the ...


1

It sounds to me like you have done everything right, so I would suggest filing a bug against aufs. PS: Kontrollfreak has done that already, and the fix is to use the dirperm1 mount option, according to http://sourceforge.net/p/aufs/bugs/21/#1293 . Thanks for your research @Kontrollfreak .


1

I'm working through this same issue now. This happens because vfs is not a true union file system (like aufs), so every incremental image in the image you restore is restored to its full size. See this issue for more details: https://github.com/docker/docker/issues/14040


Only top voted, non community-wiki answers of a minimum length are eligible