it tells the kernels idea of what you have mounted and where it is mounted. its better than mount as it represents more the kernels idea which mount sometimes doesn't.

but like i said: from the path i think nfs blocks the directory.

do u know what scan im talking about? I plugged in the device, right clicked while in the internal memory on my pc, selected properties, then tools, and i clicked error checking. do you kno if it can be stopped while running because there is no cancel button just the X and usually these things cause problems when stopped mid progress.

im trying to be as detailed as I can so that you can help

Those files inside the nfs are corrupted/damaged, that might be the issue here

actually:no i don't know what scan you are running. but i take it, you just do it and don't care until you finished.

what i read is that you have some device you have somehow(presumably via nfs) mounted on you filesystem. and what i do know from what you say, is that you cannot delete anything from it.
everything else we need to find out. and nfs is prominent for locking something up for good. so thats my guess.

yea that's exactly the problem head on but this stupid scan won't finish fast enough for me to provide with what you need. I might just have to send it to you tomorrow, I'll keep you posted on the situation though

oh, the problem sometimes vanishes if you wait long enough.

yea because nothing is permanent

Due to the way linux filesystems work, the files and directories on a FAT partition get assigned permissions by the vfat driver even though FAT itself doesn't support permissions. This does, of course, mean you can't change them in the usual way, you can only change permissions by remounting the filesystem, and you can only go so far as setting a default mask that applies to all files on the filesystem, and a separate one for all directories. But as far as the kernel (aside from the vfat driver) and userspace utilities see the files, they do have permissions.

Eh? Does this mean something?

you can have permissions on the mount. but no way to temper in any way with permissions on directories or files for there is nothing to store them on the filesystem. precise enough?
i seconded what you said.

and look what we found out: the op mounted something and has problem with that mount.
lets see when he is finished checking the filesystem.

Well seeing as I was getting to delete one file at a time in the folder, what would you say about that? Would you say the entire file system is messed up or just that those files are damaged which they are by the way

when it calls you a bonehead you know that you are checking a mounted filesystem.
i might been wrong with the nfs just guessed it from the pathname. say, what is that thing you had mounted?

edit: no offense! that "bonehead" thing is really the errormessage you get after a while when you try to check a mounted filesystem. it realy says that,