public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nscott@aconex.com>
To: Fong Vang <sudoyang@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_check running out of memory
Date: Fri, 04 Apr 2008 10:33:38 +1100	[thread overview]
Message-ID: <1207265618.21048.159.camel@edge.scott.net.au> (raw)
In-Reply-To: <4f52331f0804031623hc880b03i90f1eed342e97f3c@mail.gmail.com>


On Thu, 2008-04-03 at 16:23 -0700, Fong Vang wrote:
> 
> 
> 
> 
> good to know.  Doesn't xfs_check also repair?  with xfs_repair -n,

No, it doesn't.

>  this doesn't do any repair.  SO the right approach on big volumes
> would be to run xfs_repair -n first to detect problem then xfs_repair
> to fix?

Sure - whatever floats your boat.

> thank you for the info.  much appreciated.  just, curious.  where did
> you get this info?

>From the source.

cheers.

-- 
Nathan

      reply	other threads:[~2008-04-03 23:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 22:56 xfs_check running out of memory Fong Vang
2008-04-03 23:03 ` Nathan Scott
2008-04-03 23:11   ` Fong Vang
2008-04-03 23:16     ` Nathan Scott
2008-04-03 23:23       ` Fong Vang
2008-04-03 23:33         ` Nathan Scott [this message]

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=1207265618.21048.159.camel@edge.scott.net.au \
    --to=nscott@aconex.com \
    --cc=sudoyang@gmail.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