From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from userp1040.oracle.com ([156.151.31.81]:36939 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751035AbdHAWqf (ORCPT ); Tue, 1 Aug 2017 18:46:35 -0400 Date: Tue, 1 Aug 2017 15:45:19 -0600 From: Liu Bo To: Roman Mamedov Cc: "marcel.cochem" , linux-btrfs@vger.kernel.org Subject: Re: BTRFS error: bad tree block start 0 623771648 Message-ID: <20170801214519.GF26357@localhost.localdomain> Reply-To: bo.li.liu@oracle.com References: <20170731181200.GA3459@lim.localdomain> <20170801110410.0813a03a@natsu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20170801110410.0813a03a@natsu> Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Tue, Aug 01, 2017 at 11:04:10AM +0500, Roman Mamedov wrote: > On Mon, 31 Jul 2017 11:12:01 -0700 > Liu Bo wrote: > > > Superblock and chunk tree root is OK, looks like the header part of > > the tree root is now all-zero, but I'm unable to think of a btrfs bug > > which can lead to that (if there is, it is a serious enough one) > > I see that the FS is being mounted with "discard". So maybe it was a TRIM gone > bad (wrong location or in a wrong sequence). > By checking discard path in btrfs, looks OK to me, more likely it's caused by problems from underlying stuff. Thanks, -liubo > Generally it appears to be not recommended to use "discard" by now (because of > its performance impact, and maybe possible issues like this), instead schedule > to call "fstrim " once a day or so, and/or on boot-up. > > > on ssd like disks, by default there is only one copy for metadata. > > Time and time again, the default of "single" metadata for SSD is a terrible > idea. Most likely DUP metadata would save the FS in this case. > > -- > With respect, > Roman > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html