From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Kai Hendry <hendry@iki.fi>,
"Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: USB upgrade fun
Date: Sat, 28 Oct 2017 15:58:21 +0800 [thread overview]
Message-ID: <8cff4fc5-6a33-e076-bfdb-d40dca8023ed@gmx.com> (raw)
In-Reply-To: <1509174195.600847.1153723936.0D8751F2@webmail.messagingengine.com>
[-- Attachment #1.1: Type: text/plain, Size: 1949 bytes --]
On 2017年10月28日 15:03, Kai Hendry wrote:
> On Fri, 13 Oct 2017, at 09:42 AM, Kai Hendry wrote:
>> It probably is... since when I remove my new 4TB USB disk from the
>> front, I am at least able to mount my two 2x2TB in degraded mode and see
>> my data!
>
> Just a follow up. I have not been of late been able to mount my data,
> even in degraded mode.
>
> However someone on #btrfs suggested I try an older Linux kernel & I also
> found https://www.spinics.net/lists/linux-btrfs/msg69905.html to
> reaffirm my suspicions.
>
> Low and behold I can mount with an older kernel
> (linux-4.4.3-1-x86_64.pkg.tar.xz) !! But if I reboot into 4.13.9-1-ARCH,
> no worky:
>
> [ 489.139903] BTRFS warning (device sdb1): devid 3 uuid
> e5f03f81-35e7-4a29-9608-bd78864cc0ad is missing
> [ 489.524334] BTRFS info (device sdb1): bdev (null) errs: wr 0, rd 1,
> flush 0, corrupt 0, gen 0
> [ 489.524367] BTRFS info (device sdb1): bdev /dev/sdb1 errs: wr 13361,
> rd 31990017, flush 155, corrupt 0, gen 0
> [ 502.934069] BTRFS warning (device sdb1): missing devices (1) exceeds
> the limit (0), writeable mount is not allowed
> [ 502.980748] BTRFS error (device sdb1): open_ctree failed
>
>
> Does anyone know how I can track the progress of "--fix-dev-size"? It
> doesn't seem part of btrfs-progs 4.13-1...
>
Didn't follow the whole thread, so I can't say much about the original
problem.
But concerning "--fix-dev-size", it's not merged into mainline yet.
So if you really want to try it, you could use the out-of-tree btrfs-progs:
https://github.com/adam900710/btrfs-progs/tree/check_unaligned_dev
Don't get confused with the name, to use "fix-dev-size" you need to run
"btrfs rescue fix-dev-size"
However, according to your kernel message, it seems that you're missing
one device, in which case "fix-dev-size" can't handle yet.
So I'm afraid it can't help much for your case.
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2017-10-28 7:58 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 [this message]
2017-10-29 3:20 ` Kai Hendry
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=8cff4fc5-6a33-e076-bfdb-d40dca8023ed@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=ahferroin7@gmail.com \
--cc=hendry@iki.fi \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).