| To: | bren@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: Free space question |
| From: | Steve Lord <lord@xxxxxxx> |
| Date: | 01 May 2002 13:37:35 -0500 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <1020277619.1202.21.camel@stout.americas.sgi.com> |
| References: | <Pine.BSI.4.33L2.0205011859110.24740-100000@xs3.xs4all.nl> <1020273839.3cd024af9c1aa@webmail.midco.net> <1020275216.1266.17.camel@stout.americas.sgi.com> <1020277416.3cd032a880faf@webmail.midco.net> <1020277619.1202.21.camel@stout.americas.sgi.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Wed, 2002-05-01 at 13:26, Eric Sandeen wrote: > imaxpct sets how much filesystem space can be consumed by the inodes > themselves. It is not reserved, just an upper bound. > > You would want to raise the imaxpct, if anything, to test this. > However, if you were able to lower it, that means that you had not yet > hit the old max, so that's not the problem. > > Still thinking... > > -Eric > Try running xfs_db -r /dev/xxx then run the freesp command, this will report how freespace is distributed on the filesystem. quit gets you out of xfs_db. 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: | Re: Free space question, Eric Sandeen |
|---|---|
| Next by Date: | Re: Free space question, bren |
| Previous by Thread: | Re: Free space question, Eric Sandeen |
| Next by Thread: | Re: Free space question, bren |
| Indexes: | [Date] [Thread] [Top] [All Lists] |