Hi,

Iam using FC6. the problem is that i lose my FAT32 Permissions while am in between a session. to be more precise i lose my write permission for FAT32 but iam still able to read it. the only way to get the permission back to reboot.

can anyone plz tell me wat to do. why are the permissions lost.

thanks.

sounds like a bug somewhere in whatever driver is providing FAT32 support. Check syslog to see if that gives any hints.

I personally have never gotten write access to a FAT32 filesystem to work correctly.

driver?? all my iam using is the default. passing the permissions through fstab.

where is syslog located?

/var/log/syslog on my system. Its a plain-text file on debian, but log management varies 100% between distros, so you may have to do some digging.

As I understand linux, every filesystem must have a corresponding driver in the kernel. Many filesystems are built into the kernel (ext2 for example).

Be prepared to get your hands dirty if you really want to fix this.

Perhaps it would help if you told us how you're setting the permissions, i.e. show us the line in /etc/fstab. FAT32 filesystems don't support UNIX-style permissions, so just specifying the rw option won't work. You need to use the umask option and possibly the uid and gid options.

I wouldn't worry about the kernel drivers. The vfat module (which handles all FAT filesystems) is very widely used and quite reliable. It's much more likely that your configuration is wrong than that the kernel is broken.

here is the my fstab. please go thru it and tell me whr iam wrong.

LABEL=/ / ext4 defaults 1 1
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/hda1 /win/c vfat rw,exec,noatime,uid=500,,gid=500,user 0 0
/dev/hda5 /win/d vfat rw,exec,noatime,uid=500,,gid=500,user 0 0
/dev/hdb7 /win/e_avk vfat rw,exec,noatime,uid=500,,gid=500,user 0 0
/dev/hdb8 /win/f_avk vfat rw,exec,noatime,uid=500,,gid=500,user 0 0
LABEL=SWAP-hdb6 swap swap defaults 0 0
/dev/hdd /media/cdrom auto pamconsole,exec,noauto,managed 0 0
/dev/hdc /media/cdrecorder auto pamconsole,exec,noauto,managed 0 0
/dev/fd0 /media/floppy auto pamconsole,exec,noauto,managed 0 0


thanks.

Try adding "umask=000" to the options for your FAT32 filesystems and then re-mounting the filesystems. That whould make them writable to all users. With the uid-500 option, they should be writable to whoever user ID 500 belongs to (and root of course), but not to any other accounts.

Came across this old posting, probably solved by now but I had a similar experience recently and learnt Thanks to Guth from the Zenwalk forum) that Linux automatically suppresses write permissions when it detects a problem with the file system. Try verifying/reparing the Win file system, check the disk (if it hasn't failed by now) and that may solve the problem.

Clever stuff this Linux software!