Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Jon Nelson <jnelson@jamponi.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: WARNING: at fs/btrfs/free-space-cache.c:921 __btrfs_write_out_cache+0x6b9/0x9a0 [btrfs]()
Date: Wed, 1 May 2013 19:19:54 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130501T211832-352@post.gmane.org> (raw)
In-Reply-To: 20130501185701.GA12414@localhost.localdomain

Josef Bacik <jbacik <at> fusionio.com> writes:

..
> Ok well that's not good, I'm not sure how you got a 156 gigabyte block 
group,
> but thats why that warning is going off.  Can you pull btrfs-image down 
from
> here
> 
> git://github.com/josefbacik/btrfs-progs.git

What is the difference between this git repo and the one at 
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git

I notice that the former has commits the latter doesn't. Is the latter the 
analogue to btrfs-next ? 




  reply	other threads:[~2013-05-01 19:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30  6:37 WARNING: at fs/btrfs/free-space-cache.c:921 __btrfs_write_out_cache+0x6b9/0x9a0 [btrfs]() Alexander Skwar
2013-04-30  6:55 ` Helmut Hullen
2013-04-30  9:41   ` Hugo Mills
2013-04-30 11:51     ` Alexander Skwar
2013-04-30 13:58       ` Josef Bacik
2013-04-30 14:33         ` Alexander Skwar
2013-04-30 17:53           ` Josef Bacik
2013-05-01  6:39             ` Alexander Skwar
2013-05-01 18:57               ` Josef Bacik
2013-05-01 19:19                 ` Jon Nelson [this message]
2013-05-01 20:08                 ` Alexander Skwar
     [not found]                   ` <CADn-QaPh9EZjnbr9HoRKTMi8OUgnvfRdD7riEDZ0hpkcNRN93Q@mail.gmail.com>
2013-05-08 20:40                     ` Josef Bacik
2013-05-08 20:47                     ` Josef Bacik
2013-05-13  8:33                       ` Alexander Skwar

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=loom.20130501T211832-352@post.gmane.org \
    --to=jnelson@jamponi.net \
    --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