From: Jan Hudec <bulb@ucw.cz>
To: Ewerton Romulo <ewertonromulo@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Run linux in ramdisk(tmpfs) and use a mounted HD for files cause memory and CPU overflow!
Date: Mon, 27 Jun 2005 16:20:13 +0200 [thread overview]
Message-ID: <20050627142013.GA11425@vagabond> (raw)
In-Reply-To: <1f52e8ed050627021872365696@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]
On Mon, Jun 27, 2005 at 06:18:11 -0300, Ewerton Romulo wrote:
> I am building a very small linux system to boot off an IDE-HD module
> and run from a ramdisk.
Ramdisk *OR* tmpfs? They are completely different things.
> He´s working well and have no problem funtion like that. I´m using
> linux kernel 2.4.30!
> But some times I need to mount a partion on HD and use a directory to
> save many files in it!
How large are those "many files"? Where do the data come from?
> I mount it, create a directory there but ... when I try to use the HD
> mount with the directory, save many files in it, the memory go up .. up
> ... and the linux stop working!!!o
> If I umount the partion everything return to function well.
How do you umount it, when it stopped working?!
Anyway, could you provide contents of /proc/meminfo, /proc/slabinfo,
/proc/mounts and /proc/swaps when the bad things are happening?
> When I mount the partion again and begin to put files in it ... the
> problem return!
> I try to mount partion using ext2 and ext3 ... the problem is the
> same!!!
I'd be surprised if there was a difference. The filesystems are quite
similar.
-------------------------------------------------------------------------------
Jan 'Bulb' Hudec <bulb@ucw.cz>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-27 14:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 9:18 Run linux in ramdisk(tmpfs) and use a mounted HD for files cause memory and CPU overflow! Ewerton Romulo
2005-06-27 14:20 ` Jan Hudec [this message]
2005-06-28 18:06 ` Ewerton Romulo
2005-06-28 20:24 ` Jan Hudec
2005-06-29 4:41 ` Ewerton Romulo
2005-06-29 8:41 ` Jan Hudec
2005-06-29 16:28 ` Bryan Henderson
2005-06-29 18:36 ` Ewerton Romulo
2005-06-29 21:00 ` Bryan Henderson
2005-06-30 16:02 ` Jan Hudec
2005-06-29 18:46 ` Ewerton Romulo
2005-06-28 21:42 ` Bryan Henderson
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=20050627142013.GA11425@vagabond \
--to=bulb@ucw.cz \
--cc=ewertonromulo@gmail.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).