LKML Archive on
help / color / mirror / Atom feed
From: "Robert M. Stockmann" <>
To: Andrew Morton <>
Subject: Re: ramdisk driver in 2.6.6 has a severe bug
Date: Tue, 18 May 2004 02:13:19 +0200 (CEST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, 17 May 2004, Andrew Morton wrote:

> "Robert M. Stockmann" <> 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.

Well i think a problem has risen due to people allocating huge ramdisks with
sizes over 128Mb RAM. This is biting into the virtual memory management
system. For people using the ramdisk driver as a permanent runtime
root filesystem, maybe create a boot option : 

ramdisk=persistent	(or =solid or =sticky )

Robert M. Stockmann - RHCE
Network Engineer - UNIX/Linux Specialist

  reply	other threads:[~2004-05-18  0:13 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
2004-05-18  0:13       ` Robert M. Stockmann [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: ramdisk driver in 2.6.6 has a severe bug' \

* 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).