From: Kai Hendry <hendry@iki.fi>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: USB upgrade fun
Date: Sun, 29 Oct 2017 11:20:55 +0800 [thread overview]
Message-ID: <1509247255.1470208.1154302000.6571EE79@webmail.messagingengine.com> (raw)
In-Reply-To: <8cff4fc5-6a33-e076-bfdb-d40dca8023ed@gmx.com>
On Sat, 28 Oct 2017, at 03:58 PM, Qu Wenruo wrote:
> Don't get confused with the name, to use "fix-dev-size" you need to run
> "btrfs rescue fix-dev-size"
[hendry@nuc btrfs-progs]$ sudo ./btrfs rescue fix-device-size /dev/sdc1
warning, device 2 is missing
ERROR: devid 2 is missing or not writeable
ERROR: fixing device size needs all device(s) present and writeable
[hendry@nuc btrfs-progs]$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 vfat 0C95-8576 /boot
└─sda2 btrfs c5f98288-5ab3-4236-b00e-f2cd15c0616d /
sdb
sdc
└─sdc1 btrfs extraid1 5cab2a4a-e282-4931-b178-bec4c73cdf77
[hendry@nuc btrfs-progs]$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 vfat 0C95-8576 /boot
└─sda2 btrfs c5f98288-5ab3-4236-b00e-f2cd15c0616d /
sdb
└─sdb1 btrfs extraid1 5cab2a4a-e282-4931-b178-bec4c73cdf77
sdc
└─sdc1 btrfs extraid1 5cab2a4a-e282-4931-b178-bec4c73cdf77
[hendry@nuc btrfs-progs]$ sudo ./btrfs rescue fix-device-size /dev/sdc1
Couldn't setup extent tree
Couldn't setup device tree
ERROR: could not open btrfs
[hendry@nuc btrfs-progs]$ sudo ./btrfs rescue fix-device-size /dev/sdb1
leaf parent key incorrect 1320477425664
ERROR: could not open btrfs
[hendry@nuc btrfs-progs]$ sudo mount -o degraded /dev/sdb1 /mnt/raid1/
mount: /mnt/raid1: wrong fs type, bad option, bad superblock on
/dev/sdb1, missing codepage or helper program, or other error.
Still unable to mount. Damn. Maybe I'm chasing a red herring? Here are
the relevant kernel logs:
Oct 29 10:56:45 nuc kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
Oct 29 10:57:32 nuc kernel: BTRFS info (device sdc1): allowing degraded
mounts
Oct 29 10:57:32 nuc kernel: BTRFS info (device sdc1): disk space caching
is enabled
Oct 29 10:57:32 nuc kernel: BTRFS info (device sdc1): has skinny extents
Oct 29 10:57:33 nuc kernel: BTRFS error (device sdc1): super_total_bytes
4000795746304 mismatch with fs_devices total_rw_bytes 4000795749888
Oct 29 10:57:33 nuc kernel: BTRFS error (device sdc1): failed to read
chunk tree: -22
Oct 29 10:57:33 nuc kernel: BTRFS error (device sdc1): open_ctree failed
Nonetheless if I reboot to 4.4, I can still mount. However my root is
bizarrely out of space or inodes so journalctl et al is unusable.
Kind regards,
next prev parent reply other threads:[~2017-10-29 3:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 9:58 USB upgrade fun Kai Hendry
2017-10-10 2:06 ` Satoru Takeuchi
2017-10-11 4:18 ` Kai Hendry
2017-10-12 2:27 ` Kai Hendry
2017-10-12 17:19 ` Chris Murphy
2017-10-12 16:57 ` Chris Murphy
2017-10-12 17:19 ` Austin S. Hemmelgarn
2017-10-13 1:42 ` Kai Hendry
2017-10-13 11:22 ` Austin S. Hemmelgarn
2017-10-13 18:28 ` Chris Murphy
2017-10-28 7:03 ` Kai Hendry
2017-10-28 7:58 ` Qu Wenruo
2017-10-29 3:20 ` Kai Hendry [this message]
2017-10-29 10:02 ` Qu Wenruo
2017-10-30 11:12 ` Kai Hendry
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=1509247255.1470208.1154302000.6571EE79@webmail.messagingengine.com \
--to=hendry@iki.fi \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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 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).