You are not logged in.
Pages: 1
I notice that I one of my mounted VFAT drives, after online for a while, is becoming read only. Why would this happen? To resolve it, I have to umount and then mount it. After a while, I have to do it again. Here's the relevant line in my fstab:
/dev/hdb1 /mnt/back vfat auto,umask=000,uid=1000,gid=100 0 0
My user id and gid are the ones you see above. Here's an ls -l output of that partition:
drwxrwxrwx 37 ralvy users 32768 2006-02-07 19:03 back
No writes or deletes can be done on that drive right now.
A few seconds later, after umount/mount of /mnt/back ...
All is fine again. Why?
I'm running Arch current/extra up to date.
Offline
This is my entry for my fat32 partition that automounts at boot
/dev/hdb1 /mnt/music vfat umask=0000,auto,users 0 0
It is what I used in Gentoo, and I just copied it into Arch, works great.
Into the great wide open without a clue
Registered Linux user 375921
www.google.com/linux is your friend to find stuff.
Offline
Check your syslog (/var/log/*). There might be something that tells you the reason (though I've only such this behaviour with ext2/3 so far).
Offline
Check your syslog (/var/log/*). There might be something that tells you the reason (though I've only such this behaviour with ext2/3 so far).
Found this for that day:
Feb 7 11:43:17 tux FAT: Filesystem panic (dev hdb1)
Feb 7 11:43:17 tux fat_free_clusters: deleting FAT entry beyond EOF
Feb 7 11:43:17 tux File system has been set read-only
So I just did
fsck -t vfat -a /mnt/back
and let it fix the problems. We'll see this stops it. Sounds like it will.
Thanks for the suggestion.
Offline
Pages: 1