Bug #2439
closed
'df' shows permission denied for other user's FUSE mounts
Description
why's it say 'permission denied'?
jsheffi@shell.qr1hi:~$ df
df: `/home/peter/mnt': Permission denied
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 8256952 6271188 1566336 81% /
udev 10240 0 10240 0% /dev
tmpfs 170160 41032 129128 25% /run
/dev/xvda1 8256952 6271188 1566336 81% /
tmpfs 5120 0 5120 0% /run/lock
tmpfs 523820 0 523820 0% /run/shm
/dev/xvdb 153899044 54755436 99143608 36% /scratch
Updated by Tom Clegg almost 10 years ago
- Target version set to 2014-05-28 Pipeline Factory
Updated by Peter Amstutz almost 10 years ago
- Subject changed from df bug? to 'df' shows permission denied for other user's FUSE mounts
Updated by Peter Amstutz almost 10 years ago
- Target version deleted (
2014-05-28 Pipeline Factory)
Updated by Tom Clegg almost 10 years ago
- Target version set to 2014-07-16 Sprint
Updated by Brett Smith almost 10 years ago
I think the best solution is for Puppet to install this script on our shell nodes as /usr/local/bin/df:
#!/bin/sh exec df -x fuse "$@"
This general issue consistently comes up in bug reports and the consensus is that the onus is on df to be smarter.
- Debian bug - about Docker integration
- Red Hat bug the first
- Red Hat bug the second (note: exact same bug, exact same basic answer years later)
Obviously my solution isn't perfect (it might not help people who modify $PATH) but I think it solves our immediate "bad first impression" problem with an appropriate amount of effort.
Updated by Brett Smith almost 10 years ago
- Status changed from New to Resolved
Brett Smith wrote:
I think the best solution is for Puppet to install this script on our shell nodes as
/usr/local/bin/df:
I asked for feedback on IRC and Peter and Tim both supported this approach. Looking at our system configuration, I found an even better solution: we have a shell file that gets sourced for all interactive sessions to help set up Arvados environment. I added code here to alias df as described. This is a better fit because it means it's more likely to help users (e.g., not thwarted by $PATH changes), and less likely to interfere with init scripts or other noninteractive users of df.
Reviewed and approved by Ward, and pushed to our system configuration.