From: Chris Mason <chris.mason@oracle.com>
To: Alex Chiang <achiang@hp.com>
Cc: David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
btrfs-devel@oss.oracle.com
Subject: Re: [ANNOUNCE] Btrfs v0.13
Date: Tue, 1 Apr 2008 09:38:26 -0400 [thread overview]
Message-ID: <200804010938.26762.chris.mason@oracle.com> (raw)
In-Reply-To: <20080401004053.GF2362@ldl.fc.hp.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Chris Mason <chris.mason@oracle.com>
To: Alex Chiang <achiang@hp.com>
Cc: linux-fsdevel@vger.kernel.org, btrfs-devel@oss.oracle.com,
David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Btrfs v0.13
Date: Tue, 1 Apr 2008 09:38:26 -0400 [thread overview]
Message-ID: <200804010938.26762.chris.mason@oracle.com> (raw)
In-Reply-To: <20080401004053.GF2362@ldl.fc.hp.com>
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
next prev parent reply other threads:[~2008-04-01 13:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 21:09 [ANNOUNCE] Btrfs v0.13 Chris Mason
2008-02-21 21:12 ` Chris Mason
2008-03-31 20:26 ` Alex Chiang
2008-03-31 20:35 ` Alex Chiang
2008-03-31 20:45 ` David Miller
2008-03-31 22:43 ` Alex Chiang
2008-03-31 23:25 ` Alex Chiang
2008-04-01 15:58 ` Chris Mason
2008-03-31 22:47 ` Alex Chiang
2008-04-01 0:40 ` Alex Chiang
2008-04-01 13:38 ` Chris Mason [this message]
2008-04-01 13:38 ` Chris Mason
2008-03-31 20:52 ` Chris Mason
2008-03-31 21:02 ` Alex Chiang
2008-03-31 20:28 ` [PATCH 1/2] btrfs-progs: Fix printf format casting errors Alex Chiang
2008-03-31 20:29 ` [PATCH 2/2] btrfs-progs: Stop stomping on 'name' input parameter Alex Chiang
2008-04-01 23:28 ` [ANNOUNCE] Btrfs v0.13 Badari Pulavarty
2008-04-01 23:33 ` Badari Pulavarty
2008-04-03 16:51 ` [PATCH] btrfs - replace div_long_long_rem() Badari Pulavarty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200804010938.26762.chris.mason@oracle.com \
--to=chris.mason@oracle.com \
--cc=achiang@hp.com \
--cc=btrfs-devel@oss.oracle.com \
--cc=davem@davemloft.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.