| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Logdev size? |
| From: | Andrew Tridgell <tridge@xxxxxxxxxxx> |
| Date: | Thu, 26 Jul 2001 18:16:01 -0700 (PDT) |
| In-reply-to: | <20010726121229.A2656@xxxxxxx> (message from Andrew Klaassen on Thu, 26 Jul 2001 12:12:29 -0400) |
| References: | <200107241352.f6ODqZJ23995@xxxxxxxxxxxxxxxxxxxx> <20010725205259.C2291@xxxxxxx> <3B603846.5B6A6980@xxxxxxx> <20010726121229.A2656@xxxxxxx> |
| Reply-to: | tridge@xxxxxxxxx |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
A related question about logdev sizes ... I've noticed that mkfs.xfs refuses to make a logdev bigger than 128M. Have anyone done any work on upping this limit? I'd like to put the logdev on a 1G ram card so that I can do really large netbench runs without hitting the real disks. I'm testing at the moment with the logdev on a ramdisk (see http://samba.org/ftp/unpacked/junkcode/trd/) but the 130M limit means those pesky disk lights come on with even quite small runs. also, is there any work being done to use the same logdev for multiple filesystems? Having to know in advance how to split up a valuable nv ram area over lots of filsystems can be tricky. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: umask fix (patch), Andrew Tridgell |
|---|---|
| Next by Date: | Re: umask fix (patch), Timothy Shimmin |
| Previous by Thread: | Re: Logdev size?, Seth Mos |
| Next by Thread: | Re: Logdev size?, Seth Mos |
| Indexes: | [Date] [Thread] [Top] [All Lists] |