Hey,
I am hoping you guys can shed some light on my issue. I know that it's
a common question that people see differences in the "disk used" when
running different calculations, but I still think that my issue is
weird.
root@s4 / # mount
/dev/md3 on /opt/drives/ssd type btrfs
(rw,noatime,compress
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
id it will corrupt the file if it
runs out of space.
Do you know how btrfs behaves if it runs out of space durring a
defrag? Any other ideas how I can solve it?
Regards,
Daniele
2014-12-18 23:35 GMT+08:00 Hugo Mills :
> On Thu, Dec 18, 2014 at 11:02:34PM +0800, Daniele Testa wrote:
>>
h the mount-flags if this
filesystem only contain big VM-files? Or is it not needed if I put +C
on the parent dir?
2014-12-20 2:53 GMT+08:00 Phillip Susi :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12/18/2014 9:59 AM, Daniele Testa wrote:
>> As seen above, I have a
But I read somewhere that compression should be turned off on mounts
that just store large VM-images. Is that wrong?
Btw, I am not pre-allocation space for the images. I use sparse files with:
dd if=/dev/zero of=drive.img bs=1 count=1 seek=300G
It creates the file in a few ms.
Is it better to us
osef Bacik :
> On 12/19/2014 04:10 PM, Josef Bacik wrote:
>>
>> On 12/18/2014 09:59 AM, Daniele Testa wrote:
>>>
>>> Hey,
>>>
>>> I am hoping you guys can shed some light on my issue. I know that it's
>>> a common question that people see di
