From: Luca <kronos@kronoz.cjb.net>
To: linux-kernel@vger.kernel.org
Cc: Jean Delvare <khali@linux-fr.org>,
Anton Altaparmakov <aia21@cam.ac.uk>,
Bas Vermeulen <bvermeul@blackstar.nl>
Subject: Re: 2.6.14-rc1 - kernel BUG at fs/ntfs/aops.c:403
Date: Sat, 17 Sep 2005 16:51:50 +0200 [thread overview]
Message-ID: <20050917145150.GA5481@dreamland.darkstar.lan> (raw)
In-Reply-To: <20050917114459.647654d4.khali@linux-fr.org>
Jean Delvare <khali@linux-fr.org> ha scritto:
> Hi Anton, Bas, all,
>
> [Bas Vermeulen]
>> > I get a kernel BUG when mounting my (dirty) NTFS volume.
>> >
>> > Sep 12 18:54:47 laptop kernel: [4294708.961000] NTFS volume version
>> > 3.1. Sep 12 18:54:47 laptop kernel: [4294708.961000] NTFS-fs error
>> > (device sda2): load_system_files(): Volume is dirty. Mounting
>> > read-only. Run chkdsk and mount in Windows.
>> > Sep 12 18:54:47 laptop kernel: [4294709.063000] ------------[ cut
>> > here ]------------
>> > Sep 12 18:54:47 laptop kernel: [4294709.063000] kernel BUG at
>> > fs/ntfs/aops.c:403!
>
> I just hit the same BUG in different conditions. My NTFS volume is not
> dirty, not compressed and the BUG triggered on use (updatedb), not
> mount.
Same here, but it only triggers accessing a compressed directory. I can
reproduce at will just by using 'ls' inside a compressed dir.
> (BTW, is there a way to tell from Linux directly?)
ntfsinfo(8)
Luca
--
Home: http://kronoz.cjb.net
Se non puoi convincerli, confondili.
next prev parent reply other threads:[~2005-09-17 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 7:29 Bas Vermeulen
2005-09-15 8:58 ` Anton Altaparmakov
2005-09-15 19:24 ` Bas Vermeulen
2005-09-15 21:21 ` Anton Altaparmakov
2005-09-15 22:14 ` Bas Vermeulen
2005-09-16 0:11 ` Anton Altaparmakov
2005-09-17 9:44 ` Jean Delvare
2005-09-17 14:51 ` Luca [this message]
2005-09-19 9:39 ` Anton Altaparmakov
2005-09-20 17:44 ` Luca
2005-09-20 17:47 ` Anton Altaparmakov
2005-09-21 18:37 ` Jean Delvare
2005-09-21 19:34 ` Anton Altaparmakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050917145150.GA5481@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=aia21@cam.ac.uk \
--cc=bvermeul@blackstar.nl \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®