From: "James McMechan" <james_mcmechan@hotmail.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] many cow files with ubd_kern.c
Date: Sat, 28 Jan 2006 23:11:31 +0000 [thread overview]
Message-ID: <BAY101-F14AF59E645AF66A2146EF5E2170@phx.gbl> (raw)
Once again I have been tweaking ubd_kern to support lots of disks since I
need it for recovery
but I hit (even on a plain 2.6.15-bs1 kernel)
allocation failed: out of vmalloc space - use "vmalloc=<size>" to increse
size
Failed to vmalloc COW bitmap
ubd0: Can't open "COW0": errno -12
but I already had vmalloc=128M (which should be the default) and
vmalloc=256M and mem=384M on the command line.
I can't seem to locate where the equivlaent of arch/i386/kernel/setup.c has
the vmalloc= option on arch/um though
has anyone hit something like this before each of the bitmaps should only
take about 60M of memory and at this point I have only tried to allocate 1
for a single 250G ubd device
This will present a larger problem when I get everything working and try to
allocate all 10 drives worth of bitmap ~600M
I suppose I may have to go back to the paged bitmap logic but it is still a
mess...
The multiple major numbers and C:H:S from mconsole do seem to work correctly
though
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2006-01-28 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 23:11 James McMechan [this message]
2006-01-29 2:46 ` [uml-devel] many cow files with ubd_kern.c Jeff Dike
2006-01-29 3:42 ` James McMechan
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=BAY101-F14AF59E645AF66A2146EF5E2170@phx.gbl \
--to=james_mcmechan@hotmail.com \
--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