From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: [ANNOUNCE] Btrfs v0.13 Date: Tue, 1 Apr 2008 09:38:26 -0400 Message-ID: <200804010938.26762.chris.mason@oracle.com> References: <200802211609.50563.chris.mason@oracle.com> <20080331224710.GC2362@ldl.fc.hp.com> <20080401004053.GF2362@ldl.fc.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, btrfs-devel@oss.oracle.com, David Miller , linux-kernel@vger.kernel.org To: Alex Chiang Return-path: In-Reply-To: <20080401004053.GF2362@ldl.fc.hp.com> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: btrfs-devel-bounces@oss.oracle.com Errors-To: btrfs-devel-bounces@oss.oracle.com List-Id: linux-fsdevel.vger.kernel.org On Monday 31 March 2008, Alex Chiang wrote: > > So, using the patch from my last mail, I created a btrfs, but was > > unable to mount it... > > At some point, I got confused which btrfs trees I was working in, > and gotten switched up to where I had insmod'ed btrfs v0.13, but > was trying to mount a filesystem created with > btrfs-progs-unstable. Of course, I got a version mismatch when it > went to check for BTRFS_MAGIC and mount failed. > > Moving to btrfs-unstable allowed me to mount the filesystem. This is a very easy mistake to make, a long standing TODO is to make sane format revision fields. I'll include this in the multi-device code. Thanks for all the patches so far. -chris