From: Hendrik Friedel <hendrik@friedels.name>
To: Omar Sandoval <osandov@fb.com>,
Donald Pearson <donaldwhpearson@gmail.com>,
Hugo Mills <hugo@carfax.org.uk>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: size 2.73TiB used 240.97GiB after balance
Date: Mon, 06 Jul 2015 23:12:29 +0200 [thread overview]
Message-ID: <559AEF3D.2070408@friedels.name> (raw)
In-Reply-To: <559AEAAB.4070401@fb.com>
Hello,
oh dear, I fear I am in trouble:
recovery-mounted, I tried to save some data, but the system hung.
So I re-booted and sdc is now physically disconnected.
Label: none uuid: b4a6cce6-dc9c-4a13-80a4-ed6bc5b40bb8
Total devices 3 FS bytes used 4.67TiB
devid 1 size 2.73TiB used 2.67TiB path /dev/sdc
devid 2 size 2.73TiB used 2.67TiB path /dev/sdb
*** Some devices missing
I try to mount the rest again:
mount -o recovery,ro /dev/sdb /mnt/__Complete_Disk
mount: wrong fs type, bad option, bad superblock on /dev/sdb,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
root@homeserver:~# dmesg | tail
[ 447.059275] BTRFS info (device sdc): enabling auto recovery
[ 447.059280] BTRFS info (device sdc): disk space caching is enabled
[ 447.086844] BTRFS: failed to read chunk tree on sdc
[ 447.110588] BTRFS: open_ctree failed
[ 474.496778] BTRFS info (device sdc): enabling auto recovery
[ 474.496781] BTRFS info (device sdc): disk space caching is enabled
[ 474.519005] BTRFS: failed to read chunk tree on sdc
[ 474.540627] BTRFS: open_ctree failed
mount -o degraded,ro /dev/sdb /mnt/__Complete_Disk
Does work now though.
So, how can I remove the reference to the failed disk and check the data
for consistency (scrub I suppose, but is it safe?)?
Regards,
Hendrik
On 06.07.2015 22:52, Omar Sandoval wrote:
> On 07/06/2015 01:01 PM, Donald Pearson wrote:
>> Based on my experience Hugo's advice is critical, get the bad drive
>> out of the pool when in raid56 and do not try to replace or delete it
>> while it's still attached and recognized.
>>
>> If you add a new device, mount degraded and rebalance. If you don't,
>> mount degraded then device delete missing.
>>
>
> Watch out, replacing a missing device in RAID 5/6 currently doesn't work
> and will cause a kernel BUG(). See my patch series here:
> http://www.spinics.net/lists/linux-btrfs/msg44874.html
>
--
Hendrik Friedel
Auf dem Brink 12
28844 Weyhe
Tel. 04203 8394854
Mobil 0178 1874363
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
next prev parent reply other threads:[~2015-07-06 21:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 19:20 size 2.73TiB used 240.97GiB after balance Hendrik Friedel
2015-07-06 19:44 ` Hendrik Friedel
2015-07-06 19:49 ` Hugo Mills
2015-07-06 20:01 ` Donald Pearson
2015-07-06 20:52 ` Omar Sandoval
2015-07-06 21:12 ` Hendrik Friedel [this message]
2015-07-06 21:49 ` Donald Pearson
[not found] <000f4242.05e425492a977c7b@friedels.name>
2015-07-06 22:59 ` Donald Pearson
2015-07-07 5:42 ` Hendrik Friedel
2015-07-07 13:14 ` Donald Pearson
2015-07-08 18:56 ` Hendrik Friedel
2015-07-08 19:06 ` Donald Pearson
2015-07-08 21:29 ` Hendrik Friedel
2015-07-08 22:16 ` Donald Pearson
2015-07-09 12:02 ` Austin S Hemmelgarn
2015-07-09 11:59 ` 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=559AEF3D.2070408@friedels.name \
--to=hendrik@friedels.name \
--cc=donaldwhpearson@gmail.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@fb.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.