odd permissions issue

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

odd permissions issue

Gordon Wrigley-4
I have a production system that has been running a custom fuse file
system for sometime now without any problems. I am trying to replicate
that file system on another machine and I am running into some
permission issues. It works fine for root but all other users hit
"Permission denied". I even get a permission denied just trying to do ls
-l on (not in) the mount point. If I unmount the FS then my others users
can access the mount point directory fine. I have also noticed that the
mount options on the second machine are showing up a little weird,
allow_other is listed twice and allow_root isn't listed at all despite
them both being running the same file system binary invoked with the
same options.

Original working machine:
mount output: unionFs on /mnt/fileServer type fuse
(rw,nosuid,nodev,default_permissions,allow_other,allow_root)
uname -r: 2.6.11-1-k7
lib fuse version (from apt): 2.2.1-4
fuse module version (from apt): 2.3.0-1

New non-working machine:
mount output: unionFs on /mnt/fileServer type fuse
(rw,nosuid,nodev,default_permissions,allow_other,allow_other)
uname -r: 2.6.11-1-k7
lib fuse version (from apt): 2.3.0-1
fuse module version (from apt): 2.3.0-1

Does anyone have any idea what I might be doing wrong?


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
fuse-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fuse-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: odd permissions issue

Miklos Szeredi
> Original working machine:
> mount output: unionFs on /mnt/fileServer type fuse
> (rw,nosuid,nodev,default_permissions,allow_other,allow_root)
> uname -r: 2.6.11-1-k7
> lib fuse version (from apt): 2.2.1-4
> fuse module version (from apt): 2.3.0-1
>
> New non-working machine:
> mount output: unionFs on /mnt/fileServer type fuse
> (rw,nosuid,nodev,default_permissions,allow_other,allow_other)
> uname -r: 2.6.11-1-k7
> lib fuse version (from apt): 2.3.0-1
> fuse module version (from apt): 2.3.0-1
>
> Does anyone have any idea what I might be doing wrong?

Can you try specifying only 'allow_other'.  This implies allowing
access for root as well, so 'allow_root' is not needed.

This works slightly differently in 2.2.1 and 2.3.0 so that could
explain your problems.  But using only one of 'allow_root' or
'allow_other' should work the same way under both versions.

Thanks,
Miklos


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
fuse-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fuse-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: odd permissions issue

Gordon Wrigley-4
Thank you, that fixed it.

 >'allow_other'.  This implies allowing access for root as well

is that documented somewhere?

Miklos Szeredi wrote:

>>Original working machine:
>>mount output: unionFs on /mnt/fileServer type fuse
>>(rw,nosuid,nodev,default_permissions,allow_other,allow_root)
>>uname -r: 2.6.11-1-k7
>>lib fuse version (from apt): 2.2.1-4
>>fuse module version (from apt): 2.3.0-1
>>
>>New non-working machine:
>>mount output: unionFs on /mnt/fileServer type fuse
>>(rw,nosuid,nodev,default_permissions,allow_other,allow_other)
>>uname -r: 2.6.11-1-k7
>>lib fuse version (from apt): 2.3.0-1
>>fuse module version (from apt): 2.3.0-1
>>
>>Does anyone have any idea what I might be doing wrong?
>
>
> Can you try specifying only 'allow_other'.  This implies allowing
> access for root as well, so 'allow_root' is not needed.
>
> This works slightly differently in 2.2.1 and 2.3.0 so that could
> explain your problems.  But using only one of 'allow_root' or
> 'allow_other' should work the same way under both versions.
>
> Thanks,
> Miklos


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
fuse-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fuse-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: odd permissions issue

Miklos Szeredi
>  >'allow_other'.  This implies allowing access for root as well
>
> is that documented somewhere?

It's probably not stated clearly enough in the README.  I'll add some
clarification.  Also the library should check if both options are
given and bail out with an error.

Thanks,
Miklos


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
fuse-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fuse-devel
Loading...