linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Mader <Wolfgang_Mader@brain-frog.de>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: How to get the devid of a missing device
Date: Mon, 27 Apr 2015 10:00:07 +0200	[thread overview]
Message-ID: <1714496.4Yoe3Ejg52@discus> (raw)
In-Reply-To: <pan$7e6ba$6d122ecc$73869bfb$271bf54f@cox.net>

On Monday, April 27, 2015 02:11:05 AM Duncan wrote:
> Wolfgang Mader posted on Sun, 26 Apr 2015 20:39:34 +0200 as excerpted:
> > Hello,
> > 
> > I have a raid10 with one device missing. I would like to use btrfs
> > replace to replace it. However, I am unsure on how to obtain the devid
> > of the missing device.
> 
> The devid is if the device is still active in the filesystem.  If it's
> missing...
> 
> btrfs device delete missing
> 
> That, along with a bunch of other likely helpful information, is covered
> on the wiki:
> 
> https://btrfs.wiki.kernel.org
> 
> Specifically for that (reassemble from the wrap, too lazy to fiddle with
> it on my end):
> 
> https://btrfs.wiki.kernel.org/index.php/
> Using_Btrfs_with_Multiple_Devices#Replacing_failed_devices
> 
> But since it was a four-device raid10 and four devices is the minimum for
> that, I don't believe it'll let you delete until you device add, first.

Thanks for your answer. I know the stuff of that page, but since it is 
possible to use btrfs replace on a missing device I wanted to try that 
approach.

> 
> Of course that means probably some hours for the add, then some more
> hours for the delete missing, during which you obviously hope not to lose
> another device.  Of course the sysadmin's backup rule of thumb applies --
> if you don't have a backup, by definition, loss of the data isn't a big
> deal, or you'd have it backed up.  (And the corollary, it's not a backup
> until it's tested, applies as well.)  So you shouldn't have to worry
> about loss of a second device during that time, because it's either
> backed up or the data isn't worth the trouble to backup and thus loss of
> it with the loss of a second device isn't a big deal.

Well, of course, there is a backup on a different machine. Its in the same 
room, but who has the luxury for off-site backups in a home-use setting! :)

> 
> That page doesn't seem to cover direct replacement, probably because the
> replace command is new and it hasn't been updated.  But AFAIK replace
> doesn't work with a missing device anyway; it's the fast way to replace a
> still listed device, so you don't have to add and then delete, but the
> device has to still be there in ordered to use that shortcut.  (You could
> try using missing with the -r option tho, just in case it works now.  The
> wiki/manpage is a bit vague on that point.)
> 
> > Btw, the file system is too old for skinny metadata and extended inode
> > refs. If I do a btrfs replace or a btrfs device add, must I myself
> > ensure that the new features are not enables for the new device which is
> > to be added?
> 
> I don't believe there's any way to set that manually even if you wanted
> to -- you don't use mkfs on it and the add/replace would overwrite
> existing if you did.  The new device should just take on the attributes
> of the filesystem you're adding it to.

 Good to know.

Thanks


  reply	other threads:[~2015-04-27  8:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-26 18:39 How to get the devid of a missing device Wolfgang Mader
2015-04-27  2:11 ` Duncan
2015-04-27  8:00   ` Wolfgang Mader [this message]
2015-04-27  4:48 ` Anand Jain
2015-04-27  8:01   ` Wolfgang Mader

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=1714496.4Yoe3Ejg52@discus \
    --to=wolfgang_mader@brain-frog.de \
    --cc=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;
as well as URLs for NNTP newsgroup(s).