problems when there are top level filesystem mount points #38
Comments
|
Thanks for the report! Could you please try the branch mount-fix and let me know if it works on your setup. |
|
I encountered this same issue, and yes the |
Merged
|
I have the same issue, and the current |
|
@skorokithakis I wonder if your problem is #19. Can you show us the output of |
|
Sure: |
|
Okay, I think your issue is indeed #19. |
|
I agree, does it work if you unmount |
|
It does not: |
|
Old error: Also, could you try with branch nested-mount (need to install mergerfs) (and running from your home dir) |
|
Should be addressed by #67 |
Merged
8 tasks
ezrizhu
added a commit
that referenced
this issue
Jun 29, 2023
* Allow for nested mount by using mergerfs
* Remove debug bash and echo
* mount /run with merger aswell
* refactor and use overlayfs via mergerfs if regular overlayfs fails
* Only mount /dev/{tty null zero full random urandom}
* improve docs, refactor from top_dir to mountpoint
* Fix mergerfs failing not showing mount log path
* Add support for unionfs, allow user to specify unionfs helper path
* Write mountpoint on unionhelper not found message
* exit if findmnt not installed
* nested mount docs
* add newlines to readme
* grammar fix
* Add -U option description to manpages
* Add shell completion for -U option
* Change -U flag autocompletion to only suggest executables
* Install mergerfs in ci
* Try reading from /run directory before testing
* Refactor and unmount devices for tests to pass
* Add a device test
* Some comments and redirect a test to /dev/null
Fixed #56 #45 #38 #20 #19
---------
Co-authored-by: Eric Zhu <eric@debian-BULLSEYE-live-builder-AMD64>
Co-authored-by: gliargovas <gliargovas@aueb.gr>
Co-authored-by: Konstantinos Kallas <konstantinos.kallas@hotmail.com>
Co-authored-by: Michael Greenberg <michael@greenberg.science>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the code that tries to mount the overlays, there is a check for top level directory mount points that is a little too aggressive for systems the have user filesystems mounted at locations like /srv and /home (which is the custom of the system administrators where I work).
this line
excludes the LVM volumes mounted at /srv/and /home on my system via the "! mountpoint" clause.
When I run try from my home directory (/home/mccahill) it fails like this:
Try does run correctly when run from a directory for which it has created an overlay.
I can see why try wants to exclude mounts like /boot, /dev, /proc, /run, /sys, and so on, but user filesystem mounts need to have overlays.
The text was updated successfully, but these errors were encountered: