Bug 117314 - [ntfs] Long-filename only NTFS fs'es cause kernel panics on read
Summary: [ntfs] Long-filename only NTFS fs'es cause kernel panics on read
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-fs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-18 23:00 UTC by Enji Cooper
Modified: 2013-02-03 22:27 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Enji Cooper freebsd_committer freebsd_triage 2007-10-18 23:00:07 UTC
Creating a filesystem after disabling short (MSDOS 8.3 filenames), as per the following webpage / tip: http://www.activewin.com/tips/reg/file_3.shtml, and then adding files / directories on the filesystem and trying to display (ls) or copy (cp) results in a panic (don't have the output, but I can obtain it again if requested).

How-To-Repeat: From Windows:
1. Follow directions here: <http://www.activewin.com/tips/reg/file_3.shtml>.
2. Reboot machine.
3. Create file / folder on NTFS volume.

From FreeBSD:
1. mount /path/to/ntfs/node /mnt/ntfs
2. ls /path/to/ntfs/file

(panic)
Comment 1 Remko Lodder 2007-10-24 07:31:13 UTC
On Thu, October 18, 2007 11:52 pm, Garrett Cooper wrote:
>

>>Description:
> Creating a filesystem after disabling short (MSDOS 8.3 filenames), as per
> the following webpage / tip:
> http://www.activewin.com/tips/reg/file_3.shtml, and then adding files /
> directories on the filesystem and trying to display (ls) or copy (cp)
> results in a panic (don't have the output, but I can obtain it again if
> requested).
>>How-To-Repeat:
>>From Windows:
> 1. Follow directions here:
> <http://www.activewin.com/tips/reg/file_3.shtml>.
> 2. Reboot machine.
> 3. Create file / folder on NTFS volume.
>
>>From FreeBSD:
> 1. mount /path/to/ntfs/node /mnt/ntfs
> 2. ls /path/to/ntfs/file
>
> (panic)

Hi Garrett,

I think that the proper backtraces etc are required to get this fixed (as
per the developers handbook) can you possibly obtain them and hook them to
this ticket so that people interested in fixing this problem can see where
things go wrong?

Thanks & Cheers
remko


-- 
Kind regards,

     Remko Lodder               ** remko@elvandar.org
     FreeBSD                    ** remko@FreeBSD.org

     /* Quis custodiet ipsos custodes */
Comment 2 Garrett Cooper 2008-06-17 04:22:57 UTC
Will submit followup after my Macbook "returns from the shop".
-Garrett
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2009-05-18 05:26:47 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-fs

Over to maintainer(s).
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2012-01-02 15:17:09 UTC
State Changed
From-To: open->feedback

Is this still an issue?
Comment 5 Eitan Adler freebsd_committer freebsd_triage 2012-02-08 01:52:29 UTC
State Changed
From-To: feedback->closed

this appears to be fixed. If this is still a problem mail me and I'll 
reopen it.