All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Barry Naujok <bnaujok@sgi.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: REVIEW: Enhance xfs_repair -P option to disable libxfs xfs_buf_t locking
Date: Thu, 29 May 2008 20:17:04 -0500	[thread overview]
Message-ID: <483F5590.30403@sandeen.net> (raw)
In-Reply-To: <op.ubx0ccd33jf8g2@pc-bnaujok.melbourne.sgi.com>

Barry Naujok wrote:
> On Fri, 30 May 2008 10:52:23 +1000, Eric Sandeen <sandeen@sandeen.net>  
> wrote:
> 
>> Barry Naujok wrote:
>>> I hope the subject is explanation enough :)
>> not really ;)
>>
>> Hum, if I normally lock why do I not want to lock?  Locking good?
>> Locking bad?  Locking too slow?  locking for what?  Incoherency ok?  Man
>> page updates? :)
>>
> 
> Ok, man page update:

I like it.  Thanks!

-Eric

> --- a/xfsprogs/man/man8/xfs_repair.8    2008-05-30 11:11:41.000000000 +1000
> +++ b/xfsprogs/man/man8/xfs_repair.8    2008-05-30 11:10:24.075877526 +1000
> @@ -91,6 +91,14 @@
>   should not modify the filesystem but should only scan the
>   filesystem and indicate what repairs would have been made.
>   .TP
> +.B \-P
> +Disable prefetching of inode and directory blocks. Use this option if
> +you find
> +.B xfs_repair
> +gets stuck and stops proceeding. Interrupting a stuck
> +.B xfs_repair
> +is safe.
> +.TP
>   .BI \-m " maxmem"
>   Specifies the approximate maximum amount of memory, in megabytes, to use  
> for
>   .BR xfs_repair .
> @@ -146,9 +154,6 @@
>   outputs its progress every 15 minutes. Reporting is only activated when
>   ag_stride is enabled.
>   .TP
> -.B \-P
> -Disable prefetching of inode and directory blocks.
> -.TP
>   .B \-v
>   Verbose output.
>   .TP
> 
> 

      reply	other threads:[~2008-05-30  1:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30  0:49 REVIEW: Enhance xfs_repair -P option to disable libxfs xfs_buf_t locking Barry Naujok
2008-05-30  0:52 ` Eric Sandeen
2008-05-30  1:03   ` Barry Naujok
2008-05-30  1:13   ` Barry Naujok
2008-05-30  1:17     ` Eric Sandeen [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=483F5590.30403@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=bnaujok@sgi.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.