On 02/12/11 15:14, krz...@gmail.com wrote:
I've upgraded to newest kernel 3.1.2 but problem is not fixed.
As btrfs is an experimental filesystem I don't believe that fixes are
backported to those stable releases, they only go into Linus's tree for
his next release (3.2 in this case). So I'm
On 24/11/11 12:00, Chris Samuel wrote:
You're running quite an old kernel btrfs wise - it would be
very interesting to see if you have the same issue with Linus's
current git version (which has the latest btrfs code) or
wait for 3.2-rc3.
3.2-rc3 is now out, Linus is after testers around the
I've been using btrfs for two months now. Every day between 02:00 and
08:00 I rsync some 300GB data (milions of files) to btrfs device and
then make snapshot. Next day i rsync again 300GG little changed (rsync
in place). First days it worked perfectly. Then loadavg (sys load)
started to rise. Now,
Yes, yesterday I've umouted partition and re-mounted it. Nothing has
changed this night.
You can look at my load graphs here:
http://img42.imageshack.us/img42/4661/33737291.png
http://img210.imageshack.us/img210/2742/46527625.png
On the second one blue is SYS load. I bet you can reasily spot
On 11/23/2011 9:43 AM, krz...@gmail.com wrote:
What all those btrfs benchmark does not tell you that its performance
decreases (sys load increases) with growing size of btree. Creating
btrfs filesystem is instantaneous because initial tree is just
nothing...
While something is clearly wrong,
I've rebooted server and run backup to btrfs partition again. It seems
that problem is gone, high sys load does not occur now. So it is some
bug in btrfs... Before reboot server had 30 days uptime so its really
not much.
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
On Thu, Nov 24, 2011 at 8:00 AM, Chris Samuel ch...@csamuel.org wrote:
Another possibility I *think* is that you could try 3.1 with
Chris Mason's for-linus git branch pulled into it. Hopefully
someone who knows the procedure better than I can correct me
on this! :-)
My method is:
- use 3.1.1
