On Wed, Apr 04, 2007 at 10:36:01PM +0200, Lars Ellenberg wrote:
> NOTE that I used the default sarge xfsprogs version 2.6.20, not
> the upstream 2.8.20. yet. I'll start an xfs_repair run with
> 2.8.20 right after this post, though...
now, this used seriously more memory, and cpu,
and the box went thrashing.
after some experimenting,
xfs_repair -o bhash=512
got it going without using excessive amounts of swap,
so it finally finished after about 12 hours
(2.6.20 needed 8:30, repeatable).
it did not change the situation, however.
I know I could clean these using xfs_db and an additional run of
xfs_repair, but I'm going to keep these around for some more time, in
case you want me to have a look at some internals still.
file system itself has gone life again, I hope it does not hurt having
those strange directories around.
maybe it is even "just" a problem on the kernel side,
not being able to convert so the expected "form" of directory?
sorry, I'm not too deep in the xfs internals, so I need some input from
the developers here...
: Lars Ellenberg Tel +43-1-8178292-0 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe http://www.linbit.com :
please use the "List-Reply" function of your email client.