On an already running / setup Armbian 23.11.1 (Bookworm CLI) installed on [Odroid M1](https://www.armbian.com/odroid-m1/) I run `armbian-install` as mentioned on the wiki page to move the bootloader / root filesystem to NVMe.
The rsync is unfortunately not limited to the root device (via `-x / --one-file-system`) and therefore also copies any other mounts (in my case it tried to copy another zfs device mounted in /var/lib/incus/storage-pools/ until the NVMe partition was full).
So armbian-install should run any rsync including `--one-file-system`
How to reproduce?
mount another device (e.g. to /var/lib/test) having data in it and run `armbian-install`
expected behavior: any mounted directory should not be copied but also mounted on the new boot device when booting.
What happened?
On an already running / setup Armbian 23.11.1 (Bookworm CLI) installed on [Odroid M1](https://www.armbian.com/odroid-m1/) I run `armbian-install` as mentioned on the wiki page to move the bootloader / root filesystem to NVMe.
The rsync is unfortunately not limited to the root device (via `-x / --one-file-system`) and therefore also copies any other mounts (in my case it tried to copy another zfs device mounted in /var/lib/incus/storage-pools/ until the NVMe partition was full).
So armbian-install should run any rsync including `--one-file-system`
How to reproduce?
mount another device (e.g. to /var/lib/test) having data in it and run `armbian-install`
expected behavior: any mounted directory should not be copied but also mounted on the new boot device when booting.
Branch
main (main development branch)
On which host OS are you observing this problem?
Jammy
Relevant log URL
https://www.armbian.com/odroid-m1/
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Raised by: https://github.com/hi-ko
https://github.com/armbian/build/issues/6242