Linux-BTRFS Archive on lore.kernel.org
 help / color / Atom feed
* WARNING: fs/btrfs/extent-tree.c:6974 __btrfs_free_extent.isra.0.cold
@ 2019-08-12  5:00 Chris Murphy
  2019-08-12  5:20 ` Qu Wenruo
  0 siblings, 1 reply; 2+ messages in thread
From: Chris Murphy @ 2019-08-12  5:00 UTC (permalink / raw)
  To: Btrfs BTRFS

Filed bug here
https://bugzilla.kernel.org/show_bug.cgi?id=204557

kernel 5.2.8
progs  5.2.1

I'm getting a kernel warning, and tainted kernel following 'btrfs
scrub start' on a file system that was previously corrupted during
failure to clear v1 cache.

It's valid to complain about a problem with the file system that can't
be fixed. But for the scrub to abort and also taint the kernel sounds
like a bug?

-- 
Chris Murphy

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: WARNING: fs/btrfs/extent-tree.c:6974 __btrfs_free_extent.isra.0.cold
  2019-08-12  5:00 WARNING: fs/btrfs/extent-tree.c:6974 __btrfs_free_extent.isra.0.cold Chris Murphy
@ 2019-08-12  5:20 ` Qu Wenruo
  0 siblings, 0 replies; 2+ messages in thread
From: Qu Wenruo @ 2019-08-12  5:20 UTC (permalink / raw)
  To: Chris Murphy, Btrfs BTRFS

[-- Attachment #1.1: Type: text/plain, Size: 1011 bytes --]



On 2019/8/12 下午1:00, Chris Murphy wrote:
> Filed bug here
> https://bugzilla.kernel.org/show_bug.cgi?id=204557

Exactly the WARN_ON()/BUG_ON()s I'm going to kill in this patch:

https://patchwork.kernel.org/patch/11038303/

So hopefully in 5.3/5.4 release, it will be a more developer-friendly
output.
(But still not user-friendly)
> 
> kernel 5.2.8
> progs  5.2.1
> 
> I'm getting a kernel warning, and tainted kernel following 'btrfs
> scrub start' on a file system that was previously corrupted during
> failure to clear v1 cache.
> 
> It's valid to complain about a problem with the file system that can't
> be fixed. But for the scrub to abort and also taint the kernel sounds
> like a bug?
> 
Corruption in extent tree is a serious problem, it could easily screw
btrfs CoW, so we *must* abort transaction when we find anything wrong on
extent tree.
(Ironically, most corruption happens in extent tree).

For the warning part, it is going to be fixed.

Thanks,
Qu


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-12  5:00 WARNING: fs/btrfs/extent-tree.c:6974 __btrfs_free_extent.isra.0.cold Chris Murphy
2019-08-12  5:20 ` Qu Wenruo

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