From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cn.fujitsu.com ([59.151.112.132]:41613 "EHLO heian.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751413AbbGJAej (ORCPT ); Thu, 9 Jul 2015 20:34:39 -0400 Subject: Re: btrfs partition converted from ext4 becomes read-only minutes after booting: WARNING: CPU: 2 PID: 2777 at ../fs/btrfs/super.c:260 __btrfs_abort_transaction+0x4b/0x120 To: Chris Murphy , Vytautas D References: <558CB0D4.8060401@cn.fujitsu.com> <558CB404.8050300@cn.fujitsu.com> CC: Robert Munteanu , Btrfs BTRFS From: Qu Wenruo Message-ID: <559F131B.30206@cn.fujitsu.com> Date: Fri, 10 Jul 2015 08:34:35 +0800 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Sender: linux-btrfs-owner@vger.kernel.org List-ID: One of my patch addressed a problem that a converted btrfs can't pass btrfsck. Not sure if that is the cause, but if you can try btrfs-progs v3.19.1, the one without my btrfs-progs patches and some other newer convert related patches, and see the result? I think this would at least provide the base for bisect the btrfs-progs if the bug is in btrfs-progs. Thanks, Qu Chris Murphy wrote on 2015/07/09 15:38 -0600: > On Thu, Jul 9, 2015 at 4:52 AM, Vytautas D wrote: >> >> >> does these bugs exist in systems that converted from ext4 to btrfs using >> kernel 3.13 and then upgraded to kernel 4.1 ? > > I don't recall what btrfs-progs and kernel I last tested ext4 > conversion with. I know this is a regression, I just don't know how > old it is. I think there's more than one bug here (obviously since > I've filed 4 related bugs in ~24 hours), but I really don't know the > scope of the problem. But the case where the recommended procedure not > only fails but corrupts the file system and it can't be fixed or > rolled back, is not good. > > Perhaps the wiki should provide a warning that this is currently > broken, status unknown, or something? >