Re: Compression on Btrfs

2021-01-11 Thread Patrick O'Callaghan
On Sun, 2021-01-10 at 17:08 -0700, Chris Murphy wrote: > On Sun, Jan 10, 2021 at 4:09 PM Patrick O'Callaghan > wrote: > > > > > If you're using libvirt, creating a new pool on Btrfs will automatically > > > set +C attribute. > > > > It wasn't Btrfs at the time the image was created. > > Ahh got

Re: Compression on Btrfs

2021-01-10 Thread Chris Murphy
On Sun, Jan 10, 2021 at 4:39 PM Matthew Miller wrote: > > On Sun, Jan 10, 2021 at 11:09:31PM +, Patrick O'Callaghan wrote: > > > It's not possible to set this attribute once a file has data in it, it's > > > not retroactive. You'll need to duplicate the file, in that same > > > directory. > >

Re: Compression on Btrfs

2021-01-10 Thread Chris Murphy
On Sun, Jan 10, 2021 at 4:09 PM Patrick O'Callaghan wrote: > > > If you're using libvirt, creating a new pool on Btrfs will automatically > > set +C attribute. > > It wasn't Btrfs at the time the image was created. Ahh gotcha. A proper conversion guide should point out this gotcha. The work aroun

Re: Compression on Btrfs

2021-01-10 Thread Matthew Miller
On Sun, Jan 10, 2021 at 11:09:31PM +, Patrick O'Callaghan wrote: > > It's not possible to set this attribute once a file has data in it, it's > > not retroactive. You'll need to duplicate the file, in that same directory. > > Because the directory has the attribute now, the duplicate will inher

Re: Compression on Btrfs

2021-01-10 Thread Patrick O'Callaghan
On Sun, 2021-01-10 at 09:01 -0700, Chris Murphy wrote: > On Sun, Jan 10, 2021, 3:52 AM Patrick O'Callaghan > wrote: > > > On Sat, 2021-01-09 at 18:01 -0700, Chris Murphy wrote: > > > > Does this mean that my VM image subvolume is being included in the > > > > compression? If that's the case I'll

Re: Compression on Btrfs

2021-01-10 Thread Chris Murphy
On Sun, Jan 10, 2021, 3:52 AM Patrick O'Callaghan wrote: On Sat, 2021-01-09 at 18:01 -0700, Chris Murphy wrote: > > > Does this mean that my VM image subvolume is being included in the > > > compression? If that's the case I'll cease and desist. > > > > Did you set 'chattr +C' for nodatacow on t

Re: Compression on Btrfs

2021-01-10 Thread Patrick O'Callaghan
On Sat, 2021-01-09 at 18:01 -0700, Chris Murphy wrote: > > Does this mean that my VM image subvolume is being included in the > > compression? If that's the case I'll cease and desist. > > Did you set 'chattr +C' for nodatacow on the enclosing > directory/subvolume for the VM images? Nodatacow imp

Re: Compression on Btrfs

2021-01-09 Thread Chris Murphy
On Sat, Jan 9, 2021 at 4:15 AM Patrick O'Callaghan wrote: > > On Fri, 2021-01-08 at 00:03 -0700, Chris Murphy wrote: > > On Thu, Jan 7, 2021 at 5:52 AM Patrick O'Callaghan > > wrote: > > > > > > I did the following: > > > > > > # btrfs filesystem defragment -czstd -r -v /home > > > > > > and chan

Re: Compression on Btrfs

2021-01-09 Thread Patrick O'Callaghan
On Fri, 2021-01-08 at 00:03 -0700, Chris Murphy wrote: > On Thu, Jan 7, 2021 at 5:52 AM Patrick O'Callaghan > wrote: > > > > I did the following: > > > > # btrfs filesystem defragment -czstd -r -v /home > > > > and changed the fstab entry: > > > > # grep /home /etc/fstab > > UUID=8e1f7af4-c0bf

Re: Compression on Btrfs

2021-01-09 Thread Patrick O'Callaghan
On Fri, 2021-01-08 at 00:21 -0700, Chris Murphy wrote: > On Thu, Jan 7, 2021 at 7:52 AM Patrick O'Callaghan > wrote: > > > > On Thu, 2021-01-07 at 21:33 +0800, Qiyu Yan wrote: > > > > and the space usage doesn't seem to have changed. > > > Try using compsize to get space usage? > > > > # compsiz

Re: Compression on Btrfs

2021-01-07 Thread Chris Murphy
On Thu, Jan 7, 2021 at 7:52 AM Patrick O'Callaghan wrote: > > On Thu, 2021-01-07 at 21:33 +0800, Qiyu Yan wrote: > > > and the space usage doesn't seem to have changed. > > Try using compsize to get space usage? > > # compsize /home > Processed 373221 files, 936531 regular extents (1058479 refs),

Re: Compression on Btrfs

2021-01-07 Thread Chris Murphy
On Thu, Jan 7, 2021 at 5:52 AM Patrick O'Callaghan wrote: > > I did the following: > > # btrfs filesystem defragment -czstd -r -v /home > > and changed the fstab entry: > > # grep /home /etc/fstab > UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56 /home btrfs > subvol=home,discard=as

Re: Compression on Btrfs

2021-01-07 Thread Patrick O'Callaghan
On Thu, 2021-01-07 at 21:33 +0800, Qiyu Yan wrote: > > and the space usage doesn't seem to have changed. > Try using compsize to get space usage? # compsize /home Processed 373221 files, 936531 regular extents (1058479 refs), 155981 inline. Type Perc Disk Usage Uncompressed Referenced

Re: Compression on Btrfs

2021-01-07 Thread Qiyu Yan
> and the space usage doesn't seem to have changed. Try using compsize to get space usage? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fe

Compression on Btrfs

2021-01-07 Thread Patrick O'Callaghan
I did the following: # btrfs filesystem defragment -czstd -r -v /home and changed the fstab entry: # grep /home /etc/fstab UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56 /home btrfs subvol=home,discard=async,compress-force=zstd 0 0 (this is an SSD, hence the discard-async)