tag:blogger.com,1999:blog-3156578562014006371.post607979900070275721..comments2023-09-23T18:48:06.541+02:00Comments on NTFS-3G for Mac OS X: NTFS-3G 1.2506Erikhttp://www.blogger.com/profile/18326970669258666618noreply@blogger.comBlogger38125tag:blogger.com,1999:blog-3156578562014006371.post-5358864593361716412008-05-30T10:32:00.000+02:002008-05-30T10:32:00.000+02:00Yes! No more waiting for ntfs-3g at shutdown. Cool...Yes! No more waiting for ntfs-3g at shutdown. Cool. My MacBook (10.5.3--intel) shut down so fast I didn't even have a chance to read the (verbose) messages...<BR/>[Btw, BlueHarvest does indeed solve the resource fork problems.]rocketmousehttps://www.blogger.com/profile/01146655222676357812noreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-64776699461977605592008-05-30T07:58:00.000+02:002008-05-30T07:58:00.000+02:00Anonymous, May 29, 2008 6:22 PM:A workaround is in...Anonymous, May 29, 2008 6:22 PM:<BR/><BR/>A workaround is included in the latest version of the package, released today.Erikhttps://www.blogger.com/profile/18326970669258666618noreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-76452098091412404292008-05-29T18:22:00.000+02:002008-05-29T18:22:00.000+02:00any update on how the fix for the 30 second shutdo...any update on how the fix for the 30 second shutdown issue is coming along?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-2184690804918248262008-05-28T20:42:00.000+02:002008-05-28T20:42:00.000+02:00Mac OS X 10.5.3 released! NTFS-3G 1.2506 works wit...Mac OS X 10.5.3 released! NTFS-3G 1.2506 works with them (tested on Intel Mac)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-4948162474447661052008-05-26T03:26:00.000+02:002008-05-26T03:26:00.000+02:00aaron:If you would have read the "known issues" se...aaron:<BR/><BR/>If you would have read the "known issues" section in the release post, you wouldn't be so confused. :)<BR/>Hint: it's issue number two.<BR/><BR/>It's essentially the Finder that isn't constructed with other file systems than HFS+ in mind, enforcing limitations that make no sense to other file systems than HFS+.Erikhttps://www.blogger.com/profile/18326970669258666618noreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-83146050511372010212008-05-26T01:27:00.000+02:002008-05-26T01:27:00.000+02:00this is really strangeIt works with the regular cp...this is really strange<BR/>It works with the regular cp command, but not through the apple file manager? Any ideas as to why?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-27195100107714173192008-05-25T19:47:00.000+02:002008-05-25T19:47:00.000+02:00Hi Erik,I'm having troublewith ntfs-3g.There are t...Hi Erik,<BR/><BR/>I'm having trouble<BR/>with ntfs-3g.<BR/>There are two NTFS partitions which I'm transferring files between..<BR/>but strangely, files with UTF8 characters won't transfer over. Putting<BR/>pt_BR or pt_BR.UTF-8 in the .ntfs-locale file of both drives doesn't seem to do<BR/>anything. Where am I going wrong? <BR/><BR/>-Thanks in advance.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-8360359416204099112008-05-21T07:40:00.000+02:002008-05-21T07:40:00.000+02:00rocketmouse:The shutdown issue affects all mounted...rocketmouse:<BR/><BR/>The shutdown issue affects all mounted partitions, internal or external. However, if you use the stable version, there's less need to worry about it.<BR/><BR/>Thanks for the info about BlueHarvest, I hadn't heard about it. I'll try it out some day.Erikhttps://www.blogger.com/profile/18326970669258666618noreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-19481843026643074912008-05-20T10:25:00.000+02:002008-05-20T10:25:00.000+02:00WOW! Thank you! Not only can I now write to my Boo...WOW! Thank you! Not only can I now write to my BootCamp partition again (internal, MacBook 2GHz Duo 10.5.2) but the machine started up noticeably faster. What a bonus! I didn't uninstall anything ntfs-3g that came along from Tiger... because I didn't know how, ahem. Being an 'ancient' DOS-person myself I can just barely follow along. For the person who asked about the resource forks, BlueHarvest might just do the trick. I haven't restarted in Windows yet so I can't say for sure.<BR/>I'm assuming I don't need to unmount when it's an internal partition? On the other hand, I did have some problems with 'hangs' on shutdown in 10.4.11 so I'd better ask.rocketmousehttps://www.blogger.com/profile/01146655222676357812noreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-28651178072040263482008-05-18T05:24:00.000+02:002008-05-18T05:24:00.000+02:00cvparker:It's not related to the NTFS-3G driver re...cvparker:<BR/><BR/>It's not related to the NTFS-3G driver really, but to the way Mac OS X handles resource forks. A file in Mac OS X consists of two streams of data... the "data fork" and the "resource fork". These "._"-files constitute the resource forks of the files, which is used by Mac OS X to store metadata about the file.<BR/><BR/>I know it can be annoying, and I think there is a way to turn it off, but you should be looking in a more general direction as this is an issue with all non-HFS+ file systems used under OS X, for instance when you use a FAT drive, or mount network shares.Erikhttps://www.blogger.com/profile/18326970669258666618noreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-29079001939417295112008-05-18T03:12:00.000+02:002008-05-18T03:12:00.000+02:00Thank you for this utility. Forgive me if this is...Thank you for this utility. Forgive me if this is not the right place to post this. I'm running on a MacBook with 10.5.2. When I copy a file (test.txt) from my mac partition to the NTFS partition, and then reboot into windows XP, there are two files, test.txt, and another called ._test.txt. Is this expected? Can it be turned off?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-10118361347184535812008-05-16T18:27:00.000+02:002008-05-16T18:27:00.000+02:00Dude, you rock! thanks againDude, you rock! <BR/><BR/>thanks againAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-59052008840991897652008-05-13T22:17:00.000+02:002008-05-13T22:17:00.000+02:00Erik:Yes, my NTFS partition labeled as '750GB' and...Erik:<BR/><BR/>Yes, my NTFS partition labeled as '750GB' and this label was shown before.<BR/><BR/>PS. Probably things goes wrong after I'd reformatted my HD with 16KB blocks instead of standard 8Kb, using Acronis Partition Manager.Andrew Stromnovhttps://www.blogger.com/profile/11554041615926707670noreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-53762552851082189902008-05-13T22:07:00.000+02:002008-05-13T22:07:00.000+02:00Andrew Stromnov:Good to hear. The check for whethe...Andrew Stromnov:<BR/><BR/>Good to hear. The check for whether ntfslabel succeeded or not will be disabled in future releases because of this buggy behaviour. This means label lookup will fail silently.<BR/><BR/>Have you got a label on your drive, and has it shown correctly as the mount point name earlier?Erikhttps://www.blogger.com/profile/18326970669258666618noreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-32538512287445947612008-05-13T21:51:00.000+02:002008-05-13T21:51:00.000+02:00erik:Sorry for delay - I was quite busy last week....erik:<BR/><BR/>Sorry for delay - I was quite busy last week.<BR/><BR/>After changing<BR/>if ( [[ ${NTFSLABEL_RETVAL} -ne 0 ]] || [[ -n "${READONLY}" ]] ); then<BR/>with:<BR/>if ( [[ -n "${READONLY}" ]] ); then<BR/><BR/>automounting starts working again in RW mode with volume label 'Untitled'. Thank you for your help!Andrew Stromnovhttps://www.blogger.com/profile/11554041615926707670noreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-39067512376764732752008-05-13T18:31:00.000+02:002008-05-13T18:31:00.000+02:00Szabolcs:Sounds great. :) Thanks for the effort.I ...Szabolcs:<BR/><BR/>Sounds great. :) Thanks for the effort.<BR/>I still rely on a few of these ntfsprogs (ntfscat, ntfsls, mkntfs), so there is still a long way until I can throw them away completely. They may all have similar bugs, but as long as nobody complains I guess there's no immediate reason to fix what isn't proven broken.Erikhttps://www.blogger.com/profile/18326970669258666618noreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-38659657190321224132008-05-13T12:11:00.000+02:002008-05-13T12:11:00.000+02:00This comment has been removed by a blog administrator.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-41569956221737287932008-05-13T10:38:00.000+02:002008-05-13T10:38:00.000+02:00Erik: Okey :-) Then I try to find the time to add ...Erik: <BR/><BR/>Okey :-) Then I try to find the time to add ntfs-3g.label to the next NTFS-3G release.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-52365394038803344892008-05-12T22:00:00.000+02:002008-05-12T22:00:00.000+02:00Szabolcs:I am using ntfs-3g.probe, don't you worry...Szabolcs:<BR/><BR/>I am using ntfs-3g.probe, don't you worry. :> However, ntfs-3g.probe won't fetch and print the actual label of the drive, or am I misunderstanding something?<BR/>I need to get the volume name of the drive and return it to the OS X's DiskArbitration subsystem before the mount, so I can't see any other way than using ntfslabel at the moment.Erikhttps://www.blogger.com/profile/18326970669258666618noreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-8933099330251026972008-05-12T21:49:00.000+02:002008-05-12T21:49:00.000+02:00anonymous @ 11:05, I believe that was a different ...anonymous @ 11:05, <BR/>I believe that was a different bug than the one labeled here as serious.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-52111786237046473672008-05-12T21:31:00.000+02:002008-05-12T21:31:00.000+02:00ntfslabel is not relible. ntfs-3g.probe should be ...ntfslabel is not relible. ntfs-3g.probe should be used which was developed as a replacement specifically for NTFS-3G for OS X ;-)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-58253660551892728912008-05-12T19:21:00.000+02:002008-05-12T19:21:00.000+02:00Andrew Stromnov:Okay, then I guess there might be ...Andrew Stromnov:<BR/><BR/>Okay, then I guess there might be a bug in the ntfslabel utility. I'm not using the latest version of ntfslabel because of other, newer bugs that are more serious.<BR/><BR/>Did you try to modify the ntfs-3g.util file as I said?Erikhttps://www.blogger.com/profile/18326970669258666618noreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-8197232319056937712008-05-12T13:16:00.000+02:002008-05-12T13:16:00.000+02:00Invoking ntfslabel and ntfsls leads to "Input/outp...Invoking ntfslabel and ntfsls leads to "Input/output error", but mounting thru console works well:<BR/>ntfs-3g /dev/disk1s5 /tmp/ntfs<BR/><BR/>Seagate FreeAgent Pro 750Gb,<BR/>USB, primary partition, NTFS, 16Kb per block.Andrew Stromnovhttps://www.blogger.com/profile/11554041615926707670noreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-1407321870334785622008-05-12T11:25:00.000+02:002008-05-12T11:25:00.000+02:00PSobral:The serious issue is for all cases, all co...PSobral:<BR/><BR/>The serious issue is for all cases, all computers. It's not particularly serious if you use the stable version, as the chance of any corruption is really tiny. With the ublio version though, you may experience that the last file system operations that you did never made it to disk at the time of shutdown because it's still in the memory cache and never got committed to disk.<BR/>I have experienced this a few times, copying a few files to the ntfs drive, immediately restarting to Windows and finding that the files aren't there.Erikhttps://www.blogger.com/profile/18326970669258666618noreply@blogger.comtag:blogger.com,1999:blog-3156578562014006371.post-37859439233608031492008-05-12T11:19:00.000+02:002008-05-12T11:19:00.000+02:00Andrew Stromnov:By some reason the "ntfslabel" com...Andrew Stromnov:<BR/><BR/>By some reason the "ntfslabel" command returns 1, instead of 0, which is what should happen with a normal volume.<BR/>I haven't seen that before, but in fact this check is a bit obsolete... I'm not sure it's needed.<BR/><BR/>See what response you get if you disable the check by editing the file /System/Library/Filesystems/ntfs-3g.fs/ntfs-3g.util and replace line 435:<BR/><BR/>if ( [[ ${NTFSLABEL_RETVAL} -ne 0 ]] || [[ -n "${READONLY}" ]] ); then<BR/><BR/>with:<BR/><BR/>if ( [[ -n "${READONLY}" ]] ); then<BR/><BR/>You can use the nano text editor, it should be available everywhere. (sudo nano /System/Library/Filesystems/ntfs-3g.fs/ntfs-3g.util)Erikhttps://www.blogger.com/profile/18326970669258666618noreply@blogger.com