i didnt know exactly where to put this so i chose this section...

i have a box with slackware v.12
2 hdd devices:
a)1 ide 20gb -ext3 (OS installed on this one) (hda1)
b)1 sata 500gb -vfat (sda1)

i have the sda1 mounted with -w -t vfat /xx location
shared with samba and nfs with rw sync
mainly 1 laptop with mandriva and 1 windows pc have access on the sda1
my shares work properly i have no real problem
i also use ktorrent or downloading some staff from ftp servers on the box
since i dont shutdown it
well after a recent crush / emergency shutdown during a problem with electricity on my area i went home and started up the system
i started all things like i used to
steps:
1. login
2.kde
3.ktorrent
4.ftp
5.samba
6.nfs

after a while a msg pop ups in ktorr saying that cant write becuase system is read-only
which is true
i need to stop nfs,samba(everything that is accessing the sda1), umount and then remount the hdd
after about 10 mins it happens again...

i suspect that the nfs is the problem
but i had this system on for about 3 months
why after the crush?
how can i fix it?
maybe i need to force a check on vfat? and how i do that?
thanks in advance

Why did you choose fat32 filesystem for your 500gb partition ?
It will get fragmented quickly especially if you use it as download storage
Your partition is accessed by network, so you can choose any good linux filesystem instead (ext3, reiserfs...)

it was a usb2 external hdd which had destroyed usb conection i opened him and connected it to a sata
it was already 40% with data
and seems like i found a way to fix it
after
#mount
i get some strange arguments after /dev/sda1 rw async and a olot of others i thought it was becuase of vfat)

mount -o defaults /dev/sda1 /somelocation fix it

it seems that the problem is still here but i decided to backup my data at 1tb usb external hdd and format the sata on the box at ext3 and see what happens,i hope it will fix it