Hi,
It took me a couple of days, because I needed to patch my kernel first
and then issue a rebalance, which ran for more than two days.
Nevertheless, the rebalance succeeded without any kernel BUG-messages,
so apparently your patch works!
I noticed that at first, the messages were like this:
On Wed, Jan 26, 2011 at 10:04:02AM +0100, Erik Logtenberg wrote:
Hi,
It took me a couple of days, because I needed to patch my kernel first
and then issue a rebalance, which ran for more than two days.
Nevertheless, the rebalance succeeded without any kernel BUG-messages,
so apparently your
[104178.827624] entry offset 8891924480, bytes 4096, bitmap yes
[104178.827626] block group has cluster?: no
[104178.827628] 0 blocks of free space at or bigger than bytes is
[104178.827631] block group 17213423616 has 5368709120 bytes, 5368709120
used 0 pinned 0 reserved
[104178.827634]
Yesterday I reported a similar problem in this mailing list, in the
thread version.
Running kernel 2.6.37 didn't show this error, but running kernel 2.6.38-
rc2 ended with errors.
Viele Gruesse!
Helmut
Ah, indeed, just like you I use 2.6.38-rc2. Or to be more precise:
please try patch attached below, Thanks.
---
diff --git a/fs/btrfs/relocation.c b/fs/btrfs/relocation.c
index b37d723..49d6b13 100644
--- a/fs/btrfs/relocation.c
+++ b/fs/btrfs/relocation.c
@@ -1158,6 +1158,7 @@ static int clone_backref_node(struct
btrfs_trans_handle *trans,
On Tue, Jan 18, 2011 at 9:22 PM, Erik Logtenberg e...@logtenberg.eu wrote:
On 01/18/2011 01:54 AM, Yan, Zheng wrote:
On Mon, Jan 17, 2011 at 10:14 PM, Erik Logtenberg e...@logtenberg.eu wrote:
Hi,
btrfs balance results in:
http://pastebin.com/v5j0809M
My system: fully up-to-date Fedora 14
Hi,
btrfs balance results in:
http://pastebin.com/v5j0809M
My system: fully up-to-date Fedora 14 with rawhide kernel to make btrfs
balance do useful stuff to my free space:
kernel-2.6.37-2.fc15.x86_64
btrfs-progs-0.19-12.fc14.x86_64
Filesystem had 0 bytes free, should be 45G, so on darklings
Hi,
Please find attached the error log, for future reference.
Forgot to mention:
I could still use the system after this error, so it was not a complete
fatal error in that regard. All active processes (mostly rsync) were
hanging in state D though, so I couldn't kill them anymore. Also the FS
Hi,
Additionally, I cannot mount the filesystem anymore. mount gives no
error messages but hangs in state D.
dmesg shows:
[ 422.323116] btrfs: use compression
Which is a good thing, but it doesn't do anything otherwise.
Thanks,
Erik.
On 01/17/2011 03:31 PM, Erik Logtenberg wrote:
Hi,
