Bug#657497: nfs-common: Exec permission denied
Package: nfs-common Version: 1:1.2.6-3 Followup-For: Bug #657497 I have just come across the same issue, but in my case the `exec` option is being ignored when used in conjunction with the `users` option, even when `exec` coming after `users`. With `/etc/fstab` containing labrador:/oneforall /oneforall nfs auto,exec 0 0 the `exec` option is obeyed: labrador:/oneforall on /oneforall type nfs (rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.2,mountvers=3,mountport=57298,mountproto=udp,local_lock=none,addr=192.168.0.2) However, with `/etc/fstab` containing labrador:/oneforall /oneforall nfs users,auto,exec 0 0 the `exec` option is _not_ obeyed: labrador:/oneforall on /oneforall type nfs (rw,nosuid,nodev,noexec,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.2,mountvers=3,mountport=57298,mountproto=udp,local_lock=none,addr=192.168.0.2) This is a regression, and should be fixed. -- Package-specific info: -- rpcinfo -- program vers proto port 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 44901 status 1000241 tcp 53640 status 1000211 udp 35126 nlockmgr 1000213 udp 35126 nlockmgr 1000214 udp 35126 nlockmgr 1000211 tcp 37294 nlockmgr 1000213 tcp 37294 nlockmgr 1000214 tcp 37294 nlockmgr -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD= NEED_GSSD= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- labrador:/oneforall /oneforall nfs auto,exec 0 0 -- /proc/mounts -- rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 labrador:/oneforall /oneforall nfs rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.2,mountvers=3,mountport=57298,mountproto=udp,local_lock=none,addr=192.168.0.2 0 0 -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-35 ii libc6 2.13-38 ii libcap2 1:2.22-1.2 ii libcomerr2 1.42.5-1 ii libdevmapper1.02.1 2:1.02.74-6 ii libevent-2.0-5 2.0.19-stable-3 ii libgssglue1 0.4-2 ii libk5crypto31.10.1+dfsg-3 ii libkeyutils11.5.5-4 ii libkrb5-3 1.10.1+dfsg-3 ii libmount1 2.20.1-5.3 ii libnfsidmap20.25-4 ii libtirpc1 0.2.2-5 ii libwrap07.6.q-24 ii lsb-base4.1+Debian9 ii rpcbind 0.2.0-8 ii ucf 3.0025+nmu3 Versions of packages nfs-common recommends: ii python 2.7.3-3 Versions of packages nfs-common suggests: pn open-iscsi none pn watchdognone Versions of packages nfs-kernel-server depends on: ii libblkid1 2.20.1-5.3 ii libc6 2.13-38 ii libtirpc1 0.2.2-5 ii libwrap0 7.6.q-24 ii lsb-base 4.1+Debian9 ii ucf3.0025+nmu3 -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2013084501.7604.44419.reportbug@localhost
Bug#657497: Bug #657497 nfs-common: Exec permission denied
On Mon, 27 Feb 2012 06:43:55 + Ben Hutchings b...@decadent.org.uk wrote: On Sun, 2012-02-26 at 16:35 +, Tony Houghton wrote: I tried hand mounting as per message #72, I don't think that's the cause. It seems to be the user option that disables exec. Without user I get exec permissions whether I mount using /etc/fstab or give a full mount command, with the user option I get no exec. Well yes, 'user' implies 'noexec,nodev,nosuid'. You have to put 'exec' *after* 'user' to override that. Maybe mount.nfs behaved differently in the past, but if so that was a bug. However Jakub and Luc apparently had these options in the right order. I thought I had tried exec after user but I see that on one of my affected machines I had them the wrong way round. Putting exec after user fixes it for me. signature.asc Description: PGP signature
Bug#657497: Bug #657497 nfs-common: Exec permission denied
I tried hand mounting as per message #72, I don't think that's the cause. It seems to be the user option that disables exec. Without user I get exec permissions whether I mount using /etc/fstab or give a full mount command, with the user option I get no exec. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120226163523.5f676d8a@junior
Bug#657497: Bug #657497 nfs-common: Exec permission denied
On Sun, 2012-02-26 at 16:35 +, Tony Houghton wrote: I tried hand mounting as per message #72, I don't think that's the cause. It seems to be the user option that disables exec. Without user I get exec permissions whether I mount using /etc/fstab or give a full mount command, with the user option I get no exec. Well yes, 'user' implies 'noexec,nodev,nosuid'. You have to put 'exec' *after* 'user' to override that. Maybe mount.nfs behaved differently in the past, but if so that was a bug. However Jakub and Luc apparently had these options in the right order. I tested the conversion of option strings by running: strace -e mount mount.nfs -o options source mountpoint This shows the mount() call made to the kernel along with the mount flags (names beginning 'MS_'), which should not include MS_NOEXEC. when I run mount.nfs with options 'users,async,exec' or 'rw,user,exec,auto' I see mount.nfs using the correct mount flags, MS_NOSUID|MS_NODEV. Jakub, Luc, do you get the same results? Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part
Bug#657497: nfs-common: Exec permission denied
On 02/04/12 01:47, Tony Houghton wrote: Sorry about the lack of response. On Thu, 26 Jan 2012 22:14:41 + Ben Hutchingsb...@decadent.org.uk wrote: I assume you upgraded the client and not the server? Which was the previous version? (/var/log/dpkg.log should show this.) Did you upgrade the kernel at the same time? If so, what were the old and new package versions? Client and server were both upgraded from 1:1.2.5-3 to 1:1.2.5-4 on the same day. ls -l shows the x bit is still set, but I get permission denied when I try to run them, and bash's autocompletion also seems to know they're not executable because it doesn't expand them when I press Tab. I've tried adding 'exec' to fstab options but it didn't help. The same thing happens whether I use mount or pmount as a normal user or mount as root. Are all 'x' permission bits set? Do you also have read permission for the executables? ~ $ ls -l /media/htpc/hdvb/mscript.py -rwxr-xr-x 1 nobody nogroup 376 Jan 11 12:54 /media/htpc/hdvb/mscript.py ~ $ /media/htpc/hdvb/mscript.py bash: /media/htpc/hdvb/mscript.py: Permission denied I overlooked the nobody nogroup before. Is that normal? The UIDs are the same on both PCs and I can write to the file despite the discrepancy in the user and group names. Here I have to restart the idmapd service to get the names properly. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f2d0ebb.5050...@gmail.com
Bug#657497: nfs-common: Exec permission denied
Sorry about the lack of response. On Thu, 26 Jan 2012 22:14:41 + Ben Hutchings b...@decadent.org.uk wrote: I assume you upgraded the client and not the server? Which was the previous version? (/var/log/dpkg.log should show this.) Did you upgrade the kernel at the same time? If so, what were the old and new package versions? Client and server were both upgraded from 1:1.2.5-3 to 1:1.2.5-4 on the same day. ls -l shows the x bit is still set, but I get permission denied when I try to run them, and bash's autocompletion also seems to know they're not executable because it doesn't expand them when I press Tab. I've tried adding 'exec' to fstab options but it didn't help. The same thing happens whether I use mount or pmount as a normal user or mount as root. Are all 'x' permission bits set? Do you also have read permission for the executables? ~ $ ls -l /media/htpc/hdvb/mscript.py -rwxr-xr-x 1 nobody nogroup 376 Jan 11 12:54 /media/htpc/hdvb/mscript.py ~ $ /media/htpc/hdvb/mscript.py bash: /media/htpc/hdvb/mscript.py: Permission denied I overlooked the nobody nogroup before. Is that normal? The UIDs are the same on both PCs and I can write to the file despite the discrepancy in the user and group names. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120203201745.101f8536@tiber
Bug#657497: nfs-common: Exec permission denied
On Tuesday 31 of January 2012 04:47:58 Ben Hutchings wrote: On Mon, 2012-01-30 at 23:17 +0100, Jakub Krajewski wrote: [...] Looks like with 1.2.5-4 there is noexec flag present (even though I have put exec flag in /etc/fstab, when I remove it - it is the same however). If you need any other data, please ask. :) Sorry, I forgot to ask: what is the full entry for this mount in /etc/fstab? Here it is: imperator:/usr/src/linux/usr/src/linux-imperatornfs users,async,exec 0 0 Best regards, -- Jakub Krajewski -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201201311740.59528.ja...@krajewski.org
Bug#657497: nfs-common: Exec permission denied
Hello, Thanks for your response, I'll try to address all questions in one message. @dE.: This Squeeze NFS server have been working great for more than a year and always with custom kernel. More to say I have not changed anything there. About permissions - files are owned by root and mounted by root on the client. It is my home server and home workstation. So nothing mission critical. :) @Ben: nfs-common 1.2.5-3: /proc/mounts: imperator:/usr/src/linux/ /usr/src/linux-imperator nfs rw,nosuid,nodev,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.3,mountvers=3,mountport=42837,mountproto=udp,local_lock=none,addr=192.168.1.3 0 0 /etc/mtab: imperator:/usr/src/linux/ /usr/src/linux-imperator nfs rw,nosuid,nodev,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.3,mountvers=3,mountport=42837,mountproto=udp,local_lock=none,addr=192.168.1.3 0 0 nfs-common 1.2.5-4: /proc/mounts: imperator:/usr/src/linux/ /usr/src/linux-imperator nfs rw,nosuid,nodev,noexec,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.3,mountvers=3,mountport=42837,mountproto=udp,local_lock=none,addr=192.168.1.3 0 0 /etc/mtab: imperator:/usr/src/linux/ /usr/src/linux-imperator nfs rw,nosuid,nodev,noexec,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.3,mountvers=3,mountport=42837,mountproto=udp,local_lock=none,addr=192.168.1.3 0 0 Looks like with 1.2.5-4 there is noexec flag present (even though I have put exec flag in /etc/fstab, when I remove it - it is the same however). If you need any other data, please ask. :) Best regards, -- Jakub Krajewski -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201201302317.16310.ja...@krajewski.org
Bug#657497: nfs-common: Exec permission denied
On Mon, 2012-01-30 at 23:17 +0100, Jakub Krajewski wrote: [...] Looks like with 1.2.5-4 there is noexec flag present (even though I have put exec flag in /etc/fstab, when I remove it - it is the same however). If you need any other data, please ask. :) Sorry, I forgot to ask: what is the full entry for this mount in /etc/fstab? Ben. -- Ben Hutchings Lowery's Law: If it jams, force it. If it breaks, it needed replacing anyway. signature.asc Description: This is a digitally signed message part
Bug#657497: nfs-common: Exec permission denied
What about the server exports? This is mine: /usr/src/linux192.168.1.2(rw,sync,no_subtree_check,no_root_squash) Packages on the Squeeze server (kernel is custom there, as I said, works like charm with 1.2.5-3 version of sid's nfs-common package): ii nfs-common 1:1.2.2-4 ii nfs-kernel-server 1:1.2.2-4 Best regards, -- Jakub Krajewski -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201201281038.29941.ja...@krajewski.org
Bug#657497: nfs-common: Exec permission denied
On 01/28/12 15:08, Jakub Krajewski wrote: What about the server exports? This is mine: /usr/src/linux192.168.1.2(rw,sync,no_subtree_check,no_root_squash) Packages on the Squeeze server (kernel is custom there, as I said, works like charm with 1.2.5-3 version of sid's nfs-common package): ii nfs-common 1:1.2.2-4 ii nfs-kernel-server 1:1.2.2-4 Best regards, Maybe there's a mismatch between the kernel modules and the userspace nfs-kernel-server package. Did you try the Debian kernel? Also, who's the owner of the files in the server? root? Also, as what UID are you mounting from the client? Did you try this as root? Could you post output of ls -l from the client? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f23abc6.4020...@gmail.com
Bug#657497: nfs-common: Exec permission denied
On Sat, 2012-01-28 at 13:33 +0530, dE . wrote: On 01/28/12 15:08, Jakub Krajewski wrote: What about the server exports? This is mine: /usr/src/linux192.168.1.2(rw,sync,no_subtree_check,no_root_squash) Packages on the Squeeze server (kernel is custom there, as I said, works like charm with 1.2.5-3 version of sid's nfs-common package): ii nfs-common 1:1.2.2-4 ii nfs-kernel-server 1:1.2.2-4 Best regards, Maybe there's a mismatch between the kernel modules and the userspace nfs-kernel-server package. [...] This is unlikely as they are not tightly coupled. Ben. -- Ben Hutchings If you seem to know what you are doing, you'll be given more to do. signature.asc Description: This is a digitally signed message part
Bug#657497: nfs-common: Exec permission denied
On Fri, 2012-01-27 at 21:24 +0100, Jakub Krajewski wrote: I have exactly same problem as one described by Tony. Reverting back nfs-common package to version 1.2.5-3 solves issue and everything works OK. My NFS shares are served by Debian Squeeze box and no server upgrade was done there. Exec flag in fstab does not help as well. [...] The major change in 1:1.2.5-4 was to use libmount for access to the files /etc/fstab and /etc/mtab. Could you report what the lines for this NFS mount look like in /proc/mounts and in /etc/mtab (if the latter is a separate file) when using each of these versions? Ben. -- Ben Hutchings If you seem to know what you are doing, you'll be given more to do. signature.asc Description: This is a digitally signed message part
Bug#657497: nfs-common: Exec permission denied
I have exactly same problem as one described by Tony. Reverting back nfs-common package to version 1.2.5-3 solves issue and everything works OK. My NFS shares are served by Debian Squeeze box and no server upgrade was done there. Exec flag in fstab does not help as well. Package: nfs-common Version: 1:1.2.5-4 Followup-For: Bug #657497 -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000211 udp 45810 nlockmgr 1000213 udp 45810 nlockmgr 1000214 udp 45810 nlockmgr 1000211 tcp 47670 nlockmgr 1000213 tcp 47670 nlockmgr 1000214 tcp 47670 nlockmgr 1000241 udp 51653 status 1000241 tcp 40295 status -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD=yes NEED_GSSD=no -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- imperator:/srv/xbmc /mnt/xbmc nfs users,noatime,async,nolock,nfsvers=3 0 0 imperator:/usr/src/linux/usr/src/linux-imperatornfs users,async,exec 0 0 -- /proc/mounts -- imperator:/srv/xbmc/ /mnt/xbmc nfs rw,nosuid,nodev,noexec,noatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.3,mountvers=3,mountport=56275,mountproto=udp,local_lock=all,addr=192.168.1.3 0 0 nfsd /proc/fs/nfsd nfsd rw,relatime 0 0 imperator:/usr/src/linux/ /usr/src/linux-imperator nfs rw,nosuid,nodev,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.3,mountvers=3,mountport=43815,mountproto=udp,local_lock=none,addr=192.168.1.3 0 0 rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (1001, 'unstable'), (500, 'stable'), (101, 'experimental'), (101, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.113 ii initscripts 2.88dsf-18 ii libc6 2.13-24 ii libcap2 1:2.22-1 ii libcomerr2 1.42-1 ii libdevmapper1.02.1 2:1.02.67-2 ii libevent-2.0-5 2.0.16-stable-1 ii libgssapi-krb5-21.10+dfsg~beta1-2 ii libgssglue1 0.3-4 ii libk5crypto31.10+dfsg~beta1-2 ii libkeyutils11.5.2-2 ii libkrb5-3 1.10+dfsg~beta1-2 ii libmount1 2.20.1-1.2 ii libnfsidmap20.25-1 ii libtirpc1 0.2.2-5 ii libwrap07.6.q-22 ii lsb-base3.2-28.1 ii rpcbind 0.2.0-7 ii ucf 3.0025+nmu2 Versions of packages nfs-common recommends: ii python 2.7.2-10 nfs-common suggests no packages. Versions of packages nfs-kernel-server depends on: ii libblkid1 2.20.1-1.2 ii libc6 2.13-24 ii libnfsidmap2 0.25-1 ii libtirpc1 0.2.2-5 ii libwrap0 7.6.q-22 ii lsb-base 3.2-28.1 ii ucf 3.0025+nmu2 -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201201272124.43941.ja...@krajewski.org
Bug#657497: nfs-common: Exec permission denied
Package: nfs-common Version: 1:1.2.5-4 Severity: normal Dear Maintainer, *** 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 lines *** Since this upgrade I can not execute scripts and programs on an NFS mount. ls -l shows the x bit is still set, but I get permission denied when I try to run them, and bash's autocompletion also seems to know they're not executable because it doesn't expand them when I press Tab. I've tried adding 'exec' to fstab options but it didn't help. The same thing happens whether I use mount or pmount as a normal user or mount as root. -- Package-specific info: -- rpcinfo -- program vers proto port 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 47020 status 1000241 tcp 40017 status 132 tcp 2049 nfs 133 tcp 2049 nfs 134 tcp 2049 nfs 1002272 tcp 2049 1002273 tcp 2049 132 udp 2049 nfs 133 udp 2049 nfs 134 udp 2049 nfs 1002272 udp 2049 1002273 udp 2049 1000211 udp 54893 nlockmgr 1000213 udp 54893 nlockmgr 1000214 udp 54893 nlockmgr 1000211 tcp 42107 nlockmgr 1000213 tcp 42107 nlockmgr 1000214 tcp 42107 nlockmgr 151 udp 58977 mountd 151 tcp 39316 mountd 152 udp 38698 mountd 152 tcp 37115 mountd 153 udp 58590 mountd 153 tcp 60792 mountd -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD= NEED_GSSD= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- htpc.local:/home/tony /media/htpc nfsexec,user,noauto,nolock 0 0 infant.local:/home/tony /media/infant nfsexec,user,noauto,nolock 0 0 -- /proc/mounts -- rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 nfsd /proc/fs/nfsd nfsd rw,relatime 0 0 htpc.local:/home/tony /media/htpc nfs4 rw,nosuid,nodev,noexec,relatime,vers=4,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.78,minorversion=0,local_lock=none,addr=192.168.1.81 0 0 -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.113 ii initscripts 2.88dsf-18 ii libc6 2.13-24 ii libcap2 1:2.22-1 ii libcomerr2 1.42-1 ii libdevmapper1.02.1 2:1.02.67-2 ii libevent-2.0-5 2.0.16-stable-1 ii libgssapi-krb5-21.10+dfsg~beta1-2 ii libgssglue1 0.3-4 ii libk5crypto31.10+dfsg~beta1-2 ii libkeyutils11.5.2-2 ii libkrb5-3 1.10+dfsg~beta1-2 ii libmount1 2.20.1-1.2 ii libnfsidmap20.25-1 ii libtirpc1 0.2.2-5 ii libwrap07.6.q-22 ii lsb-base3.2-28.1 ii rpcbind 0.2.0-7 ii ucf 3.0025+nmu2 Versions of packages nfs-common recommends: ii python 2.7.2-10 nfs-common suggests no packages. Versions of packages nfs-kernel-server depends on: ii libblkid1 2.20.1-1.2 ii libc6 2.13-24 ii libnfsidmap2 0.25-1 ii libtirpc1 0.2.2-5 ii libwrap0 7.6.q-22 ii lsb-base 3.2-28.1 ii ucf 3.0025+nmu2 -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120126163334.5166.99009.report...@tiber.lan
Bug#657497: nfs-common: Exec permission denied
On Thu, Jan 26, 2012 at 04:33:34PM +, Tony Houghton wrote: Package: nfs-common Version: 1:1.2.5-4 Severity: normal [...] Since this upgrade I can not execute scripts and programs on an NFS mount. I assume you upgraded the client and not the server? Which was the previous version? (/var/log/dpkg.log should show this.) Did you upgrade the kernel at the same time? If so, what were the old and new package versions? ls -l shows the x bit is still set, but I get permission denied when I try to run them, and bash's autocompletion also seems to know they're not executable because it doesn't expand them when I press Tab. I've tried adding 'exec' to fstab options but it didn't help. The same thing happens whether I use mount or pmount as a normal user or mount as root. [...] Are all 'x' permission bits set? Do you also have read permission for the executables? Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120126221441.gp12...@decadent.org.uk
