linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan Olbrich <stephanolbrich@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: bad tree block start, want 705757184 have 82362368
Date: Fri, 16 Nov 2018 17:17:19 +0100	[thread overview]
Message-ID: <1758973.r4I5FPff6i@chaos-desktop> (raw)

Hi,

a few days ago my root file system (simple btrfs on a SSD, no RAID or anything) suddenly became read only. 
Looking at dmsg, I found this:

[   19.285020] BTRFS error (device sda2): bad tree block start, want 705757184 have 82362368
[   19.285042] BTRFS: error (device sda2) in __btrfs_free_extent:6804: errno=-5 IO failure
[   19.285048] BTRFS info (device sda2): forced readonly
[   19.285051] BTRFS: error (device sda2) in btrfs_run_delayed_refs:2934: errno=-5 IO failure
[   19.287213] BTRFS error (device sda2): pending csums is 41889792

Late on I got the same errors for my /home partition (on the same drive) as well.
I have snapshots of all partitions on another drive made by btrbk. To get a working system, I made new (rw) snapshots
of the most recent backup and setup grub and fstab, so my system would boot from the other drive.
Unfortunately now I got the "bad tree block start" error again at least once in dmesg but I didn't save it and it's not in syslog :-(
What I remember is, that it was followed by other btrfs error messages saying something about correcting something.
And the filesystem was still read/write this time.
At the moment I can't reproduce it.

Is there any way to find out, which files are affected by the errors above? I don't really trust the data on the drive I'm using at the
moment, as it has shown errors as well, but I have a less current backup on yet another drive but at it is a few weeks old, I don't
want to use it to setup the system on the SSD again, but just copy the relevant files if possible.
Or is it possible to repair the original file system?

Some information about my system:
Kubuntu 18.04
Kernel 4.19.1 when the problem occured, now 4.19.2
btrfs-tools 4.15.1

Regards,
Stephan






             reply	other threads:[~2018-11-16 16:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 16:17 Stephan Olbrich [this message]
2018-11-16 16:44 ` bad tree block start, want 705757184 have 82362368 Nikolay Borisov
2018-11-17 20:34   ` Stephan Olbrich
2018-11-17  8:03 ` Qu Wenruo
2018-11-17 20:28   ` Stephan Olbrich
2018-11-18  0:30     ` Qu Wenruo
2018-11-18  7:56       ` Stephan Olbrich
2018-11-18 13:31         ` Anand Jain
2018-11-19 19:42           ` Stephan Olbrich

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=1758973.r4I5FPff6i@chaos-desktop \
    --to=stephanolbrich@gmx.de \
    --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).