linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Mader <Wolfgang_Mader@brain-frog.de>
To: Anand Jain <Anand.Jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: How to get the devid of a missing device
Date: Mon, 27 Apr 2015 10:01:52 +0200	[thread overview]
Message-ID: <2297316.VxuZ9hm5NH@discus> (raw)
In-Reply-To: <553DBF87.2080205@oracle.com>

On Monday, April 27, 2015 12:48:07 PM Anand Jain wrote:
> On 04/27/2015 02:39 AM, Wolfgang Mader wrote:
> > 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. Having the filesystem mounted in degraded mode under mnt,
> > btrfs fs
>   At the user end there is no way. unless you want to use gdb and dump
>   the fs_uuids and check.
> 
>   Submitted these patches as of now to obtain from the logs. Will
>   help in the situation when device is missing at the time of mount.
> 
> Btrfs: check error before reporting missing device and add uuid
> Btrfs: log when missing device is created
> 
>   For long term we have sysfs interface, patches are in the ML if you
>   want to tests.
> 
> Good luck.
> 
> Anand

Great. Thank you for patching this in.

Best,
Ẃolfgang

> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      reply	other threads:[~2015-04-27  8:01 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
2015-04-27  4:48 ` Anand Jain
2015-04-27  8:01   ` Wolfgang Mader [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=2297316.VxuZ9hm5NH@discus \
    --to=wolfgang_mader@brain-frog.de \
    --cc=Anand.Jain@oracle.com \
    --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).