public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Niehusmann <jan@gondor.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: uncorrectable ext2 errors
Date: Sun, 10 Aug 2003 23:34:50 +0200	[thread overview]
Message-ID: <20030810213450.GA7050@gondor.com> (raw)
In-Reply-To: <20030810231955.A16852@pclin040.win.tue.nl>

On Sun, Aug 10, 2003 at 11:19:55PM +0200, Andries Brouwer wrote:
> I see no kernel version in your post, that would be the first thing
> of interest. Next, look at this addressing variable via /proc.

Sorry - I mentioned it in an earlier post with a different subject. It's
plain 2.4.21. 

> It it is zero, then you are hit by something avoided by the patch
> I sketched yesterday evening or so. Otherwise we must look further.

It is 0, yes. May it be caused by the following lines in pdc202xx_old.c?

        if (hwif->pci_dev->device == PCI_DEVICE_ID_PROMISE_20265)
                hwif->addressing = (hwif->channel) ? 0 : 1;

> Also, I see that you do e2fsck on a mounted filesystem. Terrible.

:-)
I know. But it's mounted read only, and to be sure I tried it without
mounting the file system, as well. 
But the most important prove that it's not a fs problem is that writing
to one partition changed contents of a different partition.

Jan


  reply	other threads:[~2003-08-10 21:34 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06 15:03 uncorrectable ext2 errors Jan Niehusmann
2003-08-06 17:06 ` Andreas Dilger
2003-08-06 18:38   ` Jan Niehusmann
2003-08-06 18:52     ` Mike Fedyk
2003-08-06 19:50 ` Jan Niehusmann
2003-08-07 11:06 ` Jan Niehusmann
2003-08-07 12:27   ` LBA48 on Promise 20265 Jan Niehusmann
2003-08-07 21:12   ` uncorrectable ext2 errors Andries Brouwer
2003-08-10 20:55     ` Jan Niehusmann
2003-08-10 21:19       ` Andries Brouwer
2003-08-10 21:34         ` Jan Niehusmann [this message]
2003-08-10 21:58           ` Andries Brouwer
2003-08-10 22:10             ` Jan Niehusmann
2003-08-10 22:33               ` IDE bug - was: " Andries Brouwer
2003-08-12 15:36                 ` Alan Cox
2003-08-12 16:32                   ` Bartlomiej Zolnierkiewicz
2003-08-12 22:50                   ` Andries Brouwer
2003-08-13  0:21                     ` Bartlomiej Zolnierkiewicz
2003-08-13  8:03                       ` Jan Niehusmann
2003-08-13  9:25                         ` Jan Niehusmann
2003-08-13 11:16                         ` Alan Cox
2003-08-13 11:20                           ` Jan Niehusmann
2003-08-13 12:12                             ` Jan Niehusmann
2003-08-13 16:31                           ` Jan Niehusmann
2003-08-13 18:38                             ` Alan Cox
2003-08-13 12:21                         ` Bartlomiej Zolnierkiewicz
2003-08-13 13:27                       ` Andries Brouwer
2003-08-13 22:05                         ` Jan Niehusmann
2003-08-13 22:32                           ` Bartlomiej Zolnierkiewicz
2003-08-13 22:36                       ` Jan Niehusmann
2003-08-13 23:14                         ` Bartlomiej Zolnierkiewicz
2003-08-14  6:37                           ` Jan Niehusmann
2003-08-10 23:01           ` Bartlomiej Zolnierkiewicz

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=20030810213450.GA7050@gondor.com \
    --to=jan@gondor.com \
    --cc=aebr@win.tue.nl \
    --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