Re: trimming rbd image does not reclaim free space

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, May 12, 2015 at 11:09 AM, Wido den Hollander <wido@xxxxxxxx> wrote:
> On 05/12/2015 09:48 AM, Edgaras Lukoševičius wrote:
>> Resending commands I’m using to everyone.
>>
>> # rbd-fuse -p pool -r image /mnt/trim/
>> # losetup /dev/loop0 /mnt/trim/image
>> # kpartx -av /dev/loop0
>> # mount /dev/mapper/loop0p1 /mnt/fstrim/
>> # fstrim -v /mnt/fstrim/
>> /mnt/fstrim/: 1.1 TiB (1167710830592 bytes) trimmed
>>
>> I don’t use qemu, kvm.
>>
>
> I think that kernel 3.10 doesn't support TRIM yet. Afaik it was
> implemented in kernel 3.18 of 3.19
>
> Wido
>
>> Anyone can help with this?

This is rbd-fuse, not kernel client.  I wanted to take a look, but
haven't had a chance yet.  rbd-fuse probably just doesn't support
trimming.  AFAIR discard requests to a loop device are translated into
hole punches on the underlying file, and rbd-fuse doesn't seem to
provide ->fallocate() callback.  It wouldn't be hard to add though,
I can take a shot at it later.

Thanks,

                Ilya
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux