| To: | bren@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: Free space question |
| From: | Steve Lord <lord@xxxxxxx> |
| Date: | 01 May 2002 14:04:45 -0500 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <1020279724.3cd03bac1cece@xxxxxxxxxxxxxxxxx> |
| References: | <Pine.BSI.4.33L2.0205011859110.24740-100000@xxxxxxxxxxxxx> <1020273839.3cd024af9c1aa@xxxxxxxxxxxxxxxxx> <1020275216.1266.17.camel@xxxxxxxxxxxxxxxxxxxxxx> <1020277416.3cd032a880faf@xxxxxxxxxxxxxxxxx> <1020277619.1202.21.camel@xxxxxxxxxxxxxxxxxxxxxx> <1020278255.28928.63.camel@xxxxxxxxxxxxxxxxxxxx> <1020279058.3cd0391210692@xxxxxxxxxxxxxxxxx> <1020279323.28928.67.camel@xxxxxxxxxxxxxxxxxxxx> <1020279724.3cd03bac1cece@xxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Wed, 2002-05-01 at 14:02, bren@xxxxxxxxxxxxx wrote: > xfs_repair reports nothing. What if I were to dump the fs, rebuild the > partition, and restore the dump? I've tried about everything else.. Please try xfs_check on it - it is a different program, it does not fix things, but it does a good consistency check using a different algorithm. The freesp output suggests there is corruption, we at least need to capture that before doing anything else. Steve . > > Quoting Steve Lord <lord@xxxxxxx>: > > > > Ugh, try xfs_check on the unmounted device, it will look at different > > things. Those numbers look way out of bounds. > > > > Steve > > > > -- > > > > Steve Lord voice: +1-651-683-3511 > > Principal Engineer, Filesystem Software email: lord@xxxxxxx > > > > -- 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: | papers & design docs available again on oss, Eric Sandeen |
|---|---|
| Next by Date: | Re: Free space question, bren |
| Previous by Thread: | Re: Free space question, bren |
| Next by Thread: | Re: Free space question, bren |
| Indexes: | [Date] [Thread] [Top] [All Lists] |