Results 11 to 12 of 12
Enjoy an ad free experience by logging in. Not a member yet? Register.
- Join Date
- Apr 2005
Problems with writing to a mounted windows fat32 partition
I have been having no problems to write and read from my FAT32 partition, now that the partition is 95.6% full, i can not write on it anymore.
My fstab is:
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/hda8 swap swap defaults 0 0
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0
/dev/hda5 /mnt/data_fat32 vfat rw,umask=000,uid=500,gid=500 0 0
/dev/hda1 /mnt/windows vfat rw,umask=000,uid=500,gid=500 0 0
//ARMANDA/ARMANDA_INCOMING /mnt/armanda_incoming/ smbfs credentials=/root/.smbcredentials,uid=atreyu,workgroup=PITUFOLANDIA, rw
The fdisk -l output is:
Disk /dev/hda: 40.0 GB, 40007761920 bytes
16 heads, 63 sectors/track, 77520 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 23652 11920198+ c W95 FAT32 (LBA)
/dev/hda2 23652 77505 27141817+ f W95 Ext'd (LBA)
/dev/hda5 23652 62396 19526976 4 FAT16 <32M
/dev/hda6 62397 62598 101776+ 83 Linux
/dev/hda7 62599 76464 6988432+ 83 Linux
/dev/hda8 76465 77504 524128+ 82 Linux swap
When I try to free some space (being root, or normal user) from the hda5 (the partition in question), it tells me i have no permisson. I can write on some zones of this partition, and not on others, located randomly at first glance.
The weird thing is that this started happening suddenly, and apparently without any cause. In addition, partitions hda1 and hda5 should be of the same type (vfat, fat32) and now, out of the blue, hda5 is fat16 < fat32.
I am desperate, and this is begining to block my computer, as day after day I find more folders in hda5 where I can not write at all.
One more thing: when the system begins to stop giving me write access to a file, the content of the file appears to be corrupted.
Hope any of you have an idea to fix this!
Weird, that FAT 16 < 32 thing is usually for FAT 16 drives smaller than 32Mb. Is there less than that left free on the drive? Maybe your system is picking the drive up wrong because of that. (if you don't know how to find the free space, tryCode:
df -hThere are two major products that come out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence.
- Jeremy S. Anderson