Your message dated Fri, 13 Sep 2024 23:09:10 +0200 with message-id <zusp9pbvnvuyg...@eldamar.lan> and subject line Re: Bug#780944: nfs-kernel-server exports automounted filesystems under /media only as root:root has caused the Debian Bug report #780944, regarding nfs-kernel-server exports automounted filesystems under /media only as root:root to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 780944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: nfs-kernel-server Version: 1:1.2.8-9 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** I am exporting /home/.. and /media, where my USB-drives are located. When I export a directory under /home I get the correct userid and groupid mapping. The automounted drives under /media will not mount on the nfs-client with the correct userid or groupid. I have tried forcing it with anonuid and anongid in exportfs and it doesn't matter everything is root:root under /media when i try to open it on the client. I have also tried to remoutnt drives from /media/user/.. and re-export from that directory since this seems more correct but to no avail. I am using NFSv4 no idmapping and no kerberos so this should be pretty stright forward but I might miss something. or its a bug. Problem occured when I upgraded to Jessie from Wheezy on the server(the client is a new install jessie from netinst on a virtualbox instance). Last iteration of config files: Server /etc/exports /export/media 10.0.0.0/24(rw,nohide,insecure,no_subtree_check,async,sec=sys) /export/em 10.0.0.0/24(rw,nohide,insecure,no_subtree_check,async,sec=sys) /export/new 10.0.0.0/24(ro,nohide,insecure,no_subtree_check,async) /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> /dev/mapper/Melkor-root / ext4 errors=remount-ro 0 1 # /boot was on /dev/sda1 during installation UUID=39a76d28-3c42-4f57-9e07-9bea14e41f3c /boot ext4 defaults 0 2 /dev/mapper/storage_vol1-home /home ext4 defaults 0 2 /dev/mapper/Melkor-tmp /tmp ext4 defaults 0 2 /dev/mapper/Melkor-var /var ext4 defaults 0 2 /dev/mapper/storage_vol1-virtos /var/virtos ext4 defaults 0 2 /dev/mapper/Melkor-swap none swap sw 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 /home/executor/Azureus\040Downloads /export/new none bind 0 0 /media /export/media none bind 0 0 /media/executor /export/em none bind 0 0 Client /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=cc86bad1-92b6-46f8-8601-a8a79fb4f30f / ext4 errors=remount -ro 0 1 # swap was on /dev/sda5 during installation UUID=0da51868-169c-4ca5-960d-4f3f9ef6be3f none swap sw 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 ## NFS Mounts #silmarilion:/media/executor /mnt/media nfs4 _netdev,auto 0 0 #silmarilion:/export/media /mnt/media nfs4 _netdev,sec=sys,auto 0 0 silmarilion:/export/em /mnt/em nfs4 _netdev,sec=sys,auto 0 0 silmarilion:/export/new /mnt/new nfs4 _netdev,auto 0 0 #media /mnt/media vboxsf ro,uid=1000,gid=1000 0 0 I would expect this to reslut in a mounting of /meida/em from server to client under /mnt/em and all directories under /media/executor on the server showing the same owner and gid as on the client and servers. Now everything is root:root. -- Package-specific info: -- rpcinfo -- program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 59072 status 100024 1 tcp 54743 status 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100227 2 tcp 2049 100227 3 tcp 2049 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100227 2 udp 2049 100227 3 udp 2049 100021 1 udp 43177 nlockmgr 100021 3 udp 43177 nlockmgr 100021 4 udp 43177 nlockmgr 100021 1 tcp 57910 nlockmgr 100021 3 tcp 57910 nlockmgr 100021 4 tcp 57910 nlockmgr 100005 1 udp 34403 mountd 100005 1 tcp 46218 mountd 100005 2 udp 50536 mountd 100005 2 tcp 38811 mountd 100005 3 udp 46236 mountd 100005 3 tcp 57633 mountd -- /etc/default/nfs-kernel-server -- RPCNFSDCOUNT=8 RPCNFSDPRIORITY=0 RPCMOUNTDOPTS="--manage-gids" NEED_SVCGSSD="" RPCSVCGSSDOPTS="" -- /etc/exports -- /export/media 10.0.0.0/24(rw,nohide,insecure,no_subtree_check,async,anonuid=1000,anongid=1000) /export/em 10.0.0.0/24(ro,nohide,insecure,no_subtree_check,async) /export/new 10.0.0.0/24(ro,nohide,insecure,no_subtree_check,async) -- /proc/fs/nfs/exports -- # Version 1.1 # Path Client(Flags) # IPs /export 10.0.0.0/24(ro,insecure,root_squash,sync,no_wdelay,no_subtree_check,v4root,uuid=e86652c7:5fac4015:89fb16f2:2ca3b742,sec=1) /media 10.0.0.0/24(ro,insecure,root_squash,sync,no_wdelay,no_subtree_check,v4root,uuid=e86652c7:5fac4015:89fb16f2:2ca3b742,sec=1) /export/media 10.0.0.0/24(rw,insecure,root_squash,async,wdelay,nohide,no_subtree_check,anonuid=1000,anongid=1000,uuid=e86652c7:5fac4015:89fb16f2:2ca3b742,sec=1) / 10.0.0.0/24(ro,insecure,root_squash,sync,no_wdelay,no_subtree_check,v4root,fsid=0,uuid=e86652c7:5fac4015:89fb16f2:2ca3b742,sec=1) /media/executor 10.0.0.0/24(ro,insecure,root_squash,async,wdelay,nohide,no_subtree_check,uuid=e86652c7:5fac4015:89fb16f2:2ca3b742,sec=1) /export/new 10.0.0.0/24(ro,insecure,root_squash,async,wdelay,nohide,no_subtree_check,uuid=5c1b3e69:38034b53:80729f1b:5ea21e3f,sec=1) -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (650, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/24 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nfs-kernel-server depends on: ii libblkid1 2.25.2-5 ii libc6 2.19-15 ii libcap2 1:2.24-7 ii libsqlite3-0 3.8.7.1-1 ii libtirpc1 0.2.5-1 ii libwrap0 7.6.q-25 ii lsb-base 4.1+Debian13+nmu1 ii nfs-common 1:1.2.8-9 ii ucf 3.0030 nfs-kernel-server recommends no packages. nfs-kernel-server suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Hi, On Sun, Mar 22, 2015 at 11:33:18AM +0100, Thomas Liljenstam wrote: > Package: nfs-kernel-server > Version: 1:1.2.8-9 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > * What exactly did you do (or not do) that was effective (or > ineffective)? > * What was the outcome of this action? > * What outcome did you expect instead? > > *** End of the template - remove these template lines *** > > I am exporting /home/.. and /media, where my USB-drives are located. When I > export a directory under /home I get the correct userid and groupid mapping. > The automounted drives under /media will not mount on the nfs-client with the > correct userid or groupid. I have tried forcing it with anonuid and anongid in > exportfs and it doesn't matter everything is root:root under /media when i try > to open it on the client. I have also tried to remoutnt drives from > /media/user/.. and re-export from that directory since this seems more correct > but to no avail. I am using NFSv4 no idmapping and no kerberos so this should > be pretty stright forward but I might miss something. or its a bug. > > Problem occured when I upgraded to Jessie from Wheezy on the server(the client > is a new install jessie from netinst on a virtualbox instance). > > Last iteration of config files: > > Server > > /etc/exports > /export/media 10.0.0.0/24(rw,nohide,insecure,no_subtree_check,async,sec=sys) > /export/em 10.0.0.0/24(rw,nohide,insecure,no_subtree_check,async,sec=sys) > /export/new 10.0.0.0/24(ro,nohide,insecure,no_subtree_check,async) > > /etc/fstab > # /etc/fstab: static file system information. > # > # Use 'blkid' to print the universally unique identifier for a > # device; this may be used with UUID= as a more robust way to name devices > # that works even if disks are added and removed. See fstab(5). > # > # <file system> <mount point> <type> <options> <dump> <pass> > /dev/mapper/Melkor-root / ext4 errors=remount-ro 0 1 > # /boot was on /dev/sda1 during installation > UUID=39a76d28-3c42-4f57-9e07-9bea14e41f3c /boot ext4 defaults > 0 2 > /dev/mapper/storage_vol1-home /home ext4 defaults 0 > 2 > /dev/mapper/Melkor-tmp /tmp ext4 defaults 0 2 > /dev/mapper/Melkor-var /var ext4 defaults 0 2 > /dev/mapper/storage_vol1-virtos /var/virtos ext4 defaults 0 > 2 > /dev/mapper/Melkor-swap none swap sw 0 0 > /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 > /home/executor/Azureus\040Downloads /export/new none bind 0 0 > /media /export/media none bind 0 0 > /media/executor /export/em none bind 0 0 > > Client > > /etc/fstab > > # /etc/fstab: static file system information. > # > # Use 'blkid' to print the universally unique identifier for a > # device; this may be used with UUID= as a more robust way to name devices > # that works even if disks are added and removed. See fstab(5). > # > # <file system> <mount point> <type> <options> <dump> <pass> > # / was on /dev/sda1 during installation > UUID=cc86bad1-92b6-46f8-8601-a8a79fb4f30f / ext4 > errors=remount > -ro 0 1 > # swap was on /dev/sda5 during installation > UUID=0da51868-169c-4ca5-960d-4f3f9ef6be3f none swap sw > 0 0 > /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 > ## NFS Mounts > > #silmarilion:/media/executor /mnt/media nfs4 _netdev,auto 0 0 > #silmarilion:/export/media /mnt/media nfs4 _netdev,sec=sys,auto 0 0 > silmarilion:/export/em /mnt/em nfs4 _netdev,sec=sys,auto 0 0 > silmarilion:/export/new /mnt/new nfs4 _netdev,auto 0 0 > #media /mnt/media vboxsf ro,uid=1000,gid=1000 0 0 > > > I would expect this to reslut in a mounting of /meida/em from server to client > under /mnt/em and all directories under /media/executor on the server showing > the same owner and gid as on the client and servers. Now everything is > root:root. > > > > > > -- Package-specific info: > -- rpcinfo -- > program vers proto port service > 100000 4 tcp 111 portmapper > 100000 3 tcp 111 portmapper > 100000 2 tcp 111 portmapper > 100000 4 udp 111 portmapper > 100000 3 udp 111 portmapper > 100000 2 udp 111 portmapper > 100024 1 udp 59072 status > 100024 1 tcp 54743 status > 100003 2 tcp 2049 nfs > 100003 3 tcp 2049 nfs > 100003 4 tcp 2049 nfs > 100227 2 tcp 2049 > 100227 3 tcp 2049 > 100003 2 udp 2049 nfs > 100003 3 udp 2049 nfs > 100003 4 udp 2049 nfs > 100227 2 udp 2049 > 100227 3 udp 2049 > 100021 1 udp 43177 nlockmgr > 100021 3 udp 43177 nlockmgr > 100021 4 udp 43177 nlockmgr > 100021 1 tcp 57910 nlockmgr > 100021 3 tcp 57910 nlockmgr > 100021 4 tcp 57910 nlockmgr > 100005 1 udp 34403 mountd > 100005 1 tcp 46218 mountd > 100005 2 udp 50536 mountd > 100005 2 tcp 38811 mountd > 100005 3 udp 46236 mountd > 100005 3 tcp 57633 mountd > -- /etc/default/nfs-kernel-server -- > RPCNFSDCOUNT=8 > RPCNFSDPRIORITY=0 > RPCMOUNTDOPTS="--manage-gids" > NEED_SVCGSSD="" > RPCSVCGSSDOPTS="" > -- /etc/exports -- > /export/media > 10.0.0.0/24(rw,nohide,insecure,no_subtree_check,async,anonuid=1000,anongid=1000) > /export/em 10.0.0.0/24(ro,nohide,insecure,no_subtree_check,async) > /export/new 10.0.0.0/24(ro,nohide,insecure,no_subtree_check,async) > -- /proc/fs/nfs/exports -- > # Version 1.1 > # Path Client(Flags) # IPs > /export > 10.0.0.0/24(ro,insecure,root_squash,sync,no_wdelay,no_subtree_check,v4root,uuid=e86652c7:5fac4015:89fb16f2:2ca3b742,sec=1) > /media > 10.0.0.0/24(ro,insecure,root_squash,sync,no_wdelay,no_subtree_check,v4root,uuid=e86652c7:5fac4015:89fb16f2:2ca3b742,sec=1) > /export/media > 10.0.0.0/24(rw,insecure,root_squash,async,wdelay,nohide,no_subtree_check,anonuid=1000,anongid=1000,uuid=e86652c7:5fac4015:89fb16f2:2ca3b742,sec=1) > / > 10.0.0.0/24(ro,insecure,root_squash,sync,no_wdelay,no_subtree_check,v4root,fsid=0,uuid=e86652c7:5fac4015:89fb16f2:2ca3b742,sec=1) > /media/executor > 10.0.0.0/24(ro,insecure,root_squash,async,wdelay,nohide,no_subtree_check,uuid=e86652c7:5fac4015:89fb16f2:2ca3b742,sec=1) > /export/new > 10.0.0.0/24(ro,insecure,root_squash,async,wdelay,nohide,no_subtree_check,uuid=5c1b3e69:38034b53:80729f1b:5ea21e3f,sec=1) We did not took action on this bug for almost 10 years but as well on the last ping from Daniel there was no repsonse. I'm closing this bug. In case you still can reproduce the problem on a current supported system, please do reopen the bug. Regards, Salvatore
--- End Message ---
