From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Hesse Subject: Re: [Btrfs-devel] [ANNOUNCE] Btrfs v0.10 (online growing/shrinking, ext3 conversion, and more) Date: Mon, 21 Jan 2008 09:57:04 +0100 Message-ID: <200801210957.06927.mail@earthworm.de> References: <20080115105238.4fc3e992@think.oraclecorp.com> <200801180017.55007.mail@earthworm.de> <200801180848.15634.chris.mason@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: btrfs-devel@oss.oracle.com, linux-fsdevel@vger.kernel.org To: Chris mason Return-path: Received: from kolab.mylinuxtime.de ([212.112.242.22]:35660 "EHLO kolab.mylinuxtime.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758033AbYAUI5T (ORCPT ); Mon, 21 Jan 2008 03:57:19 -0500 In-Reply-To: <200801180848.15634.chris.mason@oracle.com> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Friday 18 January 2008, Chris mason wrote: > On Thursday 17 January 2008, Christian Hesse wrote: > > On Thursday 17 January 2008, Chris mason wrote: > > > So, I've put v0.11 out there. > > > > Ok, back to the suspend problem I mentioned: > > [ oopsen ] > > > I get this after a suspend/resume cycle with mounted btrfs. > > Looks like metadata corruption. How are you suspending? No, that's not metadata corruption. After reset I can use the image without problems. After resume the first access to the fs oopses. I use kernel 2.6.24-rc8 with tuxonice 3.0-rc3 and btrfs 0.11. Back in early december I reported the problem for btrfs 0.9. Seems like the lockfs call still is not implemented. Any hints what I need when I try to code it myself? -- Regards, Chris