First of all, thanks for ntfs-3g! :-)

I'm using NTFS-3G on FreeBSD 6.2 to access my Windows partitions. Mounting goes ok, despite



but after browing a while, I see this error in /var/log/messages



and Konqueror (which I'm using to browse the hd) hangs. Top /ps show ntfs-3g using quite a lot of processor time, but I have no clue what it is doing.

Hi. Do you use ntfs-3g from here?
http://www.freshports.org/sysutils/fusefs-ntfs

Yes, everything on my system is build from ports (some packages are just fetched, not build, such as KDE, and Xorg, since they take a lot of time to build).

Looked a bit deeper in this, but I think I narrowed it down to an underlying NTFS-corruption issue.

The drive suffered/filesystem some damage a while ago when Windows BSOD at an unfortunate moment. chkdsk recovered the damage, but apparently not as well as it should :-(

Yes, it looked either a FreeBSD porting issue or NTFS corruption. But since this "ntfs_attr_pread returned less bytes" problem haven't been reported by Linux, FreeBSD, etc users thus it indeed seems more like another Windows NTFS bug. This is not so surprising, we regularly meet with them, e.g.

http://support.microsoft.com/kb/925308/
http://support.microsoft.com/kb/831374/
http://support.microsoft.com/kb/873437/

One day I plan to collect and document all these Microsoft NTFS bugs.

Unfortunately it's also true that chkdsk isn't very good. Sometimes it can even remove completely valid files, so it's strongly recommended to make a full backup before running it!!

Thanx for the reply! Darn those Windows Bugs, but at least I can now use ntfs-3g to check dirs for corrupt files ;-) I'm still utterly confused as to why chkdsk misses those issues, but then again, I never really understand MS as it comes to their software...

As for backing up... It is a 250GB drive, so difficult to backup to convential media and it isn't important enough use professional backup equipment.