[SOLVED] fstab mount permissions for ext3 drive in Lucid Lynx
UbuntuThis forum is for the discussion of Ubuntu Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
fstab mount permissions for ext3 drive in Lucid Lynx
I am having some permission issues on my non-boot ext3 partition on lucid. It mounts properly, but I cannot create/delete anything on that partition without sudo. As a workaround I created a directory with in that partition with proper permission for every user. But that is not exactly what I want! I guess, there must be a way to mount with all permissions for the user.
Here is my fstab file, and the partition with problem is UUID=2846e47e-f3cf-4eaa-a64f-6c4fdd4043b0 mounted at /Partitions/Docs/ (line 12-13):
# /etc/fstab: static file system information.
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=fc703dda-3626-49ca-858f-f221379c6af5 / ext3 errors=remount-ro 0 1
# /Partitions/Docs/ was on /dev/sda3 during installation
#UUID=2846e47e-f3cf-4eaa-a64f-6c4fdd4043b0 /Partitions/Docs/ ext3 defaults 0 2
UUID=2846e47e-f3cf-4eaa-a64f-6c4fdd4043b0 /Partitions/Docs/ ext3 rw,suid,dev,exec,auto,user,async,relatime 0 2
# /Partitions/fat32/ was on /dev/sda6 during installation
UUID=B00D-9DC9 /Partitions/fat32/ vfat utf8,umask=007,gid=46 0 1
# /tmp was on /dev/sda5 during installation
UUID=72c2966e-9d1d-49b5-9f39-c19557a4f6e6 /tmp ext3 defaults 0 2
# swap was on /dev/sda2 during installation
UUID=c5c46f54-75da-4961-8277-c839f8f51314 none swap sw 0 0
Also, for this partition and for the fat32 partition (/Partitions/fat32), I cannot move any file to trash, they get deleted completely without a trace. I guess this problem is connected with the permission issue for the ext3 partition. Is it? And is there a way to avoid this in the fat32 partition?
There are probably better ways as I am not great with command line but I solved the same problem on my system doing this. In a terminal type "gksudo nautilus" and enter your pass word when prompted.This will have
you running your file mgr. as root ( real root not sudo),be careful.
Stay within nautilus and you can change the permissions of your drive.
make sure you tell it to change the permissions on the directories and
sub directories also. Just be careful and you should be able to solve your problem. I xfered about 500gb of data last week after fixing the same problem. Good Luck. Maury.
As for you not being able to create/write to the drive, you should check the permissions. I presume that root owns the top directory, so you will need to change those perms appropriately for your user.
Also - by default, external drives are owned by root if they are fat32/NTFS and I don't think there is anyway around this other than to elevate your privileges or sudo.
File permissions still apply to any mounted drive in Linux.
I am having some permission issues on my non-boot ext3 partition on lucid. It mounts properly, but I cannot create/delete anything on that partition without sudo. As a workaround I created a directory with in that partition with proper permission for every user.
It seems to me, that you created by hand a similar directory structure as for "/home" directory, which probably resides on your boot partition mounted at "/", so the first question that comes to my mind is why you don't move the "/home" directory to that partition. This would have many advantages.
If you want each user to have a separate, private, directory on that partition, you did it right, because it requires these directories to have different permissions for each user, and the directory /Partitions/Docs/ remains owned by root. Exactly as in /home directory.
However, if you want to grant all users rw rights to the root directory of that partition, i.e. /Partitions/Docs/ you must after mounting it change the rights to the mount point:
sudo chmod a+w /Partitions/Docs/
then try unmounting and remounting with default options. I tried it and it retained rw permissions.
Last edited by dr_agon; 05-03-2010 at 10:15 AM.
Reason: spelling in chmod line
Thanks Maury, Jeiku and dr_argon!
It worked as I changed the permission of the folder where the ext3 drive was being mounted as suggested by all of you.
I wanted all folders in /Partitions/Docs/ to be accessible to all, and changing permission of /Partitions/Docs/ did the trick. It retained the permission in subsequent remounts.
However, "move to trash" still doesn't work for the fat32 partition (it is not an external drive, though). I guess, as Jeiku said, there is no way around for fat32 partitions for this.