public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Barry Naujok" <bnaujok@melbourne.sgi.com>
To: 'Lars Ellenberg' <lars.ellenberg@linbit.com>, xfs@oss.sgi.com
Subject: RE: xfs_repair leaves empty but undeletable dirs in lost+found
Date: Tue, 10 Apr 2007 11:55:14 +1000	[thread overview]
Message-ID: <200704100151.LAA27963@larry.melbourne.sgi.com> (raw)
In-Reply-To: <20070405162235.GA816@barkeeper1.linbit>

Hi Lars,

Would it be possible for you apply the patch I posted to xfs@oss
in Feb http://oss.sgi.com/archives/xfs/2007-02/msg00072.html
to the latest xfsprogs source, make and install it and run:

# xfs_metadump /dev/md1 - | bzip2 > /tmp/bad_xfs.bz2

And make the image available for me to download and analyse?

Regards,
Barry. 

> -----Original Message-----
> From: xfs-bounce@oss.sgi.com [mailto:xfs-bounce@oss.sgi.com] 
> On Behalf Of Lars Ellenberg
> Sent: Friday, 6 April 2007 2:23 AM
> To: xfs@oss.sgi.com
> Subject: Re: xfs_repair leaves empty but undeletable dirs in 
> lost+found
> 
> 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.
> 
> 

  reply	other threads:[~2007-04-10  1:51 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
2007-04-10  1:55   ` Barry Naujok [this message]
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=200704100151.LAA27963@larry.melbourne.sgi.com \
    --to=bnaujok@melbourne.sgi.com \
    --cc=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