| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: unable to use xfs_repair |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Fri, 4 Oct 2002 18:21:51 +0200 |
| Cc: | Sidik Isani <lksi@xxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <1033747014.2457.11.camel@xxxxxxxxxxxxxxxxxxxx> |
| References: | <20021003170436.A11748@xxxxxxxxxxxxxxx> <4.3.2.7.2.20021004090036.036b5728@xxxxxxxxxxxxx> <20021003224118.A12588@xxxxxxxxxxxxxxx> <1033747014.2457.11.camel@xxxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.22.1i |
> OK, I went and had a look, and we are actually as efficient as we can > be in use of the memory itself. Only problem is that we allocate 4 times > what we use. I fixed this in cvs. Unless you memset it (=actually using, not allocating) and it still fits into the 32big address space that could be worked around by echo 1 > /proc/sys/vm/overcommit_memory -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | TAKE - Bump version, document xfs_repair memory allocation fix., Eric Sandeen |
|---|---|
| Next by Date: | Re: Journal Free Space, Michael Wahlbrink |
| Previous by Thread: | Re: unable to use xfs_repair, Steve Lord |
| Next by Thread: | Re: unable to use xfs_repair, Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |