Volume Name inconsistency and System Crashes after turning spotlight indexing on

[GoogleCodeExporter]

What steps will reproduce the problem?
1. sudo mdutil -i on /Volumes/volume (turned Volume indexing on on a ntfs-3g 
volume running 
on macfuse
2. after indexing is done system will crash  seriously (grey screen with the 
big "switch off"-
symbol). 
3. The name of the Volume shown in the Finder differs from the name it shows in 
Terminal or 
Apples Disk Repair Utility. In Finder it is called "Gigantus" (which is the 
original name), in the 
Disk Utility it is called "disk1s5", while the mount point has the name 
"Untitled". Another ntfs-3g 
volume on the same HDD has no name inconsistencies. 

What is the expected output? What do you see instead?
I want Spotlight to index my ntfs-3g volume. Instead I experience system 
instability. And I would 
like to restore the correct name of the volume.

What version of the product are you using? On what operating system?
macfuse 1.5.1, ntfs-3g 1.2531. Operating System is Mac OS 10.5.3

Please provide any additional information below.

Original issue reported on code.google.com by toma...@gmail.com on 27 Jun 2008 at 8:44

[GoogleCodeExporter]

By default, MacFUSE will not let Spotlight (or any other root process) have 
access to a MacFUSE volume. I don't know 
what options you are running ntfs-3g with, but you will have to explicitly 
opt-in so that Spotlight can work.

That said, I'm afraid I don't know what might be happening with ntfs-3g or Disk 
Utility. MacFUSE itself doesn't 
interact with disk utility.

If you can give me a reproducible case of a system crash that doesn't involve 
ntfs-3g (or is clearly MacFUSE's fault), 
I'll be happy to look at it.

Original comment by si...@gmail.com on 27 Jun 2008 at 10:02

• Changed state: Invalid

[GoogleCodeExporter]

tomasio: since OS X should never crash whatever ntfs-3g options are used and the
issue seem to be MacFUSE irrelevent thus I suggest to contact Apple because a 
pure
user space process should never be able to crash the operating system. It seems 
you
have found an OS X bug. Good luck.

Original comment by sz...@ntfs-3g.org on 28 Jun 2008 at 11:39

[GoogleCodeExporter]

an OS X bug? Oh no :.(

Okey, I will send it to Apple. Thank you in the meanwhile.

Original comment by toma...@gmail.com on 28 Jun 2008 at 5:19

[GoogleCodeExporter]

Can you post your panic log? It should be the most recently created file in 
/Library/Logs/PanicReporter/ folder. 
Lets just make sure that it is indeed not MacFUSE's fault.

Original comment by si...@gmail.com on 28 Jun 2008 at 5:29

[GoogleCodeExporter]

I attached the last two panic logs. The first documents a crash with indexing 
turned
on, the second with indexing disabled. I am really thankful that you are trying 
to
help me with this.

Original comment by toma...@gmail.com on 28 Jun 2008 at 6:13

Attachments:

• 2008-06-27-144831.panic
• 2008-06-27-193100.panic

[GoogleCodeExporter]

Based on your panic log, MacFUSE _is_ involved (the panic is file system 
related), but I can't say yet if it's 
MacFUSE's fault or OS X's fault. The panic itself is occurring outside of 
MacFUSE, but the file involved comes from 
a MacFUSE volume. I'll try to reproduce this and look into it.

Original comment by si...@gmail.com on 28 Jun 2008 at 6:30

• Changed state: New

[GoogleCodeExporter]

If I can be of any help, let me know!

Original comment by toma...@gmail.com on 28 Jun 2008 at 6:52

[GoogleCodeExporter]

I just had a kernel panic while saving a file to an sshfs-mounted volume. I'm 
hoping
that it's related and the panic log may help diagnose both cases. Attached 
panic log.

This has occurred occasionally for me; it's pretty darn rare. And of course, 
it's not
related to ntfs-3g; the remote mount is actually a ClearCase mvfs volume on a 
Solaris
box using ufs filesystem roots.

Original comment by dbk...@gmail.com on 7 Jul 2008 at 1:15

Attachments:

• panic.log

[GoogleCodeExporter]

dbkirk: The panic log you posted is for the following issue (not related to 
this one):

http://code.google.com/p/macfuse/issues/detail?id=111&can=2&q=

I don't think Apple fixed this issue in Tiger--Leopard should have fixed this.

Original comment by si...@gmail.com on 7 Jul 2008 at 6:31

[GoogleCodeExporter]

Can't reproduce.

Original comment by si...@gmail.com on 10 Nov 2008 at 5:30

• Changed state: WontFix

[GoogleCodeExporter]

I reformatted the regarding Volumes with Apple's Disk Utility to "Mac OS 
Extended"
(HFS Plus), so Spotlight use on NTFS-3G Volumes is not an issue for me anymore. 
Thank
you for your efforts.

Original comment by toma...@gmail.com on 15 Nov 2008 at 7:04