public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Improve btrfs man page
Date: Mon, 24 Mar 2014 18:50:50 +0000 (UTC)	[thread overview]
Message-ID: <pan$83baa$4fa193c7$def231f6$e0d4bf9e@cox.net> (raw)
In-Reply-To: 1395607101.4607.0.camel@spike.sunnydale.homeip.net

Per Nystrom posted on Sun, 23 Mar 2014 13:38:21 -0700 as excerpted:

> I am going through the process of replacing a bad drive in a RAID 1
> mirror.  The filesystem wouldn't mount because of the missing device,
> and the btrfs man pages were not helpful in resolving it.  Specifically,
> it would have been very useful to me if this part of the wiki were
> included somewhere:
> 
> https://btrfs.wiki.kernel.org/index.php/
Using_Btrfs_with_Multiple_Devices#Replacing_failed_devices
> 
> There is no mention in the man pages of the -o degraded mount option,
> which is needed to even manipulate the filesystem; nor is there any
> mention of the special option "missing" for device delete.
> 
> I'm sure I'm not the only one who would turn to man btrfs first when
> facing a failed drive.

Of course traditionally, mount options are covered in the mount manpage.  
But btrfs is new enough I guess it's not in that manpage yet, which has 
frustrated me too, since that's intuitively where I look.

The mount-manpage alternatives are either the wiki, or the
Documentation/filesystems/btrfs.txt file in the kernel sources.

But you're absolutely correct about btrfs device delete missing.  Btrfs 
device delete is of course in the btrfs manpage, but the one-sentence 
description lacks any hint that "missing" can be used if the device 
simply isn't there any longer.  Fleshing that out a bit beyond the single 
sentence would definitely be useful!

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


      reply	other threads:[~2014-03-24 18:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-23 20:38 Improve btrfs man page Per Nystrom
2014-03-24 18:50 ` Duncan [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='pan$83baa$4fa193c7$def231f6$e0d4bf9e@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    /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