public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Stransky <nico@stransky.cx>
To: linux-xfs@oss.sgi.com
Subject: Re: xfs_repair on a 1.5 TiB image has been hanging for about an hour, now
Date: Fri, 12 Feb 2010 13:16:16 -0500	[thread overview]
Message-ID: <hl45te$kjs$1@ger.gmane.org> (raw)
In-Reply-To: <4B7594D3.6040304@sandeen.net>

Right :)
I'm using xfsprogs 3.1.0, on Debian Lenny, because 3.1.1 fails to build
for some reason.
I've been trying to repair a 1.4TB filesystem for more than a week,
without success. xfs_repair never completes. I straced the stuck process
today and got:
Process 28510 attached - interrupt to quit
futex(0x429cb58, FUTEX_WAIT_PRIVATE, 2, NULL

I'm running xfs_repair -P -t5 -m500 /dev/sda1 because the machine only
has 2GB of RAM and was swapping like crazy. I'll see how it goes with
the -P option.

I'm happy to provide xfs_metadump if this still hangs!

Thanks,
    Nico

On 2/12/10 12:50 PM, Eric Sandeen wrote:
> Nicolas Stransky wrote:
>> I'm running into the same problem exactly, except that it's not 10
>> minutes, but DAYS.
>>
>> What is the version that fixes this?
> 
> hard to say without knowing for sure what version you're using, and
> what exactly "this" is that you're seeing :)
> 
> Providing an xfs_metadump of the corrupted fs that hangs repair
> is also about the best thing you could do for investigation,
> if you've already determined that the latest release doesn't help.
> 
> -Eric
> 
>> Thanks
>>
>> On 2/12/10 12:02 PM, Richard Hartmann wrote:
>>> On Fri, Feb 12, 2010 at 17:45, Richard Hartmann
>>> <richih.mailinglist@gmail.com> wrote:
>>>
>>>> I thought about that, but I fear that I will flood my terminal off with crap
>>>> and/or that I somehow impair xfs_repair while doing so.
>>> Running it for ten minutes gives me:
>>>
>>> root@grml ~ # strace -p13629
>>> Process 13629 attached - interrupt to quit
>>> futex(0xa381b4cc, FUTEX_WAIT_PRIVATE, 2, NULL^C <unfinished ...>
>>> Process 13629 detached
>>> root@grml ~ #
>>
>>
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 


-- 
Nico

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-02-12 18:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12 14:07 xfs_repair on a 1.5 TiB image has been hanging for about an hour, now Richard Hartmann
2010-02-12 15:28 ` Eric Sandeen
2010-02-12 16:45   ` Richard Hartmann
2010-02-12 17:02     ` Richard Hartmann
2010-02-12 17:31       ` Nicolas Stransky
2010-02-12 17:50         ` Eric Sandeen
2010-02-12 18:16           ` Nicolas Stransky [this message]
2010-02-12 20:30             ` Nicolas Stransky
2010-02-12 20:39               ` Richard Hartmann
2010-02-12 22:21                 ` Nicolas Stransky
2010-02-12 20:48               ` Eric Sandeen
2010-02-12 22:27                 ` Nicolas Stransky
2010-02-12 20:01           ` Richard Hartmann
2010-02-12 20:11             ` Eric Sandeen
2010-02-12 22:19             ` Eric Sandeen
     [not found] ` <20100212165801.GA7323@puku.stupidest.org>
2010-02-12 17:04   ` Richard Hartmann
2010-02-12 17:06     ` Richard Hartmann
2010-02-12 17:13     ` Eric Sandeen

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='hl45te$kjs$1@ger.gmane.org' \
    --to=nico@stransky.cx \
    --cc=linux-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