You are not logged in.
how can i create a shared partition?--that is, i already have an hda6, which i want to be accessible to any users--they can read and write.
i tried umask=0666 option in fstab:
/dev/hda6 /mnt/hda6 ext3 noatime,users,umask=0666 0 1
but i get this error:
# mount /dev/hda6
mount: wrong fs type, bad option, bad superblock on /dev/hda6,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
if i remove umask it is fine. why is that? i wanted to do it in fstab, but how can i do this?
Offline
I seem to recall that the umask is inverted to get the result. So, to give everyone read and execute access for example, you would use a umask of 222.
2 = 0 1 0
r w x
Inverting this allows everyone read and excute, but not write. You want to give everyone read, write and execute - you want a umask of zero. Your current selection denies all access to everyone, hence the error you receive.
Cast off the Microsoft shackles Jan 2005
Offline
By the way, wouldn't a more controlled approach be to create a normal partition, and then add a "common" or "group" or some other top level folder that was owned by a particular group to which all of the people you want to grant access belong? This gives you control over who gets access and who doesn't. It also lets you, for example, give the key people read and write access, and everyone else just read access. Seems safer and easier to administer than just opening up the whole partition for everyone.
Cast off the Microsoft shackles Jan 2005
Offline
thank you mac57. i simply wanted to have a partition for music, etc.. that users could share. your suggestion is good, but it still troubles me that i get the error.
it doesnt seem to be a problem with the values. if i try umask=222, umask=0222, or even gid=users,fmask=117,dmask=007, i get pretty much the same error, i think it has to do with something else. this is the error:
]# mount /dev/hda6
mount: wrong fs type, bad option, bad superblock on /dev/hda6,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
and dmesg:
# dmesg | tail
Inbound IN=ppp0 OUT= MAC= SRC=221.208.208.202 DST=210.5.114.64 LEN=485 TOS=0x00 PREC=0x00 TTL=50 ID=0 DF PROTO=UDP SPT=54996 DPT=1026 LEN=465
Inbound IN=ppp0 OUT= MAC= SRC=221.203.145.29 DST=210.5.114.64 LEN=780 TOS=0x00 PREC=0x00 TTL=49 ID=0 DF PROTO=UDP SPT=35137 DPT=1026 LEN=760
Inbound IN=ppp0 OUT= MAC= SRC=204.16.208.102 DST=210.5.114.64 LEN=453 TOS=0x00 PREC=0x00 TTL=52 ID=0 DF PROTO=UDP SPT=33118 DPT=1026 LEN=433
Inbound IN=ppp0 OUT= MAC= SRC=204.16.208.102 DST=210.5.114.64 LEN=453 TOS=0x00 PREC=0x00 TTL=52 ID=0 DF PROTO=UDP SPT=33118 DPT=1027 LEN=433
Inbound IN=ppp0 OUT= MAC= SRC=221.10.158.140 DST=210.5.114.64 LEN=776 TOS=0x00 PREC=0x00 TTL=52 ID=0 DF PROTO=UDP SPT=60254 DPT=1027 LEN=756
Inbound IN=ppp0 OUT= MAC= SRC=222.37.19.216 DST=210.5.114.64 LEN=90 TOS=0x00 PREC=0x00 TTL=44 ID=12960 PROTO=UDP SPT=2005 DPT=17130 LEN=70
EXT3-fs: Unrecognized mount option "umask=222" or missing value
Inbound IN=ppp0 OUT= MAC= SRC=69.3.92.152 DST=210.5.114.64 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=16380 DF PROTO=TCP SPT=3582 DPT=15118 WINDOW=64800 RES=0x00 SYN URGP=0
Inbound IN=ppp0 OUT= MAC= SRC=69.3.92.152 DST=210.5.114.64 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=16843 DF PROTO=TCP SPT=3582 DPT=15118 WINDOW=64800 RES=0x00 SYN URGP=0
Inbound IN=ppp0 OUT= MAC= SRC=69.3.92.152 DST=210.5.114.64 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=17225 DF PROTO=TCP SPT=3976 DPT=445 WINDOW=64800 RES=0x00 SYN URGP=0
it is like that whatever value i put. if i remove the *mask options, the device can be mounted ok. i think it may be something else, some configuration... somewhere.... but i have no idea. any advice?
Offline
ok, im sorry, i think i have an idea.. umask is only for ntfs format, or at least does not apply to ext3.
Offline
umask is for filesystems that do not have any file permissions present, such as vfat. As linux requires file/directory permision info, what umask does is create a default set of 'permissions' so to speak on the filesystem.
Maybe just try:
/dev/hda6 /mnt/hda6 ext3 deafults,users 0 1
that should share all the directory. I think you will have to chmod 777 /mnt/hda6 to allow users to create files and folders in the root directory.
Offline
umask is for filesystems that do not have any file permissions present, such as vfat. As linux requires file/directory permision info, what umask does is create a default set of 'permissions' so to speak on the filesystem.
Maybe just try:
/dev/hda6 /mnt/hda6 ext3 deafults,users 0 1that should share all the directory. I think you will have to chmod 777 /mnt/hda6 to allow users to create files and folders in the root directory.
AFAIK "users" would make all the users able to mount/umount the fs, but won't solve what he wants (or at least what I think he wants): everyone to have rw access to all the files...
Offline
You're complicating things:
mount /mnt/hda6
chown -Rv youruser:users /mnt/hda6
chmod -Rv 775 /mnt/hda6
Mind the -R switches: they work recursively! Not a problem if the partition is empty.
cf. mac57
A bus station is where a bus stops.
A train station is where a train stops.
On my desk I have a workstation.
Offline
You're complicating things:
mount /mnt/hda6 chown -Rv youruser:users /mnt/hda6 chmod -Rv 775 /mnt/hda6
Mind the -R switches: they work recursively! Not a problem if the partition is empty.
cf. mac57
The problem there is that AFAIK new files created by those users will still have permissions 644, unless the command is runned every time a new file is created.
Offline
I don't get the problem.
If it's on a VFAT filesystem: mount with 'dmask=007,fmask=117' and make sure your users are in the same group.
If it's on Ext, Reiser...: mount it as you like, put your users in the same group and make sure everyone has 'umask 002' in their .bashrc.
1000
Offline