From: "Roy S.C. Ho" <scho1208@yahoo.com>
To: Padraig Brady <padraig@antefacto.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: question about kernel 2.4 ramdisk
Date: Wed, 5 Dec 2001 01:37:44 -0800 (PST) [thread overview]
Message-ID: <20011205093744.79645.qmail@web21108.mail.yahoo.com> (raw)
In-Reply-To: <3C0D2843.5060708@antefacto.com>
Hi Padraig,
Thanks for the patch. I applied it to fs/ramfs/inode.c
in 2.4.13-ac7 and compile it as a module in 2.4.2
(removepage was changed back to truncatepage, of
course), but it seems that memory leak still occured
(I have to stick to 2.4.2 as one of my production
systems uses it...) Any idea?
By the way, is it possible to use ramdisk with the
size larger than 600MB? /var/log/messages repeatedly
reported the following when I tried to mount a
ext2-formatted ramdisk of 600MB:
Dec 5 17:22:27 roy-home kernel: set_blocksize: dev
01:00 buffer_dirty 655360 size 1024
....
....
Dec 5 17:22:27 roy-home kernel: EXT2-fs: Magic
mismatch, very weird !
Many thanks,
Roy
--- Padraig Brady <padraig@antefacto.com> wrote:
> Roy S.C. Ho wrote:
>
> > Hi, I am using linux kernel 2.4.2 and I have 1 GB
> ram.
> > I tried to boot the system with a ramdisk size of
> > 600MB. It was ok when I did "mke2fs" on it, but
> when I
> > mounted it, it failed (Magic number mismatch). I
> tried
> > this several times and found that all ramdisk
> sizes
> > larger than 513MB could cause trouble. Could
> anyone
> > please kindly give me some hints? I would like to
> have
> > a larger ramdisk (around 800MB).
> >
> > (note: I tried ramfs but it seems to have memory
> > leakage when files are deleted and created
> frequently;
> > tmpfs is ok, but the pages may be swapped, which
> is
> > not desirable in my case...)
>
>
> does the patch attached fix your problem with ramfs?
>
>
__________________________________________________
Do You Yahoo!?
Buy the perfect holiday gifts at Yahoo! Shopping.
http://shopping.yahoo.com
prev parent reply other threads:[~2001-12-05 9:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 19:01 question about kernel 2.4 ramdisk Roy S.C. Ho
2001-12-04 19:47 ` Padraig Brady
2001-12-04 20:14 ` Alan Cox
2001-12-05 7:49 ` Christoph Rohland
2001-12-05 7:56 ` Tachino Nobuhiro
2001-12-05 8:23 ` Christoph Rohland
2001-12-05 8:42 ` Tachino Nobuhiro
2001-12-05 13:51 ` Christoph Rohland
2001-12-06 16:37 ` David Gibson
2001-12-06 16:55 ` Alan Cox
2001-12-08 9:53 ` Christoph Rohland
2001-12-14 5:35 ` David Gibson
2001-12-16 15:34 ` Christoph Rohland
2001-12-17 3:49 ` David Gibson
2001-12-17 7:55 ` Christoph Rohland
2001-12-05 9:37 ` Roy S.C. Ho [this message]
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=20011205093744.79645.qmail@web21108.mail.yahoo.com \
--to=scho1208@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=padraig@antefacto.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.