linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] uml crashes when producing large files
Date: Thu, 26 Apr 2007 16:17:30 +0200	[thread overview]
Message-ID: <200704261617.31010.blaisorblade@yahoo.it> (raw)
In-Reply-To: <1177579328.5349.10.camel@xaustrobit>

On giovedì 26 aprile 2007, Herbert Volkmann wrote:
> Hi List,
>
> i ran in the following problem:
Very strange...
> when i produce files (with dd) or copy files to or from the uml machine,
Which filesystems are involved? Can you give a sample command?

> i can see (with top),
Run on the guest (i.e. UML) I guess, right?
> that the used memory and the cached things 
> increases, while the unused memory will go down.
That is reasonable, but the cache should not make the system stop.
> shortly before memory 
> will come to zero, the uml stops working completely without any messages
> in the /var/log/* files on uml or host system.
>
> if i do in between a "echo 3 > /proc/sys/vm/drop_caches"
On the guest (i.e. UML) I assume, right?
>
> it cleans caches, frees memory and works fine! but i have to do this all
> 10 seconds when i use dd for producing large files ;-(
>
> these are the components i use:
> - debian etch on host with debian kernel patched with skas3 from debian
32bit system, right?
> - 1024 MB RAM on host
> - RAID5 System with 3ware Controller (5x2G) almost 1 TB
> - on uml i use debian etch, with bridged networking, 512MB RAM for uml
Which UML kernel release? That's the most important thing.
> - 6G root_fs for uml and 256M swap
>
> here is the command with which i start the uml:
> sudo -u uml /usr/bin/linux.uml umid=uml mem=512M eth0=tuntap,tap1
> ubd0=/usr/media/uml-linux/root_fs_2007_04_23
> ubd1=/usr/media/uml-linux/swap_fs con=null root=/dev/ubda uml_dir=/tmp/
>
> I would be really happy if someone could tell me what i can test more to
> find out why this system is instable with i/o operations and caches.

I have only a doubt: if you are filling a shmfs/tmpfs filesystem (which is 
backed by ram), that's an almost normal behaviour, and can happen even on 
host systems.

> thanx for any reply,
> Herbert

-- 
Inform me of my mistakes, so I can add them to my list!
Paolo Giarrusso, aka Blaisorblade
http://www.user-mode-linux.org/~blaisorblade

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel


      reply	other threads:[~2007-04-26 14:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26  9:22 [uml-devel] uml crashes when producing large files Herbert Volkmann
2007-04-26 14:17 ` Blaisorblade [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=200704261617.31010.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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