Skip to contentSkip to conversation

2.6.0-test5-mm3 VFAT File system problem

DISCUSSION Benjamin Weber 2 participants 2 messages Sep 20, 2003

lore
Share & tools
lore
#0 lore raw

I can confirm this behavior.

I checked my fstab entry. Was saying:

/dev/hda5 /mnt/windows/D vfat rw,user,umask=0
0 0

After changing it to
/dev/hda5 /mnt/windows/D vfat
rw,user,uid=1001,gid=100 0 0

I got it working again half of the time. Its strange. Sometimes I get the message that only root can unmount it, even when I mounted it as user.

Something is a little whacky there.

--
Benjamin

Quoted 10 lines

Upon moving from -mm2 to -mm3, my vfat filesystems did not automatically bount at bootup as per the fstab and could not be accessed by applications in Gnome ie. my mount point showed no subdirectories or files.

I could manually mount (not by mount /mnt/win_c but by the full mount -t vfat /dev/hda1 /mnt/win_c) and I could explore using ls in terminals but programs in Gnome could not open the filesystem.

Upon rebooting into -mm2 everything was fine again.

#1 lore raw
Quoted 12 lines · Benjamin Weber

I can confirm this behavior.

I checked my fstab entry. Was saying:

/dev/hda5 /mnt/windows/D vfat rw,user,umask=0
0 0

After changing it to
/dev/hda5 /mnt/windows/D vfat
rw,user,uid=1001,gid=100 0 0

Quoted 5 lines

I got it working again half of the time. Its strange. Sometimes I get the message that only root can unmount it, even when I mounted it as user.

Something is a little whacky there.

Any mount option of the form `foo=0' will fail, because the parser is treating zero as an error.

I'll fix that up for -mm4, thanks.