From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: xfs@oss.sgi.com
Subject: Re: xfs_repair leaves empty but undeletable dirs in lost+found
Date: Thu, 5 Apr 2007 18:22:35 +0200 [thread overview]
Message-ID: <20070405162235.GA816@barkeeper1.linbit> (raw)
In-Reply-To: <20070404203601.GA11771@barkeeper1.linbit>
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...
done.
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...
Thanks,
--
: 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.
next prev parent reply other threads:[~2007-04-05 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 20:36 xfs_repair leaves empty but undeletable dirs in lost+found Lars Ellenberg
2007-04-05 16:22 ` Lars Ellenberg [this message]
2007-04-10 1:55 ` Barry Naujok
2007-04-10 9:24 ` Lars Ellenberg
2007-04-10 20:45 ` Martin Steigerwald
2007-04-10 21:05 ` Lars Ellenberg
2007-04-11 0:16 ` Barry Naujok
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070405162235.GA816@barkeeper1.linbit \
--to=lars.ellenberg@linbit.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox