Linux-BTRFS Archive on lore.kernel.org
 help / color / Atom feed
From: mangoblues@gmail.com
To: linux-btrfs@vger.kernel.org
Subject: [BUG] Kernel 5.2: mount fails with can't read superblock on /dev/sdb1 (kernel 5.1.16 and 4.19 is fine)
Date: Fri, 12 Jul 2019 13:05:21 +0200
Message-ID: <CABDitb8iKge1Ut41qxQSG2ep1ozp2Veieha072eANqn_L_LCNw@mail.gmail.com> (raw)

Hi,

After updating to kernel 5.2 (archlinux):  2 out of my 7 btrfs drives
fail to mount on boot.

Error: can't read superblock on /dev/sdb1 and /dev/sdc1.

Going back to kernel 5.1.16 (and 4.19 also) fixes the problem. Btrfsck
reports the 2 drives are OK.

What can I do to fix this ?

Thanks.

$ btrfs fi show

Label: 'disk3'  uuid: 37d68257-a2bf-44e4-82e6-7bda35d3af3c
        Total devices 1 FS bytes used 1.77TiB
        devid    1 size 1.82TiB used 1.82TiB path /dev/sdb1

Label: 'disk4'  uuid: 8b72d7bd-603c-41c0-a395-a763ffe0de8b
        Total devices 1 FS bytes used 2.67TiB
        devid    1 size 2.73TiB used 2.73TiB path /dev/sdc1

Label: 'disk5'  uuid: 1728d60b-bdf2-4baa-8372-de7014d85e1d
        Total devices 1 FS bytes used 3.59TiB
        devid    1 size 3.64TiB used 3.64TiB path /dev/sdg1

Label: 'disk7'  uuid: 5e9437b5-bf53-4135-8b25-52539cfc491e
        Total devices 1 FS bytes used 6.66TiB
        devid    1 size 7.28TiB used 7.23TiB path /dev/sde1

Label: 'disk6'  uuid: ce325155-0922-4c62-9f5d-70cbc1726b5c
        Total devices 1 FS bytes used 3.47TiB
        devid    1 size 3.64TiB used 3.63TiB path /dev/sdd1

Label: 'disk1'  uuid: b9c65214-b1dc-4a97-b798-dc9639177880
        Total devices 1 FS bytes used 3.31TiB
        devid    1 size 3.64TiB used 3.62TiB path /dev/sdh1

Label: 'disk2'  uuid: d77e4116-de32-4ff4-938c-9c6eea6cdd42
        Total devices 1 FS bytes used 6.83TiB
        devid    1 size 7.28TiB used 7.26TiB path /dev/sdf1

             reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 11:05 mangoblues [this message]
2019-07-12 12:18 ` Qu Wenruo
2019-07-12 12:21   ` Qu Wenruo
2019-07-16 10:48   ` mangoblues

Reply instructions:

You may reply publically 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=CABDitb8iKge1Ut41qxQSG2ep1ozp2Veieha072eANqn_L_LCNw@mail.gmail.com \
    --to=mangoblues@gmail.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

Linux-BTRFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-btrfs/0 linux-btrfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-btrfs linux-btrfs/ https://lore.kernel.org/linux-btrfs \
		linux-btrfs@vger.kernel.org linux-btrfs@archiver.kernel.org
	public-inbox-index linux-btrfs


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-btrfs


AGPL code for this site: git clone https://public-inbox.org/ public-inbox