public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: linux-bcache@vger.kernel.org, BTRFS <linux-btrfs@vger.kernel.org>
Cc: kent.overstreet@gmail.com, swami@petaramesh.org
Subject: Complete disparition of BTRFS FS on bcache, kernel 5.8
Date: Fri, 21 Aug 2020 11:58:08 +0200	[thread overview]
Message-ID: <98e963a4-dbd0-7d7b-e8e5-cd846cd6c418@petaramesh.org> (raw)

Hello,

I have a Manjaro system on which the disks setup is as follows :

sda : mechanical HD

- sda1 -> LUKS encryption -> bcache backing dev bcache0 -> BTRFS FS -> /home

sdb : SSD

- sdb1 -> System EFI partition

- sdb2 -> LUKS encryption -> BTRFS FS -> / (system root FS)

- sdb3 -> LUKS encryption -> bcache cache dev bcache0 (for /home)

- sdb4 -> LUKS encryption -> SWAP

bcache working in writeback mode.

This setup had worked perfectly flawlessly for more than a year with 
different kernel versions.

Then I upgraded to Manjaro kernel 5.8

I was immediately under the impression that the overall disks access 
performance had much worsened.

Then, after I had worked on a couple VMs hosted on the bcache'd FS, I 
tried to power the system down normally from the GUI menu.

At that time there was high disk activity going on and systemd waited 
for more than 1'30" trying to unmount the FSes, to no avail. Looks like 
everything didn't make it to disk before it eventually timed out.

Afterwards systemd killed the processes and powered down the system.

At next powerup, the bcache would activate as usual, but the BTRFS 
filesystem on it was completely *GONE*. The “file” utility would 
identify the device as “data” (not an FS), mount would complain that 
this wasn't any recognizable FS anymore, and “btrfs-find-root” wouldn't 
find anything.

AFAIK the FS is completely gone.

I've been using BTRFS over bcache over LUKS (on 2 machines) for years, 
and it was usually very stable until today.

Both the HD and SSD looks healthy and their SMART do not record any 
error, remapped sectors, or other issue.

So this was just to let you know... There might be some new kernel issue 
in bcache or BTRFS or their relation to one another.

Best regards.

ॐ

-- 
Swâmi Petaramesh <swami@petaramesh.org> PGP 9076E32E


             reply	other threads:[~2020-08-21  9:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21  9:58 Swâmi Petaramesh [this message]
2020-08-21 13:13 ` Complete disparition of BTRFS FS on bcache, kernel 5.8 Matthias Ferdinand

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=98e963a4-dbd0-7d7b-e8e5-cd846cd6c418@petaramesh.org \
    --to=swami@petaramesh.org \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-bcache@vger.kernel.org \
    --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
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