On 07/18/2011 12:53 PM, Wang Sheng-Hui wrote:
The patch is against 3.0-rc7 kernel.
From d22497ac8c5dd55a2ef9a47de5f2ddee55f8ec50 Mon Sep 17 00:00:00 2001
From: Wang Sheng-Hui
Date: Sun, 17 Jul 2011 21:45:01 -0500
Subject: [PATCH 3.0-rc7] btrfs: Update git repository links for btrfs utilities
The patch is against 3.0-rc7 kernel.
>From d22497ac8c5dd55a2ef9a47de5f2ddee55f8ec50 Mon Sep 17 00:00:00 2001
From: Wang Sheng-Hui
Date: Sun, 17 Jul 2011 21:45:01 -0500
Subject: [PATCH 3.0-rc7] btrfs: Update git repository links for btrfs utilities
in Documentation/filesystems/btrfs.txt
git repo
On 07/16/2011 02:29 AM, Josef Bacik wrote:
> Currently we reserve enough space to COW an entirely full btree for every
> extent
> we have reserved for an inode. This _sucks_, because you only need to COW
> once,
> and then everybody else is ok. Unfortunately we don't know we'll all be able
> t
Jan Schubert gmx.li> writes:
> Please find some data and log below. Is there any chance to fix this?
After playing around (incl. deleting the log) I get the strong feeling
it has something todo with compression=lzo. Dunno why it started suddenly
but I disabled compression and did reinstall everyt
2011-07-16 13:12:10 +0100, Stephane Chazelas:
> Still on my btrfs-based backup system. I still see one BUG()
> reached in btrfs-fixup per boot time, no memory exhaustion
> anymore. There is now however something new: write performance
> is down to a few bytes per second.
[...]
The condition that w
