LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Robert M. Stockmann" <stock@stokkie.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ramdisk driver in 2.6.6 has a severe bug
Date: Mon, 17 May 2004 17:04:33 -0700	[thread overview]
Message-ID: <20040517170433.0311c2e9.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0405180132240.21480-100000@hubble.stokkie.net>

"Robert M. Stockmann" <stock@stokkie.net> wrote:
>
> Be aware of other problems when using the linux ramdisk driver,
> loosing its contents. Especially the use of mkinitrd might result in 
> unexpected problems. googling for "kernel 2.6.6 ramdisk problem" shows lots
> of people with problems mounting their root filesystems and loading modules
> from ramdisk. Klaus Knopper (knoppix) is not amused, neither am i :)

Well in that case perhaps something else broke.  I've seen no such reports
of recent regressions in the ramdisk driver.

The two problems of which I am aware are:

a) It loses its brains across umount.  Seems that it's very rare that
   anyone actually cares about this, which is why it has not been fixed in
   well over a year.

b) It loses data under heavy I/O loads.  I _think_ this has been
   observed only on ppc64 and might be a cache writeback/invalidate thing.

If there are new post-2.6.5 problems then I'm all ears.

  reply	other threads:[~2004-05-18  0:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 23:02 Robert M. Stockmann
2004-05-17 23:18 ` Valdis.Kletnieks
2004-05-17 23:19 ` Andrew Morton
2004-05-17 23:50   ` Robert M. Stockmann
2004-05-18  0:04     ` Andrew Morton [this message]
2004-05-18  0:13       ` Robert M. Stockmann
2004-05-18  0:50       ` viro
2004-05-18  1:03         ` Andrew Morton
2004-05-17 23:29 Valdis.Kletnieks

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=20040517170433.0311c2e9.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stock@stokkie.net \
    --subject='Re: ramdisk driver in 2.6.6 has a severe bug' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).