From: Dave Chinner <david@fromorbit.com>
To: Jason Vagalatos <Jason.Vagalatos@citrixonline.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Stalled xfs_repair on 100TB filesystem
Date: Wed, 3 Mar 2010 11:25:00 +1100 [thread overview]
Message-ID: <20100303002500.GH18369@discord.disaster> (raw)
In-Reply-To: <DD534F7C25BFA14FB18E6D603135D7EA0A11E82ECB@sbapexch05>
On Tue, Mar 02, 2010 at 09:22:34AM -0800, Jason Vagalatos wrote:
> Hello, On Friday 2/26 I started an xfs_repair on a 100TB
> filesystem:
>
> #> nohup xfs_repair -v -l /dev/logfs-sessions/logdev
> /dev/logfs-sessions/sessions >
> /root/xfs_repair.out.logfs1.sjc.02262010 &
>
> I've been monitoring the process with 'top' and tailing the output
> file from the redirect above. I believe the repair has
> "stalled". When the process was running 'top' showed almost all
> physical memory consumed and 12.6G of virt memory consumed by
> xfs_repair. It made it all the way to Phase 6 and has been
> sitting at agno = 14 for almost 48 hours. The memory consumption
> of xfs_repair has ceased but the process is still "running" and
> consuming 100% CPU:
I wish we could reproduce hangs like this easily. I'd kill the
repair and run with the -P option. From the xfs_repair man page:
-P Disable prefetching of inode and directory blocks. Use
this option if you find xfs_repair gets stuck and
proceeding. Interrupting a stuck xfs_repair is safe.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-03-03 0:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 17:22 Stalled xfs_repair on 100TB filesystem Jason Vagalatos
2010-03-03 0:25 ` Dave Chinner [this message]
2010-03-03 0:35 ` Stan Hoeppner
2010-03-03 0:44 ` Eric Sandeen
2010-03-03 1:15 ` Jason Vagalatos
2010-03-03 2:08 ` 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=20100303002500.GH18369@discord.disaster \
--to=david@fromorbit.com \
--cc=Jason.Vagalatos@citrixonline.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.