Linux-BTRFS Archive on lore.kernel.org
 help / color / Atom feed
From: Gard Vaaler <gardv@megacandy.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Unrecoverable corruption after loss of cache
Date: Wed, 4 Dec 2019 16:50:31 +0100
Message-ID: <F7C74BD8-4505-4E74-81F2-EB0D603ABCEC@megacandy.net> (raw)
In-Reply-To: <7D7AA867-8B53-4CD5-83EF-95EABAD2A77C@megacandy.net>

> 1. des. 2019 kl. 18:27 skrev Gard Vaaler <gardv@megacandy.net>:
> 
> Trying to recover a filesystem that was corrupted by losing writes due to a failing caching device, I get the following error:
>> ERROR: child eb corrupted: parent bytenr=2529690976256 item=0 parent level=2 child level=0
> 
> Trying to zero the journal or reinitialising the extent tree yields the same error. Is there any way to recover the filesystem?

Update: using 5.4, btrfs claims to have zeroed the journal:

> [liveuser@localhost-live btrfs-progs-5.4]$ sudo ./btrfs rescue zero-log /dev/bcache0
> Clearing log on /dev/bcache0, previous log_root 2529694416896, level 0

... but still complains about the journal on mount:

> [  703.964344] BTRFS info (device bcache1): disk space caching is enabled
> [  703.964347] BTRFS info (device bcache1): has skinny extents
> [  704.215748] BTRFS error (device bcache1): parent transid verify failed on 2529691090944 wanted 319147 found 310171
> [  704.216131] BTRFS error (device bcache1): parent transid verify failed on 2529691090944 wanted 319147 found 314912
> [  704.216137] BTRFS error (device bcache1): failed to read block groups: -5
> [  704.227110] BTRFS error (device bcache1): open_ctree failed

-- 
Gard


  parent reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-01 17:27 Gard Vaaler
2019-12-01 18:51 ` Nikolay Borisov
2019-12-02 21:27   ` Gard Vaaler
2019-12-05  2:45     ` Zygo Blaxell
2019-12-04 15:50 ` Gard Vaaler [this message]
2019-12-04 19:08   ` Chris Murphy
2019-12-04 20:21     ` Gard Vaaler
     [not found]     ` <B154F1B0-C80A-4E7E-B105-B0E654279E28@megacandy.net>
2019-12-04 21:09       ` Chris Murphy
2019-12-05  0:34         ` Gard Vaaler
2019-12-05  1:26           ` Chris Murphy

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=F7C74BD8-4505-4E74-81F2-EB0D603ABCEC@megacandy.net \
    --to=gardv@megacandy.net \
    --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
	public-inbox-index linux-btrfs

Example config snippet for mirrors

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.git