public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Tobias Ringstrom <tori@tellus.mine.nu>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4 ate my filesystem on rw-mount
Date: Fri, 12 Jan 2001 20:49:32 +0100	[thread overview]
Message-ID: <20010112204932.B2740@suse.cz> (raw)
In-Reply-To: <Pine.LNX.4.30.0101120951270.7175-100000@svea.tellus>
In-Reply-To: <Pine.LNX.4.30.0101120951270.7175-100000@svea.tellus>; from tori@tellus.mine.nu on Fri, Jan 12, 2001 at 10:15:45AM +0100

On Fri, Jan 12, 2001 at 10:15:45AM +0100, Tobias Ringstrom wrote:
> I've never seen anything like it before, which I'm happy for.  The system
> had been running a standard RedHat 7 kernel for days without any problems,
> but who wants to run a 2.2 kernel?  I compiled 2.4.0 for it, rebooted, and
> blam!  The RedHat init stripts got to the "remounting root read-write"
> point, and just froze solid.
> 
> Rebooting into RH7 failed, becauce inittab could not be found.  In fact
> the filesystem was completely messed up, with /dev empty, lots of device
> nodes in /etc, and files missing all over the place.  I had to reinstall
> RH7 from scratch.
> 
> I do not understand how this could happen during a remounting root rw.
> Is the filesystem really that unstable?
> 
> Am I right in suspecting DMA, which was enabled at the time?  Any other
> ideas?  Is it a known problem?
> 
> This is on a 450 MHz AMD-K6 with the following IDE controller:
> 
> 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 06)
> 
> [I know this is not a very good trouble report, but it will have to do for
> the time beeing.  I hope to do more testing at a later time.]
> 
> /Tobias
> 
> PS. This is _not_ the same system that I reported IDE busy errors for.

Wow. Ok, I'm maintaining the 2.4.0 VIA driver, so I'd like to know more
about this:

1) What's the ISA bridge revision?
2) What's in /proc/ide/via?
3) What says hdparm -i on your devices?
4) If you mount your filesystem read-only, does it read garbage?

Thanks.

-- 
Vojtech Pavlik
SuSE Labs
-
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/

  parent reply	other threads:[~2001-01-12 19:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-12  9:15 2.4 ate my filesystem on rw-mount Tobias Ringstrom
2001-01-12 10:22 ` Alan Cox
2001-01-12 17:23   ` Martin Laberge
2001-01-12 19:51     ` Vojtech Pavlik
2001-01-12 19:49 ` Vojtech Pavlik [this message]
2001-01-13  8:12   ` Tobias Ringstrom
2001-01-13 14:35     ` Vojtech Pavlik
2001-01-13 16:20       ` Tobias Ringstrom
2001-01-13 22:36         ` 2.4 ate my filesystem on rw-mount, getting closer Tobias Ringstrom
2001-01-14  8:44           ` Vojtech Pavlik
2001-01-14  8:45             ` Tobias Ringstrom
2001-01-14  9:48               ` Vojtech Pavlik
2001-01-14 16:37                 ` Tobias Ringstrom
2001-01-14 17:59                   ` Tobias Ringstrom
2001-01-14 22:32                     ` Vojtech Pavlik
2001-01-23 21:39                       ` 2.4 ate my filesystem on rw-mount, summary Tobias Ringstrom

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=20010112204932.B2740@suse.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tori@tellus.mine.nu \
    /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