Bug #2439

'df' shows permission denied for other user's FUSE mounts

Added by Jonathan Sheffi about 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Brett Smith
Category:
-
Target version:
Start date:
03/24/2014
Due date:
% Done:

0%

Estimated time:
Story points:
0.5

Description

why's it say 'permission denied'?

:~$ 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

History

#1 Updated by Tom Clegg about 5 years ago

  • Target version set to 2014-05-28 Pipeline Factory

#2 Updated by Tom Clegg about 5 years ago

  • Story points set to 0.5

#3 Updated by Peter Amstutz about 5 years ago

  • Subject changed from df bug? to 'df' shows permission denied for other user's FUSE mounts

#4 Updated by Peter Amstutz about 5 years ago

  • Target version deleted (2014-05-28 Pipeline Factory)

#5 Updated by Tom Clegg about 5 years ago

  • Target version set to 2014-07-16 Sprint

#6 Updated by Brett Smith almost 5 years ago

  • Assigned To set to Brett Smith

#7 Updated by Brett Smith almost 5 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.

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.

#8 Updated by Brett Smith almost 5 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.

Also available in: Atom PDF