linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jordan Windsor <jordanw2@gmail.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: Chris Samuel <chris@csamuel.org>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: WARNING: at fs/btrfs/free-space-cache.c:1887 after hard shutdown.
Date: Sat, 30 Jun 2012 01:45:09 +0930	[thread overview]
Message-ID: <CACCfv7ogX5Ha-5i2AoydRA8MYTTLrbdJOca70K1exCrr6NjNaw@mail.gmail.com> (raw)
In-Reply-To: <20120629130437.GB1834@localhost.localdomain>

On Fri, Jun 29, 2012 at 10:34 PM, Josef Bacik <jbacik@fusionio.com> wrote:
> On Fri, Jun 29, 2012 at 12:35:01AM -0600, Jordan Windsor wrote:
>> On Fri, Jun 29, 2012 at 3:09 PM, Chris Samuel <chris@csamuel.org> wrote:
>> > On 29/06/12 15:36, Jordan Windsor wrote:
>> >
>> >> I get the same problem with linux-mainline from AUR (latest)
>> >
>> > What does uname -a say ?
>> >
>> > cheers!
>> > Chris
>> > --
>> >  Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC
>> >
>> >
>>
>> Hello,
>> It says:
>> Linux archpc 3.5.0-1-mainline #1 SMP PREEMPT Fri Jun 29 02:09:43 CST
>> 2012 x86_64 GNU/Linux
>>
>
> Oh crap I'm sorry I thought this was in mainline already but it's not, it's in
> btrfs-next, pull down this git tree and you should be good to go
>
> git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git
>
> Thanks,
>
> Josef

Hello,
I got it working now thanks!

      reply	other threads:[~2012-06-29 16:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27  3:46 WARNING: at fs/btrfs/free-space-cache.c:1887 after hard shutdown Jordan Windsor
2012-06-27  7:56 ` Duncan
2012-06-27 13:48 ` Josef Bacik
2012-06-29  5:36   ` Jordan Windsor
2012-06-29  5:39     ` Chris Samuel
2012-06-29  6:35       ` Jordan Windsor
2012-06-29 13:04         ` Josef Bacik
2012-06-29 16:15           ` Jordan Windsor [this message]

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=CACCfv7ogX5Ha-5i2AoydRA8MYTTLrbdJOca70K1exCrr6NjNaw@mail.gmail.com \
    --to=jordanw2@gmail.com \
    --cc=chris@csamuel.org \
    --cc=jbacik@fusionio.com \
    --cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).