Good morning,
I've created a Pi Zero install with a third partition at the end of available storage on the SD card. I have added an entry in `/etc/fstab` to mount it and changed the perms on the mount point to allow all to read/write/execute so I can have user tasks manipulate files there. The mount point is owned by `root`. I find that when I enable `overlayfs` that the scripts that perform this operation also manipulates that mount and change the permissions to allow user and group to only read/execute that mount point. Before I start experimenting with solutions to resolve this issue, I thought I'd ask if there is an intended method to manage extra partitions WRT `overlayfs`.
My first thought is to remove the entry from `/etc/fstab` and add a command to root's crontab to mount the partition at boot.
My desire is to have some writable storage on the device while employing `overlayfs` for the root partition.
Thanks!
I've created a Pi Zero install with a third partition at the end of available storage on the SD card. I have added an entry in `/etc/fstab` to mount it and changed the perms on the mount point to allow all to read/write/execute so I can have user tasks manipulate files there. The mount point is owned by `root`. I find that when I enable `overlayfs` that the scripts that perform this operation also manipulates that mount and change the permissions to allow user and group to only read/execute that mount point. Before I start experimenting with solutions to resolve this issue, I thought I'd ask if there is an intended method to manage extra partitions WRT `overlayfs`.
My first thought is to remove the entry from `/etc/fstab` and add a command to root's crontab to mount the partition at boot.
My desire is to have some writable storage on the device while employing `overlayfs` for the root partition.
Thanks!
Statistics: Posted by HankB — Thu Aug 28, 2025 2:17 pm — Replies 3 — Views 90