From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761504AbYEAQTL (ORCPT ); Thu, 1 May 2008 12:19:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753167AbYEAQS6 (ORCPT ); Thu, 1 May 2008 12:18:58 -0400 Received: from el-out-1112.google.com ([209.85.162.182]:54059 "EHLO el-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751117AbYEAQS5 (ORCPT ); Thu, 1 May 2008 12:18:57 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=b/gnGpK+kJhAKILJIPXwgSoCaubGmJ9EjHAcXivuTM2g7A9FWajMXBzmj0BxjiPO2zUzghzuwckjs/TQOuJIYjHCyR2q1yyLGWR5vFmHq23P75wwUO8pGo8OmNWG6l9coTcZMuFs48dLG/2m1Je+f9lwGNTphc8xuJmqPZiOCTo= Message-ID: Date: Thu, 1 May 2008 09:18:55 -0700 From: "Jeff Schroeder" Reply-To: jeffschroeder@computer.org To: "Chris Mason" Subject: Re: Btrfs v0.14 Released Cc: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org In-Reply-To: <200805011204.20847.chris.mason@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200804291601.32945.chris.mason@oracle.com> <200805011204.20847.chris.mason@oracle.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 1, 2008 at 9:04 AM, Chris Mason wrote: > On Tuesday 29 April 2008, Chris Mason wrote: > > Hello everyone, > > > > Btrfs v0.14 is now available for download. Please note the disk format has > > changed, and it is not compatible with older versions of Btrfs. > > > > For downloads and documention, please see the Btrfs project page: > > > > http://btrfs.wiki.kernel.org > > > > Hello everyone, > > I've rolled up some fixes for older kernels and fixed an uninitialized > variables in btrfs-progs that could cause an oops on mount. I'll wait a few > days to see if other bug reports come in and cut a 0.15 with any other > critical fixes. Well it oopses on writes everytime in Ubuntu 8.04 (Hardy). I'd planned on digging into it more before spending a bug report, but will send it tonight after getting to the affected machine. With 1 volume on 1 disk, 2 volumes raid1 on 2 disks, or with 2 volumes raid0 on 2 disks. something like: echo omg > /mnt/btrfs/file Would segfault, exit the current shell, and leave a nice stack trace in the kernel's ring buffer. The file gets created as 0 bytes. Unlinking the file works fine via rm, but any sort of write fails. Tried and reproduced the bug with stdout redirection, cp, and dd to a btrfs v0.14 volume. Will send the report later today. > > Until then, you can find download information on the important fixes so far: > > http://btrfs.wiki.kernel.org/index.php/Hot_Fixes > > > > -chris -- Jeff Schroeder Don't drink and derive, alcohol and analysis don't mix. http://www.digitalprognosis.com