public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: safemode <safemode@voicenet.com>
To: linux-kernel@vger.kernel.org
Subject: Via apollo KX133 ide bug in 2.4.x
Date: Fri, 19 Jan 2001 19:33:21 -0500	[thread overview]
Message-ID: <3A68DCD1.FACB4135@voicenet.com> (raw)

I'm sorry I can't be more descriptive than that, but there aren't any
errors ever displayed.  What happened was after about a day of uptime, I
began seeing IO errors when trying to access files.  I realized that the
IO errors occurred on any file I had created.  I rebooted since the
computer became impossible to use and fsck removed everything that I had
created since upgrading to the release kernel.  This is all on ext2fs.
I tried making bootdisks but they all showed up as being bad.  I tried
copying files to another ext2fs but upon fsck, they too were all removed
due to corruption.  These ext2fs' were not created by the release
kernel.  I had to go back to 2.4.0-test11 before the kernel would write
to the fs correctly.  For the record, I disabled DMA in the kernel and
i'm compiling for athlon using gcc 2.95.3.  I saw the same thing happen
though when I booted for a kernel compiled for Pentium 2.    Since
reverting back to 2.4.0-test11, however, no FS corruption has been
observed.  Anyone have any idea what this is about?  i'm compiling with
the same options between kernels but 2.4.x (release and newer) do not
seem to be able to write to the ext2fs correctly.  Could this be because
it was formatted by a 2.2.x kernel?   Anyone using this chipset I would
caution to have backups ready when using it with 2.4.x, as I lost
hundreds of files to it.  Also, no errors were reported anywhere,  IO
errors when trying to stat dirs just started appearing after a couple
days uptime ...then they would occur whenever you wrote to the FS.  Even
after a reboot.    If you need any extra iinfo about kernel options and
computer config, just ask.

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

             reply	other threads:[~2001-01-20  0:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-20  0:33 safemode [this message]
2000-01-20  8:38 ` Via apollo KX133 ide bug in 2.4.x Peter Horton
2001-01-20 20:56   ` Peter Horton
2001-01-20 21:32     ` safemode
2001-01-21 11:40       ` Vojtech Pavlik
2001-01-22 22:49         ` Peter Horton

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=3A68DCD1.FACB4135@voicenet.com \
    --to=safemode@voicenet.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