Re: BTRFS partition corrupted after deleting files in /home

2021-01-10 Thread Sreyan Chakravarty
On Sun, Jan 10, 2021 at 3:10 AM Chris Murphy wrote: > > No. And also, this problem is not related to a memory error. In this > case multiple writes from one commit are missing. They just didn't > make it to stable media. There isn't enough information to know why. > We might get lucky and find som

Re: BTRFS partition corrupted after deleting files in /home

2021-01-10 Thread Sreyan Chakravarty
On Sun, Jan 10, 2021 at 2:11 AM Matthew Miller wrote: > > On Sun, Jan 10, 2021 at 02:01:56AM +0530, Sreyan Chakravarty wrote: > > If I don't have ECC does that mean I shouldn't use BTRFS ? > > The chance of data corruption due to memory errors is rare, but it does > happen. If it happened and you

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: systemd-resolved floods the logs

2021-01-10 Thread Ed Greshko
On 11/01/2021 03:25, Jerome Lille wrote: On Sun, 2021-01-10 at 15:44 +0800, Ed Greshko wrote: On 06/01/2021 00:10, Jerome Lille wrote: I've just updated a desktop from Fedora 32 to 33 and after that the logs are flooded with the following message systemd-resolved[]: Using degraded feature set

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: systemd-resolved floods the logs

2021-01-10 Thread Jerome Lille
On Sun, 2021-01-10 at 15:44 +0800, Ed Greshko wrote: > On 06/01/2021 00:10, Jerome Lille wrote: > > I've just updated a desktop from Fedora 32 to 33 and after that the > > logs are flooded with the following message > > > > systemd-resolved[]: Using degraded feature set TCP instead of UDP > > for

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: systemd-resolved floods the logs

2021-01-10 Thread Sam Varshavchik
Ed Greshko writes: Networkmanager must be checking if /etc/resolv.conf is a symbolic link and only updating its own private resolver configs, otherwise it'll update them and /etc/resolv.conf I have no idea of what "private configs" you speak.  I also can't think of The configs in /var/run

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: systemd-resolved floods the logs

2021-01-10 Thread Ed Greshko
On 10/01/2021 14:50, Ed Greshko wrote: I also can't think of why NM would ever check if /etc/resolv.conf was a symlink. I actually meant to say there would be no need to check if systemd-resolved is masked. But, either way, that was not a very well thought out statement. --- The key to gettin

Re: Calibre on Fedora 33

2021-01-10 Thread Patrick O'Callaghan
On Sat, 2021-01-09 at 17:05 -0800, Clifford Snow wrote: > I'm wanting to run Calibre with DeDRM. Version 5 of Calibre was written for > Python3 while version 4 was written in Python2. DeDRM is only available for > Python2. Python3 support is being worked on but is still in development. > > Has any