#NTFS 3G FOR OS X INSTALL#
#NTFS 3G FOR OS X 32 BIT#
#NTFS 3G FOR OS X PRO#
#NTFS 3G FOR OS X CODE#
#NTFS 3G FOR OS X WINDOWS 7#

OSXFUSE does something wrong it is not in control over the NTFS Happens with OSXFUSE and not MacFUSE then it's strange, but even if NTFS-3G mailing list (the forum is not working so well these days.Īll the spam has made it quite unusable). If the corruption happens with NTFS-3G, I would recommend the Hope you guys can help me out with this problem! I've attached a file containing chkdsk output after running test 3, if that helps out any. I did a few ad hoc tests with just copying files without creating a folder first, and that worked fine sometimes, but not always. I turned on debug logging in NTFS-3g, but didn't see anything noteworthy, just some messages related to mounting the 2 NTFS drives in my box. 1 file survived the copy + chkdsk, the resource fork files survived, but the other files were truncated to 0 bytes. ABC folder and copied files disappeared after chkdsk completed.Ĭhkdsk reported corruption.

#NTFS 3G FOR OS X WINDOWS 7#

Afterwards, I rebooted into Windows 7 and ran chkdsk /f on the drive.Ĭhkdsk reported corruption. The files varied in size from 150 MB - 1 GB. (FWIW, the drive is 1 TB, with about 15 GB free space.) For the test, from within the Finder I created a new folder called 'ABC' in the root directory, then copied 5 files (plus their associated '._' resource fork files, which get copied automatically) from the OS X boot drive to the data drive, into a DIFFERENT empty folder off the root, NOT the 'ABC' folder first created. The data drive has about 50 existing folders and files in the root directory, with various files and subfolders in each. Installed the latest OSXFUSE, 2.3.9, with MacFUSE compatibility layer selected, rebooted, then NTFS-3g 2010.10.2 with UBLIO caching turned on, and finally rebooted again. Then I switched the kernel to 64 bit, rebooted again. (I did NOT perform these tests with an external USB drive, if that makes any difference.)įirst I uninstalled NTFS-3g, rebooted, then the old MacFUSE, and rebooted again. The tests I performed were copying files from the OS X boot drive to the data drive, while booted into OS X.

#NTFS 3G FOR OS X PRO#

This Mac Pro has 3 internal SATA drives, an OS X boot drive (HFS+), a Windows 7 boot drive for Boot Camp (NTFS), and a data drive (also NTFS).

#NTFS 3G FOR OS X INSTALL#

I am planning to install Lion soon, so I wanted to test OSXFUSE + NTFS-3g in 64 bit mode. To recap, I have a 2008 Mac Pro running Snow Leopard 10.6.8.

#NTFS 3G FOR OS X 32 BIT#

I am still able to reproduce the corruption quite reliably, even after switching to the 32 bit kernel. I have finally gotten around to re-testing this corruption issue I was seeing previously, as mentioned above. If the corruption is on the data level and caused by OSXFUSE we would most likely see similar issues with other file systems, too. the file system itself is fine, evidenced by running chkdsk in Windows), then OSXFUSE could be to blame (not necessarily, but it's at least possible). In general, data corruption errors can be on the file data level or one the file system level. Would be much more likely than random corruptions written out to disk.

With regard to maintaining file system integrity is if its libfuseĬorrupted the NTFS-3G process memory space, but in that case a crash The only way OSXFUSE could influence NTFS-3G's operation Level and in that case, NTFS-3G itself is most likely to blame rather In this case it's not on the file data level but on the file system Then OSXFUSE could be to blame (not necessarily, but it's at least theįile system itself is fine, evidenced by running chkdsk in Windows), In general, data corruption errors can be on the fileĭata level or one the file system level. > Erik, what is your opinion on this? Have you heard of similar issues?

OSXFUSE just passes file system operations along. > But just to make this clear: OSXFUSE does not write to the physical drive. To track this issue down you could boot Snow Leopard in 32 bit kernel mode and 'try' to get some data corruption errors using OSXFUSE and NTFS-3g.

#NTFS 3G FOR OS X CODE#

> I wonder if those corruption errors are linked to the 64 bit kernel code or OSXFUSE/NTFS-3G in general. Of note, I never saw disk corruption when using MacFUSE and this same NTFS-3g build, under the 32 bit kernel in Snow Leopard.

Ntfs 3g for os x