From: Tomasz Chmielewski <tch@virtall.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: unable to mount btrfs after upgrading from 4.16.1 to 4.19.1
Date: Sat, 10 Nov 2018 04:15:47 +0900 [thread overview]
Message-ID: <62812fe46b56258a47dc9df38c76e7f0@virtall.com> (raw)
In-Reply-To: <20181109232052.19233269@natsu>
On 2018-11-10 03:20, Roman Mamedov wrote:
> On Sat, 10 Nov 2018 03:08:01 +0900
> Tomasz Chmielewski <tch@virtall.com> wrote:
>
>> After upgrading from kernel 4.16.1 to 4.19.1 and a clean restart, the
>> fs
>> no longer mounts:
>
> Did you try rebooting back to 4.16.1 to see if it still mounts there?
Yes, just did.
Interestingly, it does mount when I boot back to 4.16.1 - side note - it
takes some 50 (!) minutes and ~8 GB of reads (according to iostat -m) to
mount... device size is 16 TB, on HDD.
Tomasz Chmielewski
https://lxadm.com
next prev parent reply other threads:[~2018-11-09 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 18:08 unable to mount btrfs after upgrading from 4.16.1 to 4.19.1 Tomasz Chmielewski
2018-11-09 18:20 ` Roman Mamedov
2018-11-09 19:15 ` Tomasz Chmielewski [this message]
2018-11-09 19:20 ` Tomasz Chmielewski
2018-11-09 20:25 ` Tomasz Chmielewski
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=62812fe46b56258a47dc9df38c76e7f0@virtall.com \
--to=tch@virtall.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.net \
/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).