New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OverlayFS #4
Comments
Your umount script it doing something wrong. Apart from that I did not fully understand the requirements to make changes to lower directory. |
Hey your right doh! I hadn't really looked its the df as they have now no longer directly mounted to a zram device. |
Right just be aware that cp may not sync deletes and renames in upper fs correctly to lower. You should test this. It will certainly not sync renamed directory correctly if redirect_dir option is enabled. |
https://github.com/kmxz/overlayfs-tools? Apols Amir but if on stop I |
overlayfs-tools seems like a nice project. never tried. it does not seem to support redirect_dir, |
https://github.com/amir73il/overlayfs/wiki/Overlayfs-TODO#features |
I would suggest trying out https://github.com/kmxz/overlayfs-tools. It supports the default overlayfs features and you can extend it to extra features if you need to. |
Ok some reading needed as my head is spinning slightly. |
I did a bit of tidying and included overlayfs-tools which is great. Just wondering can I enable redirect_dir via sys/module/overlay/parameters/* rather than edit /boot/cmdline.txt? I am all ears about redirect_dir also wondering if snapshots could be used for what was the now deleted
Do you think snapshots will get included in the kernel? To be honest the `write' syncToDisk 'snapshot' function is not hugely important and from starting with log2ram always been slightly bemused as to why? |
You can change redirect_dir default via sys/module/overlay/parameters/ overlayfs-tools does not seem to support redirect_dir. You might want to contact the author to ask about plans to support redirect_dir. I do not know the author and never used the tools myself. I am not sure how overlayfs snapshots are related to syncToDisk functionality. |
Is now a mount option. Yeah I was thinking maybe could mount as upper merge down then mount updated lower with zram upper on next boot (with snapshots rotate down that is). |
Thanks for this project btw. I'm also interested in finding an atomic copy_down and will keep tabs on the collective progress here! I noticed you turned off redirect_dir in your latest commits, curious why? Did you run into specific problems with directory renames in lower? |
Purely the because the only tool for offline merge was written before that addition to OverlayFS. amir and the FS kernel file system guys know about the tool shortage as opposed to Aufs, but hoping for some suggestions but nothing seemed to be offered. |
has anyone considered using rsync ? |
I agree with using rsync to sync. |
Think it became a default or I have made a mistake, with it being default I decicided to leave out so implementers could decide. https://github.com/amir73il is the man to ask about all this as active in the dev group. |
@StuartIanNaylor you should address your question to containers developers, because they have the most to gain from overlayfs tools. I have been involved with implementing many overlayfs features in the kernel for the past couple of years (redirect_dir,index,nfs_export,xino). All of these features bring benefits to end users, but AFAIK, they are all still disabled by default in containers (e.g. docker) because lack of tools support (e.g. migration/import/export). |
Thanks amir as its so frustrating as OverlayFS is brilliant but it does lack tools. |
I like the use of OverlayFS as large directory structures that would not be really possible to copy on the initial sync especially at boot become valid.
Like most things I am an OverlayFS noob and confused by the 2nd overlay directive copied from examples.
In some examples it is none and if you do a DF it seems to set the filesystem type description and a umount of the OverlayFS mount gives an output that the /opt/overlay mount doesn't exist.
I am struggling to find any direct documentation for that directive of as without it will look for a fstab entry.
mount --verbose --types overlay -o lowerdir=$BIND_DIR,upperdir=/opt/zram$RAM_DEV/upper,workdir=/opt/zram$RAM_DEV/workdir
overlay
$ZRAM_DIRAlso even though it will not error writing out to lower whilst mounted is supposedly a no-no.
Aufs is spin-lock crazy mad from what I can deduce from why some distro's and kernel say no and even though it would be an instant fix to writing out to lower I am slightly reluctant to make the switch.
Also wondering in ztab if log & dir entries should have a concat device option where a singular zram device is used with the sum of disksize and mem-limit entries if 1 and not if 0.
Anyway currently thinking about these 'issues/options' but if you have some input please do.
The text was updated successfully, but these errors were encountered: