On Tue, Nov 30, 2021 at 4:54 PM Carl Karsten <carl@xxxxxxxxxxxxxxxx> wrote:
>
> I don't need any help, This seems odd enough to report.
>
> I accidentally built my nfs server on buster, which threw some errors
> about index=on, so I added index=on. Then I rebuilt the server on
> bullseye, and almost everything was the same, except for 1 little
> thing. I removed the index=on, and all was well again.
>
> server:
> dist=bullseye
> d=/srv/nfs/rpi/${dist}
> p=${d}/boot
> rm -rf ${p}/work/index
> mount -t overlay overlay -o index=on,nfs_export=on,\
> lowerdir=${p}/setup:${p}/base,\
> upperdir=${p}/updates,\
> workdir=${p}/work \
> ${p}/merged
>
> /etc/exports
> /srv/nfs/rpi/bullseye/boot/merged
> *(rw,sync,no_subtree_check,no_root_squash,fsid=1)
>
>
> client:
> root@raspberrypi:~# mount
> 10.21.0.1:/srv/nfs/rpi/bullseye/root/merged on / type nfs
> (rw,relatime,vers=3,rsize=4096,wsize=4096,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.21.0.1,mountvers=3,mountproto=tcp,local_lock=all,addr=10.21.0.1)
>
> root@raspberrypi:~# mv /boot/z /boot/config.txt
> mv: cannot move '/boot/z' to '/boot/config.txt': Operation not permitted
>
> root@raspberrypi:~# strace mv /boot/z /boot/config.txt
strace is not useful information.
kernel log would have been able to shed more light on the error.
But I did not understand the report.
The error was on buster/bullseye? with index=on? without index=on?
You managed to confuse me.
index=on is deferred from nfs_export=on since commit
b0def88d807f ovl: resolve more conflicting mount options
So that is probably the difference between buster/bullseye.
Didn't check which kernels they use.
Thanks,
Amir.
