From: Denys Fedoryschenko <denys@visp.net.lb>
To: Mason <chris.mason@oracle.com>
Cc: linux-ext4@vger.kernel.org, Josef Bacik <jbacik@redhat.com>
Subject: Re: btrfs BUG() & panic in __btrfs_reserve_extent(), 2.6.30-rc6
Date: Tue, 26 May 2009 13:05:42 +0300 [thread overview]
Message-ID: <200905261305.42204.denys@visp.net.lb> (raw)
In-Reply-To: <20090526100540.GB25835@think>
On Tuesday 26 May 2009 13:05:40 Mason wrote:
>
> Josef, it looks like the tracking code is losing some bytes ;) The
> total bytes in the space info doesn't add up to the other numbers in
> this data. It is worth mentioning that he's doing nodatacow.
>
> Definitely a btrfs bug, so we can trim ext4 off the list from now on,
> full quote below for Josef.
>
> -chris
>
I'm still keeping two partitions with btrfs with such failure(i have 9 HDD's,
others i use now ext4, they do job fine for my squid, except lacking dynamic
inode allocation), do you want me to keep partitions as is more time?
prev parent reply other threads:[~2009-05-26 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 10:47 btrfs BUG() & panic in __btrfs_reserve_extent(), 2.6.30-rc6 Denys Fedoryschenko
2009-05-26 10:05 ` Mason
2009-05-26 10:05 ` Denys Fedoryschenko [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=200905261305.42204.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=chris.mason@oracle.com \
--cc=jbacik@redhat.com \
--cc=linux-ext4@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