From: Sean Greenslade <sean@seangreenslade.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: RAID1 disk upgrade method
Date: Wed, 27 Jan 2016 17:45:49 -0500 [thread overview]
Message-ID: <20160127224549.GA4891@fox.rh.rit.edu> (raw)
In-Reply-To: <CAJCQCtRLAoN+w_hy=jxwtCPkJPo_x5OGOshLr4aQ0=ZX3u91xw@mail.gmail.com>
On Sat, Jan 23, 2016 at 05:03:15PM -0700, Chris Murphy wrote:
> Just make sure you have backups before, during, and after all of this,
> which should be the case no matter Btrfs or not. Mixed extent types
> should work fine, but who knows you could get into an edge case at a
> later time for all anyone knows. Looks like skinny extent became
> default in btrfs-progs 3.18.
OK, disks have arrived, and I've completed the first replace.
Interestingly enough, the replace seems to have succeeded, however btrfs
fi show doesn't seem to think so.
Dmesg:
[Wed Jan 27 13:03:09 2016] BTRFS info (device sdb1): disk space caching
is enabled
[Wed Jan 27 13:03:09 2016] BTRFS: has skinny extents
[Wed Jan 27 13:03:09 2016] BTRFS: bdev /dev/sdb1 errs: wr 0, rd 186,
flush 0, corrupt 0, gen 0
[Wed Jan 27 13:05:23 2016] sdc: sdc1
[Wed Jan 27 13:05:25 2016] sdc: sdc1
[Wed Jan 27 13:08:37 2016] BTRFS: dev_replace from /dev/sdb1 (devid 2)
to /dev/sdc1 started
[Wed Jan 27 16:34:49 2016] BTRFS: dev_replace from /dev/sdb1 (devid 2)
to /dev/sdc1 finished
Btrfs fi show:
warning, device 3 is missing
warning, device 3 is missing
warning devid 3 not found already
Label: none uuid: 490b8b7c-59c4-45dc-ac63-6a90f0966776
Total devices 2 FS bytes used 1.45TiB
devid 1 size 1.82TiB used 1.52TiB path /dev/sda1
*** Some devices missing
I haven't rebooted or remounted yet, so I'm curious if this is a bug,
a normal thing that is fixed by a reboot, or what.
Still running the same versions from my original email, but here they
are again:
Linux rat 4.3.3-3-ARCH #1 SMP PREEMPT Wed Jan 20 08:12:23 CET 2016
x86_64 GNU/Linux
btrfs-progs v4.3.1
Thanks,
--Sean
next prev parent reply other threads:[~2016-01-27 22:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 3:45 RAID1 disk upgrade method Sean Greenslade
2016-01-22 4:37 ` Chris Murphy
2016-01-22 10:54 ` Duncan
2016-01-23 21:41 ` Sean Greenslade
2016-01-24 0:03 ` Chris Murphy
2016-01-27 22:45 ` Sean Greenslade [this message]
2016-01-27 23:55 ` Sean Greenslade
2016-01-28 12:31 ` Austin S. Hemmelgarn
2016-01-28 15:37 ` Sean Greenslade
2016-01-28 16:18 ` Chris Murphy
2016-01-28 18:47 ` Sean Greenslade
2016-01-28 19:37 ` Austin S. Hemmelgarn
2016-01-28 19:46 ` Chris Murphy
2016-01-28 19:49 ` Austin S. Hemmelgarn
2016-01-28 20:24 ` Chris Murphy
2016-01-28 20:41 ` Sean Greenslade
2016-01-28 20:44 ` Austin S. Hemmelgarn
2016-01-28 23:01 ` Chris Murphy
2016-01-29 12:14 ` Austin S. Hemmelgarn
2016-01-29 20:27 ` Henk Slager
2016-01-29 20:40 ` Austin S. Hemmelgarn
2016-01-29 22:06 ` Henk Slager
2016-02-01 12:08 ` Austin S. Hemmelgarn
2016-01-29 20:41 ` Chris Murphy
2016-01-30 14:50 ` Patrik Lundquist
2016-01-30 19:44 ` Chris Murphy
2016-02-04 19:20 ` Patrik Lundquist
2016-01-28 19:39 ` Chris Murphy
2016-01-28 22:51 ` Duncan
2016-02-14 0:44 ` Sean Greenslade
2016-01-22 14:27 ` Austin S. Hemmelgarn
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=20160127224549.GA4891@fox.rh.rit.edu \
--to=sean@seangreenslade.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).