public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Conrad <conrad@bungled.net>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Oleg Drokin <green@namesys.com>,
	Dave Jones <davej@codemonkey.org.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext3 / reiserfs data corruption, 2.5-bk
Date: Tue, 10 Jun 2003 18:18:54 -0400	[thread overview]
Message-ID: <20030610221854.GA6893@bungled.net> (raw)
In-Reply-To: <Pine.SOL.4.30.0306102001430.24343-100000@mion.elka.pw.edu.pl>

[-- Attachment #1: Type: text/plain, Size: 1899 bytes --]

Oh, ok. I am using DMA on my drives. The problem with this bug is that
it is fairly hard to observe, I've only seen it about once every other
day. I should have also pointed out that I am using ext3.

I thought that it might be taskfile stuff because that was the major
change in the kernel the time right before I started to notice these
problems. There likely is some other source of problems because you
say that there should be no change in behaviour.

-Nathan

On Tue, Jun 10, 2003 at 08:11:22PM +0200, Bartlomiej Zolnierkiewicz wrote:
> 
> On Tue, 10 Jun 2003, Nathan Conrad wrote:
> 
> > I've been noticing a similar problem on my laptop. This may, or may
> > not be related, but it did start somewhere within the past week (maybe
> > the IDE taskfile conversion???, to throw out a guess). I wonder if
> 
> wrt taskfile conversion, if you are using DMA on your IDE disks,
> there shouldn't be any change in behaviour.
> 
> I will prepare a patch adding old crap and making it selectable
> (default will be taskfile, if you go into problems you can check
> with old code) to easy spotting possible taskfile problems
> and allowing quick judging - taskfile guilty/not guilty.
> 
> --
> Bartlomiej
> 
> > Dave Jones is using IDE or SCSI. CONFIG_SMP and CONFIG_PREEMPT are
> > disabled on my machine (Sony Vaio PCG-FXA49 laptop, Athlon4). I'm
> > compiling the kernel with gcc 3.3 (Debian version).
> >
> > Anyway, certain directories get locked up on occasion and when I try
> > to execute 'ls' or read from the directory, the process gets into a
> > locked up state; ^C does not work to kill the process. The only way to
> > make a directory "readable" is to restart the machine. I have not
> > noticed any FS corruption, just the lack of being able to enter the
> > directory.
> >
> >  At the same time, a kernel bug will be displayed:
> 
> <...>


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-06-10 18:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-09 19:35 ext3 / reiserfs data corruption, 2.5-bk Dave Jones
2003-06-10  8:43 ` Oleg Drokin
2003-06-10  9:20   ` Dave Jones
2003-06-10 21:44   ` Nathan Conrad
2003-06-10 18:11     ` Bartlomiej Zolnierkiewicz
2003-06-10 22:18       ` Nathan Conrad [this message]
2003-06-10 20:59     ` Andrew Morton
2003-06-12  5:20       ` ext3 / reiserfs data corruption, 2.5-bk; NULL pointer dereference bug Nathan Conrad
2003-06-10 22:49     ` ext3 / reiserfs data corruption, 2.5-bk Dave Jones

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=20030610221854.GA6893@bungled.net \
    --to=conrad@bungled.net \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=davej@codemonkey.org.uk \
    --cc=green@namesys.com \
    --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