On Thu, Dec 18, 2014 at 6:57 PM, Chris Murphy wrote:
> The other thing going on here is that every write is going to be COW,
> which isn't ideal for VM images.
Reminder goes here for setting xattr +C on VM images. You can't set it
after the fact though. Only at the time the file is created. A ref
The other thing going on here is that every write is going to be COW,
which isn't ideal for VM images. Another thing that I wonder is what
SSD this is and if it's supporting deterministic TRIM, since discard
is enabled. And I'm not sure that md by default is passing down trim
(?). This is on md rai
ssage-
From: linux-btrfs-ow...@vger.kernel.org
[mailto:linux-btrfs-ow...@vger.kernel.org] On Behalf Of Daniele Testa
Sent: Friday, 19 December 2014 4:33 AM
To: Hugo Mills; Daniele Testa; linux-btrfs@vger.kernel.org
Subject: Re: Extra info
I am running latest Debian stable. However, I used backpor
I am running latest Debian stable. However, I used backports to update
the kernel to 3.16.
root@s4 /opt/drives/ssd # uname -a
Linux s4.podnix.com 3.16.0-0.bpo.4-amd64 #1 SMP Debian
3.16.7-ckt2-1~bpo70+1 (2014-12-08) x86_64 GNU/Linux
root@s4 /opt/drives/ssd # btrfs --version
Btrfs v3.14.1
It stil
On Thu, Dec 18, 2014 at 11:02:34PM +0800, Daniele Testa wrote:
> Sorry, did not read the guidelines correctly. Here comes more info:
>
> root@s4 /opt/drives/ssd # uname -a
> Linux s4.podnix.com 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1 x86_64
> GNU/Linux
This is your problem. I think the di
Sorry, did not read the guidelines correctly. Here comes more info:
root@s4 /opt/drives/ssd # uname -a
Linux s4.podnix.com 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1 x86_64 GNU/Linux
root@s4 /opt/drives/ssd # btrfs --version
Btrfs Btrfs v0.19
root@s4 /opt/drives/ssd # btrfs fi show
Label: none
