public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ion Badulescu <ib-xfs@badula.org>
To: xfs@oss.sgi.com
Subject: Re: xfs_repair never finishes on lvm partition
Date: Wed, 22 Jun 2011 11:32:01 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LRH.2.00.1106221115510.16108@ionlinux.tower-research.com> (raw)

Hello,

Sorry for highjacking this old thread from last year. I actually ran into 
the same situation as the original poster, using xfsprogs-3.1.5 on kernel 
2.6.38.7. Using xfs_repair -P fixed the issue, and I also managed to get a 
metadump before repairing it so you guys can take a look and maybe fix the 
prefetch mode.

The strace of the xfs_repair, for what it's worth, seems to show a 
complete deadlock with all threads waiting on futexes:

# strace -f -F -p 8315
Process 8374 attached with 6 threads - interrupt to quit
[pid  8374] futex(0x7f2336d20a84, FUTEX_WAIT, 4, NULL <unfinished ...>
[pid  8373] futex(0x7f2336d20a84, FUTEX_WAIT, 3, NULL) = -1 EAGAIN (Resource temporarily unavailable)
[pid  8372] futex(0x7f2336d20a84, FUTEX_WAIT, 2, NULL <unfinished ...>
[pid  8373] futex(0x7f2336d20a84, FUTEX_WAIT, 4, NULL <unfinished ...>
[pid  8372] <... futex resumed> )       = -1 EAGAIN (Resource temporarily unavailable)
[pid  8372] futex(0x7f2336d20a84, FUTEX_WAIT, 4, NULL <unfinished ...>
[pid  8371] futex(0x7f2336d20a84, FUTEX_WAIT, 1, NULL) = -1 EAGAIN (Resource temporarily unavailable)
[pid  8370] futex(0x7f2336d20b08, FUTEX_WAIT, 0, NULL <unfinished ...>
[pid  8371] futex(0x7f2336d20a84, FUTEX_WAIT, 4, NULL <unfinished ...>
[pid  8315] futex(0x7f2336d1f958, FUTEX_WAIT, 2, NULL^C <unfinished ...>
Process 8315 detached
Process 8370 detached
Process 8371 detached
Process 8372 detached
Process 8373 detached
Process 8374 detached

The metadump is 4.2GB, off of a 2.2TB filesystem. If there are interested 
parties, I can arrange to put online somewhere for an http download.

Thanks,
-Ion

-- 
   It is better to keep your mouth shut and be thought a fool,
             than to open it and remove all doubt.

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

             reply	other threads:[~2011-06-22 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 15:32 Ion Badulescu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-10-04  2:57 xfs_repair never finishes on lvm partition Knowledge Seeker
2010-10-04  7:16 ` Dave Chinner
2010-10-04 13:50   ` Eric Sandeen
2010-10-04 22:48     ` Knowledge Seeker

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=alpine.LRH.2.00.1106221115510.16108@ionlinux.tower-research.com \
    --to=ib-xfs@badula.org \
    --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