Re: [Linux-NTFS-Dev] ntfs OOPS (2.5.63)

[Randy.Dunlap]

>
> On Wed, 5 Mar 2003, Randy.Dunlap wrote:
>
>> > Could you try to turn on debugging in the NTFS driver (compile option in
>> the menus), then once ntfs module is loaded (or otherwise anytime) as
>> root do:
>> >
>> > echo -1 > /proc/sys/fs/ntfs-debug
>> >
>> > Then mount and to the directory changes. Assuming that you get the bug
>> again could you send me the captured kernel log output? (Note there will
>> be massive amounts of output.)
>> >
>> > The code looks ok and I can't reproduce here so it would be helpful to
>> see if there are any oddities on your partition. Just to make sure it is
>> not the compiler, could you do a "make fs/ntfs/inode.S" and send me that
>> as well?
>> >
>> > Thanks,
>>
>> Anton,
>>
>> I'll get to this in another day or so.
>>
>> The help text for NTFS_DEBUG says to use 1 to enable it
>> or 0 to disable it.  What does -1 do?
>
> Same as 1. However I doubt NTFS_DEBUG gives any useful in your case and if
> you had some NTFS "oddities" then it would be reproducible.
>
> What would be really useful is to disassemble __ntfs_init_inode what I asked
> 2 days ago (note, not the above 'make fs/ntfs/inode.S' because it will not
> tell what machine code you have on disk), your .config and exact CPU version
> (cat /proc/cpuinfo).

OK, I'll do that too.  Somehow I missed that request.  My bad.

~Randy