Burned blu-ray disc with Power2Go software in W7 and mounted this disc in gentoo. logged as root typing ll /mnt/blr shows content of the disc corect including access rights, masks etc. doing the same think as user produces corrupted output like this: ll /mnt/blr/ ls: cannot access /mnt/blr/.: Permission denied ls: cannot access /mnt/blr/..: Permission denied ls: cannot access /mnt/blr/File1: Permission denied ls: cannot access /mnt/blr/File2: Permission denied ls: cannot access /mnt/blr/File3: Permission denied ls: cannot access /mnt/blr/File4: Permission denied ls: cannot access /mnt/blr/File5 Permission denied total 0 d????????? ? ? ? ? ? . d????????? ? ? ? ? ? .. ?????????? ? ? ? ? ? File1 ?????????? ? ? ? ? ? File2 ?????????? ? ? ? ? ? File3 ?????????? ? ? ? ? ? File4 ?????????? ? ? ? ? ? File5 I exclude problem with fstab definition, rights of /mnt/blr dir as I spent excesive time to change various settings with uid, gid, fmask, umask parameters that does not affect this at all. also /etc/group has correct settings for affected user Reproducible: Always Steps to Reproduce: 1.burn BD under win (vista/win7) 2.insert and mount in gentoo 3.type ll /mnt/xxx Actual Results: ll /mnt/blr/ ls: cannot access /mnt/blr/.: Permission denied ls: cannot access /mnt/blr/..: Permission denied ls: cannot access /mnt/blr/File1: Permission denied ls: cannot access /mnt/blr/File2: Permission denied ls: cannot access /mnt/blr/File3: Permission denied ls: cannot access /mnt/blr/File4: Permission denied ls: cannot access /mnt/blr/File5 Permission denied total 0 d????????? ? ? ? ? ? . d????????? ? ? ? ? ? .. ?????????? ? ? ? ? ? File1 ?????????? ? ? ? ? ? File2 ?????????? ? ? ? ? ? File3 ?????????? ? ? ? ? ? File4 ?????????? ? ? ? ? ? File5 Expected Results: ll /mnt/blr/ total 12 drw-r--r-- 7 1005 users 464 May 12 21:17 . drwxr-xr-x 8 root root 216 May 13 11:05 .. drw-r--r-- 2 1005 users 152 May 12 21:17 File1 drw-r--r-- 2 1005 users 184 May 12 21:17 File2 drw-r--r-- 2 1005 users 180 May 12 21:17 File3 drw-r--r-- 2 1005 users 168 May 12 21:17 File4 drw-r--r-- 2 1005 users 224 May 12 21:17 File5
What exactly is 'll' an alias for ? If you don't have execution rights for the top dir, this looks correct.
(In reply to comment #1) > What exactly is 'll' an alias for ? > If you don't have execution rights for the top dir, > this looks correct. > ll is alias for for ls-la, and I thhink I have x rights for mentioned dir: 0 drwxrwxrwx 2 root users 48 May 13 11:05 blr at least until it is mounted to blu-ray device, than it changes rihts to: 2 drw-rw-rw- 7 user1 users 464 May 12 21:17 blr
Rights before mount don't matter that much (seen that with ntfs). Paste the line, 'mount' prints about your mounted device, when you have that listing problem.
(In reply to comment #3) > Rights before mount don't matter that much (seen that with ntfs). > Paste the line, 'mount' prints about your mounted device, when > you have that listing problem. > When there is listing problem, system does not even prints rights. Instead of that it prints chain of questin marks. This is observed only under user. Under root listing - including rights listing works with no problems. This is under roor printout: ll /mnt/blr/ total 12 drw-r--r-- 7 1005 users 464 May 12 21:17 . drwxr-xr-x 8 root root 216 May 13 11:05 .. drw-r--r-- 2 1005 users 152 May 12 21:17 File1 drw-r--r-- 2 1005 users 184 May 12 21:17 File2 drw-r--r-- 2 1005 users 180 May 12 21:17 File3 drw-r--r-- 2 1005 users 168 May 12 21:17 File4 drw-r--r-- 2 1005 users 224 May 12 21:17 File5 Please note that it has been discussed on several threads on gentoo forums and even few veterans did not know how to solve this problem.
Please post the output of mount | grep blr
mount | grep blr /dev/sr0 on /mnt/blr type udf (ro,nosuid,nodev,uid=1001,gid=100,iocharset=utf8) attached.
So when root can see the content but a user can't, it's a permission problem. What I find strange is that you set uid=1001 on mount but the files still belong to UID 1005... I don't have any experience with UDF filesystems but did you try to mount the disk with the "nostrict" mount-option set?
(In reply to comment #7) > So when root can see the content but a user can't, it's a permission problem. > What I find strange is that you set uid=1001 on mount but the files still > belong to UID 1005... > I don't have any experience with UDF filesystems but did you try to mount the > disk with the "nostrict" mount-option set? > well, the printout is taken when I was using relly 1005, so now I don't have it anymore: su - ls -la /mnt/blr/ total 12 drw-rw-rw- 7 ondrej2 users 464 May 12 21:17 . drwxr-xr-x 8 root root 216 May 13 11:05 .. drw-rw-rw- 2 ondrej2 users 152 May 12 21:17 File1 drw-rw-rw- 2 ondrej2 users 184 May 12 21:17 File2 drw-rw-rw- 2 ondrej2 users 180 May 12 21:17 File2 drw-rw-rw- 2 ondrej2 users 168 May 12 21:17 File2 drw-rw-rw- 2 ondrej2 users 224 May 12 21:17 File2 ls -la /mnt/blr/ ls: cannot access /mnt/blr/.: Permission denied ls: cannot access /mnt/blr/..: Permission denied ls: cannot access /mnt/blr/File1: Permission denied ls: cannot access /mnt/blr/File2 Permission denied ls: cannot access /mnt/blr/File3: Permission denied ls: cannot access /mnt/blr/File4: Permission denied ls: cannot access /mnt/blr/File5: Permission denied total 0 d????????? ? ? ? ? ? . d????????? ? ? ? ? ? .. ?????????? ? ? ? ? ? File1 ?????????? ? ? ? ? ? File2 ?????????? ? ? ? ? ? File3 ?????????? ? ? ? ? ? File4 ?????????? ? ? ? ? ? File5 tried to use "nostrict" option but it makes no changes
It appears this is an issue with the burning software writing invalid permissions to the UDF filesystem. An ubuntu bug [1] has more information, but could you please try using the umask=777 mount option, and see if that solves the problems you're encountering? [1] https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/10550
Umask 777 removes all rights on this medium /dev/sr0 on /mnt/blr type udf (ro,noexec,nosuid,nodev,,uid=1001,gid=100,iocharset=utf8,umask=777) d--------- 7 ondrej2 users 464 May 12 21:17 . drwxr-xr-x 8 root root 216 May 13 11:05 .. d--------- 2 ondrej2 users 152 May 12 21:17 File1 d--------- 2 ondrej2 users 184 May 12 21:17 File2 d--------- 2 ondrej2 users 180 May 12 21:17 File3 d--------- 2 ondrej2 users 168 May 12 21:17 File4 d--------- 2 ondrej2 users 224 May 12 21:17 File5 Under user I am unable even to list corrupted rights
Sorry, you're quite right, I got the umask bits completely the wrong way round (teaches me for mindlessly copying from ubuntu bugs, they made the same mistake and were corrected further down). Could you try with umask=007 (which should give -rwxrwx--- permissions) please?
(In reply to comment #11) > Sorry, you're quite right, I got the umask bits completely the wrong way round > (teaches me for mindlessly copying from ubuntu bugs, they made the same mistake > and were corrected further down). > > Could you try with umask=007 (which should give -rwxrwx--- permissions) please? > I went thru this path already and none of umask helps, but however I did umask=007 again and it makes absolutely no change. So same situation here with different.
One more thing. Umask 007 gives drw-rw---- and not -rwxrwx--- as expected. Is this some trigger?
No, that suggests that the umask is having no effect on the permissions, which is unusual. I don't know what else to suggest I'm afraid, perhaps try a different burner?
Your expected permissions are wrong as well. From your comment #4: > ll /mnt/blr/ > total 12 > drw-r--r-- 7 1005 users 464 May 12 21:17 . > drwxr-xr-x 8 root root 216 May 13 11:05 .. The . entry is a directory, and therefore MUST have +x on all portions. This is actually coming from the media, not the mountpoint. I don't have any tools to debug UDF images on hand right now, but try to see if iso-info from libcdio will give you an ls -lR style display (without mounting the media).
try umask=0 I use it all the time when working with USB keys
