| To: | Andi Kleen <ak@xxxxxxx> |
|---|---|
| Subject: | Re: unable to use xfs_repair |
| From: | Steve Lord <lord@xxxxxxx> |
| Date: | 04 Oct 2002 11:44:57 -0500 |
| Cc: | Sidik Isani <lksi@xxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20021004182151.A8443@xxxxxxxxxxxxx> |
| References: | <20021003170436.A11748@xxxxxxxxxxxxxxx> <4.3.2.7.2.20021004090036.036b5728@xxxxxxxxxxxxx> <20021003224118.A12588@xxxxxxxxxxxxxxx> <1033747014.2457.11.camel@xxxxxxxxxxxxxxxxxxxx> <20021004182151.A8443@xxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Fri, 2002-10-04 at 11:21, Andi Kleen wrote: > > 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 It uses all the memory, 4 bits per filesystem block, we record what type of information is in that part of the fs - including free blocks. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@xxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | 1.2 PreRelease avaliable, Russell Cattelan |
|---|---|
| Next by Date: | TAKE - fix kdb extent printing, Steve Lord |
| Previous by Thread: | Re: unable to use xfs_repair, Andi Kleen |
| Next by Thread: | Re: unable to use xfs_repair, Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |