Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S267033AbTCFGce>; Thu, 6 Mar 2003 01:32:34 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S267843AbTCFGcd>; Thu, 6 Mar 2003 01:32:33 -0500
Received: from air-2.osdl.org ([65.172.181.6]:24242 "EHLO mail.osdl.org")
	by vger.kernel.org with ESMTP id <S267033AbTCFGcc>;
	Thu, 6 Mar 2003 01:32:32 -0500
Message-ID: <33113.4.64.238.61.1046932970.squirrel@www.osdl.org>
Date: Wed, 5 Mar 2003 22:42:50 -0800 (PST)
Subject: Re: [Linux-NTFS-Dev] ntfs OOPS (2.5.63)
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <szaka@sienet.hu>
In-Reply-To: <Pine.LNX.4.30.0303060716390.28143-100000@divine.city.tvnet.hu>
References: <33061.4.64.238.61.1046931564.squirrel@www.osdl.org>
        <Pine.LNX.4.30.0303060716390.28143-100000@divine.city.tvnet.hu>
X-Priority: 3
Importance: Normal
Cc: <rddunlap@osdl.org>, <aia21@cantab.net>, <linux-kernel@vger.kernel.org>,
       <linux-ntfs-dev@lists.sourceforge.net>
X-Mailer: SquirrelMail (version 1.2.8)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1588
Lines: 46

>
> 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



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/