All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Alexander Skwar <a@skwar.me>
Cc: Josef Bacik <JBacik@fusionio.com>,
	"linux-btrfs@vger.kernel.org" <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, 8 May 2013 16:47:58 -0400	[thread overview]
Message-ID: <20130508204758.GU12414@localhost.localdomain> (raw)
In-Reply-To: <CADn-QaPh9EZjnbr9HoRKTMi8OUgnvfRdD7riEDZ0hpkcNRN93Q@mail.gmail.com>

On Wed, May 08, 2013 at 11:34:40AM -0600, Alexander Skwar wrote:
> Hello Josef
> 
> Did you have a chance to look at that image? Did you find anything?
> 
> Or should I simply create a new filesystem and forget about the issue?
> 

So the file system isn't corrupt, you just got a giant block group for some
reason.  I've sent a patch to remove the WARN_ON() so that won't bother you
anymore.  You should probably rebalance to try and trim that block group down to
a reasonable size, but other than that your fs is a-ok.  Thanks,

Josef

  parent reply	other threads:[~2013-05-08 20:48 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
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 [this message]
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=20130508204758.GU12414@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=a@skwar.me \
    --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 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.