linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Gelmini <andrea.gelmini@linux.it>
To: linux-btrfs@vger.kernel.org
Subject: Linux-next regression?
Date: Mon, 26 Nov 2018 16:01:37 +0100	[thread overview]
Message-ID: <20181126150137.GA16029@glet> (raw)

Hi everybody,
   and thanks a lot for your work.

   I'm using BTRFS over LVM over cryptsetup, over Samsung SSD 860 EVO (latest git of btrfs-progs).
   Usually I run kernel in development, because I know BTRFS is young and there are still lots of bugs and corner case to fix.

   Anyway, I just want to submit to you a - maybe - useful info.

   Yesterday I compiled and booted latest linux-next,¹ and I've got this:

-----------
nov 26 01:18:22 glet kernel: Btrfs loaded, crc32c=crc32c-intel
nov 26 01:18:22 glet kernel: BTRFS: device label home devid 1 transid 32759 /dev/mapper/cry-home
nov 26 01:18:23 glet kernel: BTRFS info (device dm-3): force lzo compression, level 0
nov 26 01:18:23 glet kernel: BTRFS info (device dm-3): disk space caching is enabled
nov 26 01:18:23 glet kernel: BTRFS info (device dm-3): has skinny extents
nov 26 01:18:23 glet kernel: BTRFS error (device dm-3): bad tree block start, want 2152002191360 have 8829432654847901262
nov 26 01:18:23 glet kernel: BTRFS error (device dm-3): failed to read block groups: -5
nov 26 01:18:23 glet kernel: BTRFS error (device dm-3): open_ctree failed
-----------

   Now, rebooting with 4.19.0-041900 (downloaded from here)², or 4.20-rc4 (compiled on this machine), the problem disappears.

   Now, running scrub a few times, and copying data (all files of the logical volume) to external device, gives no complain.

   Here I stop. This is my primary dev laptop, and at the moment I can't spend time switching/rebooting/testing. I'm comparing the data with last backup (I rsync each hour), but it takes time (it's more then 3TB).

   So, that was about to let you know. Well, it's Ubuntu 18.10, and between reboots no dist-upgrade or changes in booting related packages or systemd.

  One question: I can completely trust the ok return status of scrub? I know is made for this, but shit happens...

Kisses,
Gelma   

-----------------
¹ commit:  8c9733fd9806c71e7f2313a280f98cb3051f93df
  "Add linux-next specific files for 20181123"
² http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19/

             reply	other threads:[~2018-11-26 15:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 15:01 Andrea Gelmini [this message]
2018-11-27  1:13 ` Linux-next regression? Qu Wenruo
2018-11-27 14:11   ` Andrea Gelmini
2018-11-27 14:16     ` Qu Wenruo
2018-11-28 16:05       ` Andrea Gelmini
2018-12-04 22:29         ` Chris Mason
2018-12-05 10:59           ` Andrea Gelmini
2018-12-05 19:32             ` Chris Mason

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=20181126150137.GA16029@glet \
    --to=andrea.gelmini@linux.it \
    --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;
as well as URLs for NNTP newsgroup(s).