public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Dan Merillat <dan.merillat@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs pull request
Date: Tue, 8 Nov 2011 15:17:53 -0500	[thread overview]
Message-ID: <20111108201753.GA4149@shiny> (raw)
In-Reply-To: <20111108182728.GR4954@shiny>

On Tue, Nov 08, 2011 at 01:27:28PM -0500, Chris Mason wrote:
> On Tue, Nov 08, 2011 at 12:55:40PM -0500, Dan Merillat wrote:
> > On Sun, Nov 6, 2011 at 1:38 PM, Chris Mason <chris.mason@oracle.com> wrote:
> > > Hi everyone,
> > >
> > > This pull request is pretty beefy, it ended up merging a number of long
> > > running projects and cleanup queues.  I've got btrfs patches in the new
> > > kernel.org btrfs repo.  There are two different branches with the same
> > > changes.  for-linus is against 3.1 and has also been tested against
> > > Linus' tree as of yesterday.
> > 
> > [91795.123286] device label ROOT devid 1 transid 3331 /dev/sdi2
> > [91795.123538] btrfs: open_ctree failed
> > 
> > FS created on 3.1 (x64), mounted once on 3.2-rc1 (i386), got that
> > whenI tried to mount on 3.1 (x64) again.  Format change in 3.2 or
> > 32/64 bit compatibility issues?
> 
> I'm trying to reproduce right now but I did many bounces between 3.2 and
> 3.1 code before releasing.  I didn't try jumping between 32 and 64 bit.
> 
> Are there any other messages in dmesg?  Could you please see what
> btrfs-debug-tree says?

Ok, so I spun the wheel going between 32 and 64 and 3.1 and 3.2.  I'm
not having trouble with basic tests.

So, we'll have to dig in and see why the open is failing.  btrfsck or
btrfs-debug-tree will help.

-chris


  reply	other threads:[~2011-11-08 20:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-06 18:38 [GIT PULL] Btrfs pull request Chris Mason
2011-11-06 19:29 ` Andrea Gelmini
2011-11-07  9:37   ` Arne Jansen
2011-11-07  9:49     ` Roman Mamedov
2011-11-07  9:57       ` Arne Jansen
2011-11-07 12:49       ` Andrea Gelmini
2011-11-07 12:42     ` Andrea Gelmini
2011-11-07 12:45       ` Arne Jansen
2011-11-07 12:50         ` Andrea Gelmini
2011-11-08  7:47           ` Arne Jansen
2011-11-09  1:07             ` Chris Mason
2011-11-09  7:48               ` Christoph Hellwig
2011-11-09  9:06                 ` Arne Jansen
2011-11-09 10:11                   ` Christoph Hellwig
2011-11-09 12:11                   ` Chris Mason
2011-11-09 10:29                 ` Jan Schmidt
2011-11-09 10:34                   ` Christoph Hellwig
2011-11-09 10:49                   ` Jan Schmidt
2011-11-09 12:12                   ` Chris Mason
2011-11-07  0:35 ` Chris Mason
2011-11-08 17:55 ` Dan Merillat
2011-11-08 18:27   ` Chris Mason
2011-11-08 20:17     ` Chris Mason [this message]
2011-11-09  6:53       ` Dan Merillat

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=20111108201753.GA4149@shiny \
    --to=chris.mason@oracle.com \
    --cc=dan.merillat@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox