Jump to content
40 posts in this topic

Recommended Posts

Hey, I followed your post. I did the screenshots. Unfortunately, chkdsk didn't work. I'm thinking of reformating the hard drive but before this, I want to find the way to delete. I have to save my time first.

 

1. Show the list of files in /Volumes/Vista/ but I cannot go into "._."

 

Picture2.png

 

You should have used rm instead of rmdir, because in your case, it doesn't have the d (directory) attribute.

 

If that still doesn't work, post the output of ls -lai and ntfsinfo, as szaka had asked.

 

Go to /Volumes/Vista and type "ls -lai > ~/Desktop/ls.txt"

and then "/usr/local/bin/ntfsinfo -fvF ._. /dev/disk0s1 > ~/Desktop/ntfsinfo.txt" (replace disk0s1 with the corresponding Vista partition on your PC). Then post ls.txt and ntfsinfo.txt here, and let szaka have a look at it. He might know what's wrong with your file.

szaka, it happened again. This time it's the .fseventsd directory and underlying file.

I noticed this when I tried to delete .fseventsd from Windows, and it gave me a "not found" error.

 

ls1.txt

ls2.txt

ntfsinfo.txt

 

ls -lai gave the same inode for .fseventsd and .Trashes. Maybe that's why I've lost access to Trash on my NTFS drive...

 

I don't know how to do an ntfsinfo on files located inside directories, so there's only an ntfsinfo dump from the .fseventsd directory.

 

I haven't done a chkdsk /f on this problem, in case you need more information.

I hope this information helps.

Have you tried what I've said?

Do a disk check with leopard's disk utility, then try to delete them.

 

I deliberately let the affected file as is this time. Just giving time for szaka to see the problem. I'm getting curious as to what keeps causing this, and if keeping the problematic file for a while can help diagnosing the problem (and maybe lead to a fix for good), then I'll keep it for a while. :D

 

Don't know about 93bh, though...

szaka, it happened again. This time it's the .fseventsd directory and underlying file.

I noticed this when I tried to delete .fseventsd from Windows, and it gave me a "not found" error.

Very great info!

 

The two same directory inodes issue is definitely a corruption. It should never happen. Afaik, OS X allows this somehow but it is invalid on the file system level. The Linux kernel ensure this but apparently MacFUSE doesn't. We definitely need to investigate and fix this. Thanks a lot! I'll let our NTFS-3G for OS X expert know this issue.

 

Chkdsk should fix this problem and the above also explains your earlier chkdsk outputs.

 

Explanation for the "can't delete .Trash directory" problem: when a file is still in use by an application then it can be deleted but in real it gets renamed to something like .fuse_hidden0000000500000002. These .fuse_hiddenXXXXXXX files get removed automatically when no software use these files anymore. If there is any file in a directory (no matter if it was already "removed but still in use" or not) then removing the directory is not allowed. In the future we will eliminate these .fuse_hiddenXXXX files, so these problems shouldn't happen.

Very great info!

 

The two same directory inodes issue is definitely a corruption. It should never happen. Afaik, OS X allows this somehow but it is invalid on the file system level. The Linux kernel ensure this but apparently MacFUSE doesn't. We definitely need to investigate and fix this. Thanks a lot! I'll let our NTFS-3G for OS X expert know this issue.

 

Chkdsk should fix this problem and the above also explains your earlier chkdsk outputs.

 

Explanation for the "can't delete .Trash directory" problem: when a file is still in use by an application then it can be deleted but in real it gets renamed to something like .fuse_hidden0000000500000002. These .fuse_hiddenXXXXXXX files get removed automatically when no software use these files anymore. If there is any file in a directory (no matter if it was already "removed but still in use" or not) then removing the directory is not allowed. In the future we will eliminate these .fuse_hiddenXXXX files, so these problems shouldn't happen.

 

Wow, great! I'll be looking forward to the next release of NTFS-3g, then... :D

 

Hi back, I got the .txt

 

oh, lol. I'm boy and 15. I'm not nerd. :)

 

Well, you're never too young (or too old) to learn. :P

 

Have you tried what I've said?

Do a disk check with leopard's disk utility, then try to delete them.

 

Now that szaka has identified the problem, I tried your solution. No go.

Disk Utility gave me:

** /usr/local/bin/ntfsfix has been disabled because of volume corruption issues.

** If you still want to try fixing your volume, use /usr/local/bin/ntfsfix from the command line...

Error: Filesystem verify or repair failed.

 

Quoting NTFS-3G's own User Guide:

There is only limited support for checking and repairing NTFS file systems using free software at

