LinuxQuestions.org - same fstab, new problems

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - same fstab, new problems (https://www.linuxquestions.org/questions/debian-26/same-fstab-new-problems-85773/)

same fstab, new problems

I recentlly made the step to Sarge and last night as I was trying to listen to some music I observed that I couldn't access my vfat partitions.

How is that possible?
I made no change to the fstab and as the man page says no program will edit this file...I didn't edit it, the progs didn't so want is the problem?

I have all my music on my vfat partition (M$ legacy) and I had to listen music from windoze!!!
I hate it!!!

Have you tried mounting it from the console?
Whats your fstab looklike?

Hows the harddrives setup?

Quote:

Originally posted by leonscape
Have you tried mounting it from the console?

yes, as a user I can mount it only if root unmounts it.
the drive is mounted on startup but a normal user can't access it..

Quote:

Whats your fstab looklike?

Hows the harddrives setup?

Code:

# /etc/fstab: static file system information.

#

# <file system>        <mount point>        <type>        <options>                <dump>        <pass>

/dev/hda1        /                ext3        errors=remount-ro        0        1

/dev/hda5        /home                ext3        errors=remount-ro        0        1

/dev/hda9        none                swap        sw                        0        0

proc                /proc                proc        defaults                0        0

/dev/fd0        /mnt/floppy        auto        user,noauto                0        0

/dev/cdrom        /mnt/cdrom        iso9660        ro,user,noauto,noexec                0        0

/dev/cdrom1        /mnt/cdrom1        iso9660        ro,user,noauto,noexec                0        0

#/dev/hda6        /mnt/movie        vfat        user,auto,noexec                0        0

#/dev/hda7        /mnt/data        vfat        user,auto,noexec                0        0

#/dev/hda8        /mnt/kits        vfat        user,auto,noexec                0        0

/dev/hda6        /mnt/movie        vfat        user,auto,user,noexec                0        0

/dev/hda7        /mnt/data        vfat        user,default                0        0

/dev/hda8        /mnt/kits        vfat        user,default                0        0

The commented lines with /mnt/kits and so on are the settings that I used before the upgrade and worked fine.

They are now like this because I tried some other combinations to see if they work

Does it work without auto?

Also try using auto as the filesystem type, see if that help.

It works with auto, but only root can browse the /mnt/xxxx dirs (vfat ones)

try adding nosuid to the options

Edit:
and or users

Quote:

Originally posted by leonscape
try adding nosuid to the options

Edit:
and or users

You mean that I should replace user with nosuid in the option field?

Direct from man mount:

users:
Allow every user to mount and unmount the file system. This option implies the options noexec, nosuid, and nodev (unless overridden by subsequent options, as in the option line users,exec,dev,suid).

Users could replace user, nosuid is a slightly diffrent option, and would have to be put in as well as user. (but is unecssary with users)

If that makes sense.

In the options section, add in "gid=<your group name>,uid=<your user number>". That should work. I think the mount commands work slightly differently under woody and sarge. That's what caused the problem...

So, the elegant way would be to insert a gid=vfat_users and insert in that group whomever I want to access the vfat drives!!!

Ok, I will try this too.

the nosuid option had no effect only that I could mount the volumes when they were unmounted.

Yeah. You could also add in the group number of the users group (gid=100, I think). The user part if I recall is also pretty important. Try the group thing first and if that works then great. If not then you'll have to put in the uid option. I recall that there was a time that I didn't have to do this but recently, I did have to. Hence I believe that the newer version of mount works differently. I've always had to specify those options with ntfs, though. Linux is a lot pickier with ntfs. I don't run windows on this computer so I haven't messed around with those settings for a while now.

You may also want to change the "user" option to "users", and ditch the "noexec" and "default" options. I think that's what I had and it worked. At some point I even specified a "umask" option though I don't remember whether that was for the ntfs partition or for the vfat...

the gid option didn't work

when I run mount it says that the partitions are owned by the vfatusr - the group I made. My user is a member of vfatusr, also the root is a memeber.

This is the output

Code:

/dev/hda1 on / type ext3 (rw,errors=remount-ro)

proc on /proc type proc (rw)

devpts on /dev/pts type devpts (rw,gid=5,mode=620)

/dev/hda5 on /home type ext3 (rw,errors=remount-ro)

/dev/hda6 on /mnt/movie type vfat (rw,noexec,nosuid,nodev,gid=1002)

/dev/hda7 on /mnt/data type vfat (rw,noexec,nosuid,nodev,gid=1002)

/dev/hda8 on /mnt/kits type vfat (rw,noexec,nosuid,nodev,gid=1002)

automount(pid357) on /var/autofs/net type autofs (rw,fd=5,pgrp=357,minproto=2,maxproto=4)

automount(pid337) on /var/autofs/misc type autofs (rw,fd=5,pgrp=337,minproto=2,maxproto=4)





and this is fstab



# /etc/fstab: static file system information.

#

# <file system>        <mount point>        <type>        <options>                <dump>        <pass>

/dev/hda1        /                ext3        errors=remount-ro        0        1

/dev/hda5        /home                ext3        errors=remount-ro        0        1

/dev/hda9        none                swap        sw                        0        0

proc                /proc                proc        defaults                0        0

/dev/fd0        /mnt/floppy        auto        user,noauto                0        0

/dev/cdrom        /mnt/cdrom        iso9660        ro,user,noauto,noexec                0        0

/dev/cdrom1        /mnt/cdrom1        iso9660        ro,user,noauto,noexec                0        0

#/dev/hda6        /mnt/movie        vfat        user,auto,noexec                0        0

#/dev/hda7        /mnt/data        vfat        user,auto,noexec                0        0

#/dev/hda8        /mnt/kits        vfat        user,auto,noexec                0        0

/dev/hda6        /mnt/movie        vfat        gid=vfatusr,auto,noexec,user                0        0

/dev/hda7        /mnt/data        vfat        gid=vfatusr,,auto,user                0        0

/dev/hda8        /mnt/kits        vfat        gid=vfatusr,nosuid,auto,user                0        0

As u can see the partitions have different options (changed them over an over again!!!).

Any Ideas?!?!?
I will try the user group thing and so on...
I will inform u aboutr the results...

Also try adding umask=000, to allow everyone to read and write, or umask=002 to only allow group and owner to rw, and user to ro.

"umask=000" stops everyone from reading and writing. You can try to "uid=<your user number>" option and possibly the umask=007.

umask, uid, gid?

umask might be ok, gud might be ok(it doesn't work - at least now), but uid in fstab that's too much!!!!

What if I had a server that shared one partition over samba and I had 100 users that use the parttion?!?!?! that is just too much work (ok, it can be done through scripts) and gets fstab to giant sizes!!!