this time. The best way to repair a damaged NTFS file system is without doubt by using chkdsk in

Windows.

The NTFS-3G package for Mac OS X includes a utility called ntfsfix (part of the ntfsprogs

collection), which can repair some fundamental inconsistencies of NTFS volumes.

This utility is currently not integrated with the file system bundle, and thus can't be invoked through

Disk Utility, because of reports that it has corrupted some users' NTFS drives.

If you want to try it out despite these warnings, you will have to invoke it manually, from the

Terminal. Type “man ntfsfix” for usage info.

 

I'll stick with chkdsk for the time being. :)

Wow, great! I'll be looking forward to the next release of NTFS-3g, then... :hysterical:

I consulted with our OS X lead developer who is providing the most advanced packages at http://macntfs-3g.blogspot.com and he didn't experienced, nor ever heard about this problem. Could you please try the latest version, released a few ours ago? 2009.1.1 Update 1. It has much better Finder integration, has a Preference Pane http://hem.bredband.net/catacombae/ntfs-3g...fpanescreen.png and so on.

 

@93bh: Thank you for the files. The file list looks strange. The inode numbers autogenerated, they are not the real ones. Perhaps you're using a very old, beta version of NTFS-3G? Do you know which version do you use and from where you downloaded? Unfortunately there are a lot of 3rd party NTFS-3G packages all over the internet and many are still using the old beta versions. Please use the latest Stable from http://macntfs-3g.blogspot.com

 

Thanks!

I consulted with our OS X lead developer who is providing the most advanced packages at http://macntfs-3g.blogspot.com and he didn't experienced, nor ever heard about this problem. Could you please try the latest version, released a few ours ago? 2009.1.1 Update 1. It has much better Finder integration, has a Preference Pane http://hem.bredband.net/catacombae/ntfs-3g...fpanescreen.png and so on.

 

I just installed MacFUSE 2.0.3 and the new NTFS-3G this afternoon. Let's just hope this really does fix the problem. :)

@93bh: Thank you for the files. The file list looks strange. The inode numbers autogenerated, they are not the real ones. Perhaps you're using a very old, beta version of NTFS-3G? Do you know which version do you use and from where you downloaded? Unfortunately there are a lot of 3rd party NTFS-3G packages all over the internet and many are still using the old beta versions. Please use the latest Stable from http://macntfs-3g.blogspot.com

 

Thanks!

Hey

 

I think I got Macfuse from code.google. I can't remember where I got NTFS-3G from. I installed them in early of October 2008.

I think iPC OSx86 have same version of NTFS-3G and Macfuse as mine. I can tell that file "._." appear in my laptop (with iPC OSx86 installed).

 

Edited: I got NTFS-3G from http://www.ntfs-3g.org/. i'm using Macfuse 1.7

 

I installed MacFuse 2.0.3 and NTFS-3G. i don't know what to do. :S

hi i have had this problem with the dreaded ._. file which cannot be deleted in windows it can be seen in explorer however any attempt to rename delete or open the file result in windows not being able to find the file location or whatever. i found that the program unlocker works in windows XP to delete the file. however i think what causes this particular resource fork is when in mac you have used candybar to change the icon of each hard drive or partition i found that when i reverted to default hdd icon in mac the files will no longer appear as the original hdd icons are not custom and do not need to be physically stored on the partition u wish to have the custom icon. i am now looking for a way to disable the creation of .ds_store files when browsing through my ntfs partitions as it basically leaves a .ds_store in every single location u use through finder. kind of annoying but i guess thats just how hfs file system works. i have tried the method mentioned in several places using google however those guides refer to disabling .ds_store file creation on network ntfs volumes and using that particular method had no effect when the ntfs partitions are local it still causes them to be created.

Hello,

 

Any news or issues with the latest version?

 

Thanks.

 

Looking good so far. No problems at all (yet). :fiery:

Seems like the new 2009 version does solve the problems I've been getting.

 

 

...

i am now looking for a way to disable the creation of .ds_store files when browsing through my ntfs partitions as it basically leaves a .ds_store in every single location u use through finder. kind of annoying but i guess thats just how hfs file system works. i have tried the method mentioned in several places using google however those guides refer to disabling .ds_store file creation on network ntfs volumes and using that particular method had no effect when the ntfs partitions are local it still causes them to be created.

 

Try using BlueHarvest. You can set it to clean .DS_Store files automatically and anywhere. Even on HFS+ partitions (if you want). I use it to clean all .DS_Store and ._* files on all my non-HFS partitions.

×
×
  • Create New...