Re: systemd-resolved floods the logs
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 DNS server 127.0.0.1. systemd-resolved[]: Using degraded feature set UDP instead of TCP for DNS server 127.0.0.1. This machine uses a VPN service that is always on. The file /etc/resolver.conf has just one line with the nameserver from the VPN provider. There's no problem in name resolution. Just the constant flooding of the logs. Late to the "party". I'm surprised that nobody asked "What kind of VPN are you using, and how did you configure it?". I'm running F33 and an OpenVPN connection using the now standard systemd-resolved. The OpenVPN connection was configured and is managed by the normal NetworkManager interface. When the VPN is up the contents of /etc/resolv.conf is not changed. It still has the systemd-resolved info. nameserver 127.0.0.53 options edns0 trust-ad The only thing "new" is in the output of resolvectl. Which now has this added to it. Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 25.0.0.1 DNS Servers: 25.0.0.1 DNS Domain: ~. So, to me, it seems odd that your /etc/resolv.conf should has been overwritten. --- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: systemd-resolved floods the logs
On 10/01/2021 11:04, Tim via users wrote: Ed Greshko: When I tested reverting to the previous behavior I simply started with an empty /etc/resolv.conf. No symlink. No selinux troubles. Everything just worked. Sam Varshavchik: Well, then how do the apps that need to talk to the DNS server find it? Maybe something in the glibc resolver knows to look in the alternate locations if /etc/resolv.conf is empty. Didn't he then go on to say that it was populated? (Letting the system create that configuration file.) Surely his subsequent tests were after that stage. To be specific, I created an empty file by "touch"ing it. Then, on rebott, since systemd-resolved is masked NM will populate the file as it always has. In other words, the previous method of doing name resolution is in effect/restored. But there are apps that read /etc/resolv.conf themselves (Firefox without a proxy?). They'll be hosed now. Surely apps that only look at that file once are always going to have failures. The file changes, things need to make allowances for that. I've no knowledge of firefox reading /etc/resolv.conf directly. As a matter of fact, I don't know of any reason firefox or any other app would do that. Now, since the previous behavior is restored they wouldn't be any less "hosed" than they were in F31. --- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: systemd-resolved floods the logs
On 10/01/2021 12:24, Sam Varshavchik wrote: Tim via users writes: Ed Greshko: >> When I tested reverting to the previous behavior I simply started >> with an empty /etc/resolv.conf. >> No symlink. No selinux troubles. Everything just worked. Sam Varshavchik: > Well, then how do the apps that need to talk to the DNS server find > it? Maybe something in the glibc resolver knows to look in the > alternate locations if /etc/resolv.conf is empty. Didn't he then go on to say that it was populated? (Letting the system create that configuration file.) Surely his subsequent tests were after that stage. Didn't see that until later. I'm not in the habit of posting things that I've done that don't work. :-) :-) 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 why NM would ever check if /etc/resolv.conf was a symlink. Where is that documented? --- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Limit size of a btrfs subvolume?
On Sat, Jan 9, 2021 at 7:25 PM Richard Shaw wrote: > > On Sat, Jan 9, 2021 at 6:25 PM Chris Murphy wrote: >> >> On Sat, Jan 9, 2021 at 6:11 AM Richard Shaw wrote: >> > >> > On Fri, Jan 8, 2021 at 10:12 AM Qiyu Yan wrote: >> >> >> >> I think https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-qgroup and >> >> https://btrfs.wiki.kernel.org/index.php/Quota_support are what you are >> >> looking for. >> > >> >> While the quota tracks space usage for a subvolume, once it's reached, >> writes fail. I'm not sure what interface exists for applications to >> learn whether a quota is set and what value. I've noticed that ext4, >> xfs, btrfs each have their own quota implementation and they're all >> kinda confusing in different ways. > > > Any way to achieve what I'm trying to do then? Maybe I should ask on the > MythTV mailing list. Yeah I'm not sure how its threshold works, how configurable it is. I think it's functionally the same thing as a separate partition if its threshold triggers once a used amount value has been reached, i.e. in its own directory. Or alternatively % used or % remaining. -- Chris Murphy ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: systemd-resolved floods the logs
Tim via users writes: Ed Greshko: >> When I tested reverting to the previous behavior I simply started >> with an empty /etc/resolv.conf. >> No symlink. No selinux troubles. Everything just worked. Sam Varshavchik: > Well, then how do the apps that need to talk to the DNS server find > it? Maybe something in the glibc resolver knows to look in the > alternate locations if /etc/resolv.conf is empty. Didn't he then go on to say that it was populated? (Letting the system create that configuration file.) Surely his subsequent tests were after that stage. Didn't see that until later. 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 Wonder how long this behavior will last. In the olden days I remember that kind of thing being a continual showstopper for a variety of things. Linux seemed to expect a continual and static internet connection and didn't handle dial-up (where you may not be connected most of the day, and your IP was dynamic). NTP, for instance, would try to start (and fail) if you weren't on-line, and never recover. I had to add a NTPd restart script to my connection script. Heck, even doing a graphical login to your computer could be painful if you didn't have an assigned IP. I remember those days and I've done some of these things myself, back then. In general, I would agree that having a transparent DNS proxy on localhost that simply forwards queries to the DNS-server-du-jour is a solid idea. Actually, it's a pretty clever hack. Except that, unsurprisingly, systemd keeps trying to find every possible way to mess it up. It completely fell apart on my server with a bind running on the same machine; systemd somehow found a way to frak it up and have its port 53 proxy start spewing SERVFAILs, for random domains, repeatedly to every client. But sending the same DNS query to bind's port 53 worked as usual. And this wasn't the case of it just sending a TEMPFAIL, or two, or three, but then getting its brains back together and resuming its proxying, quietly. I've tried, over the course of several minutes to see if its brain damage went away. It didn't, it just kept returning SERVFAILs to every query, meanwhile bind, on the same server, was like: "WHASSSUP" And this happened several times, over the course of a week, it wasn't just a one-time fluke. I defy anyone to come up with a logical explanation why systemd-resolved couldn't find bind running on the same machine, and for it to keel over. Not when the real server it always should be talking to is bind on the same machine. Then we have the other reports, with it going nuts with VPN connections, and spewing tons of garbage into syslog …oops, not syslog, journalctl. And then, after reading all those assurances how easy it is turn off this "feature" simply by repointing the /etc/resolv.conf symbolic link (or removing it) – only to discover that its tentacles still slither in, via nsswitch.conf? And then I also read all that jazz about some kind of a overengineered feature-discovery thing it does, for some unclear reason. I'd love to be educated with an explanation of what is that supposed to accomplish. But until then, I just don't trust it. You know, I would've kept quiet and minded my own business, accepting the fact that it's simply a matter of turning off the service, and repointing the symlink. Ok, that sucks but it's not a big deal, not the end of the world, I'll deal with it. But then, discovering this back-door invasion via nsswitch.conf – that ticked me off, somehow. Oh, and about those NTP restart things we were reminiscing about? That was a long time ago. The forward march of progress carries on. Everything seems to be working just fine now, in that area. My laptop keeps connecting and disconnecting from my wifi, as I put it to sleep, and wake up, all the time. chronie seems to be doing its job, keeping its clock in sync. So, I don't really see what this house of cards is giving me, except a headache. pgprVYETpBJ8K.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: systemd-resolved floods the logs
Ed Greshko: >> When I tested reverting to the previous behavior I simply started >> with an empty /etc/resolv.conf. >> No symlink. No selinux troubles. Everything just worked. Sam Varshavchik: > Well, then how do the apps that need to talk to the DNS server find > it? Maybe something in the glibc resolver knows to look in the > alternate locations if /etc/resolv.conf is empty. Didn't he then go on to say that it was populated? (Letting the system create that configuration file.) Surely his subsequent tests were after that stage. > But there are apps that read /etc/resolv.conf themselves (Firefox > without a proxy?). They'll be hosed now. Surely apps that only look at that file once are always going to have failures. The file changes, things need to make allowances for that. In the olden days I remember that kind of thing being a continual showstopper for a variety of things. Linux seemed to expect a continual and static internet connection and didn't handle dial-up (where you may not be connected most of the day, and your IP was dynamic). NTP, for instance, would try to start (and fail) if you weren't on-line, and never recover. I had to add a NTPd restart script to my connection script. Heck, even doing a graphical login to your computer could be painful if you didn't have an assigned IP. -- uname -rsvp Linux 3.10.0-1160.11.1.el7.x86_64 #1 SMP Fri Dec 18 16:34:56 UTC 2020 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Limit size of a btrfs subvolume?
On Sat, Jan 9, 2021 at 6:25 PM Chris Murphy wrote: > On Sat, Jan 9, 2021 at 6:11 AM Richard Shaw wrote: > > > > On Fri, Jan 8, 2021 at 10:12 AM Qiyu Yan > wrote: > >> > >> I think https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-qgroup > and https://btrfs.wiki.kernel.org/index.php/Quota_support are what you > are looking for. > > > > While the quota tracks space usage for a subvolume, once it's reached, > writes fail. I'm not sure what interface exists for applications to > learn whether a quota is set and what value. I've noticed that ext4, > xfs, btrfs each have their own quota implementation and they're all > kinda confusing in different ways. > Any way to achieve what I'm trying to do then? Maybe I should ask on the MythTV mailing list. Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: systemd-resolved floods the logs
Ed Greshko writes: When I tested reverting to the previous behavior I simply started with an empty /etc/resolv.conf. No symlink. No selinux troubles. Everything just worked. Well, then how do the apps that need to talk to the DNS server find it? Maybe something in the glibc resolver knows to look in the alternate locations if /etc/resolv.conf is empty. But there are apps that read /etc/resolv.conf themselves (Firefox without a proxy?). They'll be hosed now. Several years ago there was an issue with the network-online target being broken. Don't recall the exact technical cause, but the end result was that in some cases the network-online target was reached several seconds before, well, local network interfaces were actually configured. So, stuff that was configured to bind to a local IP address failed. It's beginning to come back to me – I think it's when you had static IP addresses, no dhcp, and I'm pretty sure that on one of my servers that are like that, and has sshd- server configured to be bound to an explicit local IP, and it still fails to start immediatley upon boot because the IP address is not configured, and then comes up only 42 seconds later when sshd-server tries again. Anyhow, I was able to implement a workaround by installing a service that was After=NetworkManager-wait-online.service Before=network-online.target and which ran a script that attempted to bind to the local IP address, every second, and terminated only when it succeeded. Well, so far I'm seeing these selinux denials myself, but don't seem to suffer any actual fallout from that. If I ever do, and none of the quick hacks I mentioned will help, I guess I have to write another service that uses inotify to monitor no-stub-resolv.conf, and update /etc/resolv.conf. Or maybe a one-shot service that fixes the selinux context on no-stub- resolv.conf That's life with systemd. pgpHLr9JrRhna.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: systemd-resolved floods the logs
On 10/01/2021 09:17, Ed Greshko wrote: On 10/01/2021 09:12, Sam Varshavchik wrote: Doug H. writes: > > Created bug 1913276 to fix no-stub-resolv.conf, the selinux policy needs to > be fixed. Thanks for opening that bug. Note that my outbound e-mail was being blocked by this. I am using postfix for outbound and the smtp alerts were triggering for each outbound e-mail attempt and were just queuing up until I did "sudo setenforce 0". I verified that new outbound mail was sent after that and I also "pushed" the queue with "postqueue -f" and watched the log as it drained. I might just switch back to the regular setup so that I can have selinux enabled while waiting for the fix to this. If you want to try to fiddle with this: I don't know how NetworkManager writes out no-stub-resolv.conf. If it creates something like 'no-stub-resolv.conf.tmp', writes it out, and then renames it to 'no-stub-resolv.conf' then finding a workaround would be tough. But, if NetworkManager just writes out a new no-stub-resolv.conf, then fiddling the selinux context on the file might make things work again. Until the next update to selinux-policy-targeted, I suppose, which runs a restorecon on the entire universe, and will reset it again. But at least this is something that will only need to be manually unfraked once in a while, until the policies get fixed (hopefully). There is supposedly a way to override local policies and provide site-specific overrides for selinux contexts. Or so I heard. But selinux is very poorly documented, and is very painful to work with, and I never investigated this in the past. When I tested reverting to the previous behavior I simply started with an empty /etc/resolv.conf. No symlink. No selinux troubles. Everything just worked. Just to be clear I simply did systemctl mask systemd-resolved.service rm /etc/resolv.conf touch /etc/resolv.conf systemctl reboot And now [egreshko@f33g ~]$ cat /etc/resolv.conf # Generated by NetworkManager search greshko.com nameserver 192.168.122.1 [egreshko@f33g ~]$ ls -Zl /etc/resolv.conf -rw-r--r--. 1 root root system_u:object_r:net_conf_t:s0 74 Jan 10 09:48 /etc/resolv.conf --- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Calibre on Fedora 33
On 1/9/21 8:05 PM, 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 anyone found a good workaround until DeDRM for Python3 is available? Calibre 4.23.0 is the version that is packaged and available from the Fedora 33 repositories. It runs under Python 2 so DeDRM work just fine with it. I've been using this for some time without issue. -- David King dave at daveking dot com ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Calibre on Fedora 33
On Sat, 9 Jan 2021 17:05:21 -0800 Clifford Snow wrote: > Has anyone found a good workaround until DeDRM for Python3 is available? Don't know about "good", but I have a dedicated fedora 32 virtual machine just for running calibre with inbox and outbox folders NFS mounted for feeding books in and getting modified books out. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: systemd-resolved floods the logs
On 10/01/2021 09:12, Sam Varshavchik wrote: Doug H. writes: > > Created bug 1913276 to fix no-stub-resolv.conf, the selinux policy needs to > be fixed. Thanks for opening that bug. Note that my outbound e-mail was being blocked by this. I am using postfix for outbound and the smtp alerts were triggering for each outbound e-mail attempt and were just queuing up until I did "sudo setenforce 0". I verified that new outbound mail was sent after that and I also "pushed" the queue with "postqueue -f" and watched the log as it drained. I might just switch back to the regular setup so that I can have selinux enabled while waiting for the fix to this. If you want to try to fiddle with this: I don't know how NetworkManager writes out no-stub-resolv.conf. If it creates something like 'no-stub-resolv.conf.tmp', writes it out, and then renames it to 'no-stub-resolv.conf' then finding a workaround would be tough. But, if NetworkManager just writes out a new no-stub-resolv.conf, then fiddling the selinux context on the file might make things work again. Until the next update to selinux-policy-targeted, I suppose, which runs a restorecon on the entire universe, and will reset it again. But at least this is something that will only need to be manually unfraked once in a while, until the policies get fixed (hopefully). There is supposedly a way to override local policies and provide site-specific overrides for selinux contexts. Or so I heard. But selinux is very poorly documented, and is very painful to work with, and I never investigated this in the past. When I tested reverting to the previous behavior I simply started with an empty /etc/resolv.conf. No symlink. No selinux troubles. Everything just worked. --- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: systemd-resolved floods the logs
Doug H. writes: > > Created bug 1913276 to fix no-stub-resolv.conf, the selinux policy needs to > be fixed. Thanks for opening that bug. Note that my outbound e-mail was being blocked by this. I am using postfix for outbound and the smtp alerts were triggering for each outbound e-mail attempt and were just queuing up until I did "sudo setenforce 0". I verified that new outbound mail was sent after that and I also "pushed" the queue with "postqueue -f" and watched the log as it drained. I might just switch back to the regular setup so that I can have selinux enabled while waiting for the fix to this. If you want to try to fiddle with this: I don't know how NetworkManager writes out no-stub-resolv.conf. If it creates something like 'no-stub- resolv.conf.tmp', writes it out, and then renames it to 'no-stub- resolv.conf' then finding a workaround would be tough. But, if NetworkManager just writes out a new no-stub-resolv.conf, then fiddling the selinux context on the file might make things work again. Until the next update to selinux-policy-targeted, I suppose, which runs a restorecon on the entire universe, and will reset it again. But at least this is something that will only need to be manually unfraked once in a while, until the policies get fixed (hopefully). There is supposedly a way to override local policies and provide site- specific overrides for selinux contexts. Or so I heard. But selinux is very poorly documented, and is very painful to work with, and I never investigated this in the past. pgpwIhTIerqgH.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Calibre on Fedora 33
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 anyone found a good workaround until DeDRM for Python3 is available? Happy New Year, Clifford -- @osm_washington www.snowandsnow.us OpenStreetMap: Maps with a human touch ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Compression on Btrfs
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 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) > > > > > > I then rebooted, but find: > > > > > > # btrfs prop get -t i /home compression > > > # > > > (i.e. no output) > > > > The 'btrfs property' method of setting compression per file, > > directory, or subvolume, sets an xattr. The mount option method does > > not. > > > > Also, the mount option is file system wide, it's not per subvolume. It > > just seems like it could be this way due to fstab and the subvol mount > > option (which is really just a bind mount behind the scenes). > > 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 implies no compression and no checksums. There's some advantages to compressing VM images, so it's a valid workflow. But there's enough tradeoffs that it's just way simpler to recommend nodatacow because it's the most compatible option. If you want to experiment with VM images with cow and compression enabled, the main two things: long standing O_DIRECT interaction bug/RFE, just avoid using any cache options that use O_DIRECT, e.g. use writeback or unsafe. [1] Learning a bit about fragmentation mitigation, which can be scheduled with a timer. [1] Unsafe means the guest file system is at significant risk of corruption if the host has a crash or power failure. Of course, I'm using Btrfs in the guest and on the host, and I'm always force quitting the guest with impunity. That's OK. But yanking the powercord on the host while the guest is writing is just asking for big trouble. Naturally, I do that often. And I don't recommend it unless, like me, you hate your data. But if you take precautions to avoid the host falling over, you can use unsafe. I'm pretty sure Fedora infrastructure is now using unsafe on some portion of the compose process to significantly boost performance. But also they have reliable hosts. -- Chris Murphy ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Limit size of a btrfs subvolume?
On Sat, Jan 9, 2021 at 6:11 AM Richard Shaw wrote: > > On Fri, Jan 8, 2021 at 10:12 AM Qiyu Yan wrote: >> >> I think https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-qgroup and >> https://btrfs.wiki.kernel.org/index.php/Quota_support are what you are >> looking for. > > > Thanks. That should do it! > While the quota tracks space usage for a subvolume, once it's reached, writes fail. I'm not sure what interface exists for applications to learn whether a quota is set and what value. I've noticed that ext4, xfs, btrfs each have their own quota implementation and they're all kinda confusing in different ways. -- Chris Murphy ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: BTRFS partition corrupted after deleting files in /home
On Sat, Jan 9, 2021 at 1:32 PM Sreyan Chakravarty wrote: > > If I don't have ECC does that mean I shouldn't use BTRFS ? 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 some clues in the systemd journal, before the file system went read only. What I can tell you is Btrfs doesn't have any known or suspected defects related to this kind of problem. It writes a superblock only once it has reason to believe the prior metadata writes were on stable media. There is also a write time tree checker designed to complain and go read only the moment there's an inconsistency when writing. This file system has a longer period of time of writes following the missing writes, which is also why the 'usebackup' root option didn't work. And the dropped writes also affect both copies of metadata. It's very unusual. Sreyan, is the drive that this file system is on the same drive as in this reported thread? https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/thread/DJWIOXUOSAAHAAXSUTKREV452QDCXV3D/#6UDYNNWOC23NJKSLMIABSAU4QFYANSRB -- Chris Murphy ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: BTRFS partition corrupted after deleting files in /home
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 were using ext4, the result wouldn't be that everything is fine, it's that you'd have corrupted data -- hopefully not important, but... you won't know. Now, I don't think btrfs's current state of "now your system won't boot and you need to be an expert to figure out what's going on" is ideal either, but it's a rare situation and recovery tools will improve. -- Matthew Miller Fedora Project Leader ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: BTRFS partition corrupted after deleting files in /home
On Sun, Jan 10, 2021 at 1:43 AM Gordon Messmer wrote: > > On 1/9/21 11:49 AM, Sreyan Chakravarty wrote: > > https://askubuntu.com/a/391178/628460 > > Will the above work in telling me if I have ECC RAM ? > > It should: > > # lshw -C memory > ... >*-memory > description: System Memory > physical id: 27 > slot: System board or motherboard > size: 32GiB > capabilities: ecc > configuration: errordetection=multi-bit-ecc > Nope. I don't have ECC RAM. Here is the output from `lshw -C memory` https://pastebin.com/raw/CUDp9dv9 And here is the output from `dmidecode --type memory` https://pastebin.com/raw/mWxaLUiA I see no ECC in any of them. If I don't have ECC does that mean I shouldn't use BTRFS ? -- Regards, Sreyan Chakravarty ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: BTRFS partition corrupted after deleting files in /home
On 1/9/21 11:49 AM, Sreyan Chakravarty wrote: https://askubuntu.com/a/391178/628460 Will the above work in telling me if I have ECC RAM ? It should: # lshw -C memory ... *-memory description: System Memory physical id: 27 slot: System board or motherboard size: 32GiB capabilities: ecc configuration: errordetection=multi-bit-ecc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: BTRFS partition corrupted after deleting files in /home
On Sun, Jan 10, 2021 at 12:22 AM Gordon Messmer wrote: > > On 1/9/21 9:09 AM, Sreyan Chakravarty wrote: > > I mean, this is the reason I keep complaining that BTRFS is not stable > > enough. > > ... > > So is this a problem of my machine/firmware or a problem in BTRFS itself ? > > > Since I haven't seen it asked yet: Does this system have ECC RAM? > > I don't want to shortcut the debugging process or suggest that I think > there are no bugs in btrfs, but one of the things we expected to happen > in the move to checksummed filesystems is that bits that flipped in > memory and then got written to disk were going to be discovered, where > older filesystems had no way to discover that. In those cases, bailing > out and informing you that corruption was found isn't a sign that the > system is "not stable enough", it's the desired outcome of actually > checking the results. https://askubuntu.com/a/391178/628460 Will the above work in telling me if I have ECC RAM ? -- Regards, Sreyan Chakravarty ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: BTRFS partition corrupted after deleting files in /home
On Sun, Jan 10, 2021 at 12:22 AM Gordon Messmer wrote: > > On 1/9/21 9:09 AM, Sreyan Chakravarty wrote: > > I mean, this is the reason I keep complaining that BTRFS is not stable > > enough. > > ... > > So is this a problem of my machine/firmware or a problem in BTRFS itself ? > > > Since I haven't seen it asked yet: Does this system have ECC RAM? > > I don't want to shortcut the debugging process or suggest that I think > there are no bugs in btrfs, but one of the things we expected to happen > in the move to checksummed filesystems is that bits that flipped in > memory and then got written to disk were going to be discovered, where > older filesystems had no way to discover that. In those cases, bailing > out and informing you that corruption was found isn't a sign that the > system is "not stable enough", it's the desired outcome of actually > checking the results. I don't know. How can I check from a live environment ? -- Regards, Sreyan Chakravarty ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: BTRFS partition corrupted after deleting files in /home
On 1/9/21 9:09 AM, Sreyan Chakravarty wrote: I mean, this is the reason I keep complaining that BTRFS is not stable enough. ... So is this a problem of my machine/firmware or a problem in BTRFS itself ? Since I haven't seen it asked yet: Does this system have ECC RAM? I don't want to shortcut the debugging process or suggest that I think there are no bugs in btrfs, but one of the things we expected to happen in the move to checksummed filesystems is that bits that flipped in memory and then got written to disk were going to be discovered, where older filesystems had no way to discover that. In those cases, bailing out and informing you that corruption was found isn't a sign that the system is "not stable enough", it's the desired outcome of actually checking the results. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: BTRFS partition corrupted after deleting files in /home
On Sat, Jan 9, 2021 at 11:10 PM Chris Murphy wrote: > > > > On Sat, Jan 9, 2021, 10:11 AM Sreyan Chakravarty wrote: >> >> On Sat, Jan 9, 2021 at 11:55 AM Chris Murphy wrote: >> > >> > 1. If you don't have a backup of important data, you should first use >> > 'btrfs restore' as I've described in previous emails. The fsck should >> > fix the problem, but there is a chance it makes things worse. No fsck >> > is guaranteed safe, because it's making changes to the file system. >> > >> >> Let me know if it makes more sense to use ddrescue instead of `btrfs >> restore`. > > > It's up to you. Both methods make a copy. Thats whats important. > > ddrescue will take longer and needs more space than just pulling out files > with btrfs restore. But if you're already familiar with ddrescue, that's an > advantage. > Going with ddrescue then. I will try the fix after the backup has been created. -- Regards, Sreyan Chakravarty ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: systemd-resolved floods the logs
On Wed, Jan 6, 2021, at 4:15 AM, Sam Varshavchik wrote: > Jerome Lille writes: > > > On Tue, 2021-01-05 at 18:10 -0500, Sam Varshavchik wrote: > > > Chris Murphy writes: > > > > > > > On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy > > > > wrote: > > > > > > > > > > Maybe this bug: > > > > > > > > https://github.com/systemd/systemd/issues/13432 > > > > > > "opened this issue on Aug 29, 2019" > > > > > > I would not expect this to be fixed any time soon. The only solution > > > is: > > > > > > systemctl stop systemd-resolved > > > systemctl disable systemd-resolved > > > rm -f /etc/resolv.conf > > > ln -s ../run/NetworkManager/no-stub-resolv.conf /etc/resolv.conf > > > > > > Hopefully, this fix will not stop working in the future, either. > > > > Thanks for the suggestion. With those changes the flooding of the logs > > went away. I can connect to the VPN and name resolution works. > > > > BUT, I got five different SELinux errors instead > > > > rpmdb was denied read access on resolv.conf > > rpcbind was denied name_bind access on port 64866 > > chronyd was denied getattr access on no-stub-resolv.conf > > gnome-shell was denied getattr access on no-stub-resolv.conf > > geoclue was denied getattr access on no-stub-resolv.conf > > Hm, looks like I've been getting some of these selinux errors too, but > haven't noticed it. > > Created bug 1913276 to fix no-stub-resolv.conf, the selinux policy needs to > be fixed. Thanks for opening that bug. Note that my outbound e-mail was being blocked by this. I am using postfix for outbound and the smtp alerts were triggering for each outbound e-mail attempt and were just queuing up until I did "sudo setenforce 0". I verified that new outbound mail was sent after that and I also "pushed" the queue with "postqueue -f" and watched the log as it drained. I might just switch back to the regular setup so that I can have selinux enabled while waiting for the fix to this. -- Doug Herr fedoraproject@wombatz.com ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: BTRFS partition corrupted after deleting files in /home
On Sat, Jan 9, 2021, 10:11 AM Sreyan Chakravarty wrote: > On Sat, Jan 9, 2021 at 11:55 AM Chris Murphy > wrote: > > > > 1. If you don't have a backup of important data, you should first use > > 'btrfs restore' as I've described in previous emails. The fsck should > > fix the problem, but there is a chance it makes things worse. No fsck > > is guaranteed safe, because it's making changes to the file system. > > > > Let me know if it makes more sense to use ddrescue instead of `btrfs > restore`. > It's up to you. Both methods make a copy. Thats whats important. ddrescue will take longer and needs more space than just pulling out files with btrfs restore. But if you're already familiar with ddrescue, that's an advantage. -- Chris Murphy > > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Fedora 34^^33 dns resolution problems? Preliminary report...
Francis, On Sat, 2021-01-09 at 16:23 +0100, francis.montag...@inria.fr wrote: > Hi. > On Fri, 08 Jan 2021 11:59:37 -0500 "Michael H. Warfield" wrote: > > My level of confidence is growing. I think you hit the nail square > > on > > the head. The nsswitch.com problem may have been the issue. But > > the > > cause may yet still be elsewhere. That file is owned by > > glibc. I'll > > file a bugzilla report against that package for f33. I've had many > > bugzilla reports under my belt. This one, against glib, will be a > > first for me. I'll give it another week. > I think that systemd-libs is a better choice than glibc because this > is him > that provides the libnss_resolve.so library. Good advice! Thank you! I will proceed down that path once I complete some more testing. Very good and much appreciated. > It's also its postinstall script that adds the resolve stanza in > /etc/nsswitch.conf.conf (indirectly in /etc/authselect/user- > nsswitch.conf). > -- > francis Regards, Mike -- Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 | m...@wittsend.com /\/\|=mhw=|\/\/ | (c) +1 678 463-0932 | http://www.wittsend.com/mhw/ ARIN whois: MHW9-ARIN | An optimist believes we live in the best of all PGP Key: 0xC0EB9675674627FF | possible worlds. A pessimist is sure of it! signature.asc Description: This is a digitally signed message part ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: BTRFS partition corrupted after deleting files in /home
On Sat, Jan 9, 2021 at 11:55 AM Chris Murphy wrote: > > 1. If you don't have a backup of important data, you should first use > 'btrfs restore' as I've described in previous emails. The fsck should > fix the problem, but there is a chance it makes things worse. No fsck > is guaranteed safe, because it's making changes to the file system. > Let me know if it makes more sense to use ddrescue instead of `btrfs restore`. In case of ddrescue we can run an fsck again since the filesystem can be restored back to a previous state. -- Regards, Sreyan Chakravarty ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: BTRFS partition corrupted after deleting files in /home
On Sat, Jan 9, 2021 at 7:34 AM Chris Murphy wrote: > > Strong likelihood that it can be fixed. But if the user data is > important we should do a btrfs restore first. That's a safe read-only > operation, does not change the file system like fsck which always has > risk. > Doesn't it make more sense to use ddrescue and make a filesystem image ? I mean if the fsck makes things worse then I can restore with ddrescue. Rather than taking a btrfs restore it's better I take an image right ? > > > Also is the fix for my particular problem being worked on by the devs > > at the particular moment ? > > Yes. > That's pretty cool. But what happens when BTRFS crashes on me again ? I mean, this is the reason I keep complaining that BTRFS is not stable enough. I can't keep complaining to you or the devs each time the filesystem crashes on me, can I. > > It's actually an unusual failure, so it is an edge case. I'm happy to > discuss this part later. Priority is to get your data backed up, and > fix the file system. > So is this a problem of my machine/firmware or a problem in BTRFS itself ? I am either extremely lucky or extremely unlucky if I have spotted an error in the filesystem itself. > > I saw your message today on IRC and replied about 15 seconds later but > didn't get a reply. Anyway, next email I'll write up a procedure. Apologies, I must have missed it. I think you message me around 1 in the morning in Indian Standard Time. -- Regards, Sreyan Chakravarty ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Fedora 34^^33 dns resolution problems? Preliminary report...
Hi. On Fri, 08 Jan 2021 11:59:37 -0500 "Michael H. Warfield" wrote: > My level of confidence is growing. I think you hit the nail square on > the head. The nsswitch.com problem may have been the issue. But the > cause may yet still be elsewhere. That file is owned by glibc. I'll > file a bugzilla report against that package for f33. I've had many > bugzilla reports under my belt. This one, against glib, will be a > first for me. I'll give it another week. I think that systemd-libs is a better choice than glibc because this is him that provides the libnss_resolve.so library. It's also its postinstall script that adds the resolve stanza in /etc/nsswitch.conf.conf (indirectly in /etc/authselect/user-nsswitch.conf). -- francis ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: KDE Plasma desktop won't load [SOLVED]
On 1/9/2021 4:54 AM, Ed Greshko wrote: On 09/01/2021 14:20, Temlakos wrote: On 1/9/2021 12:12 AM, Ed Greshko wrote: On 09/01/2021 12:53, Temlakos wrote: I sincerely hope someone can help me with this. This morning, KDE seems to have pushed Plasma 5.20--and the push was incomplete. After I had the bad sense to force some updates, I found that my SDDM theme was gone, and I couldn't log on. Sounds like you forced updates which had dependency issues. You could enable the updates-testing and update from there and this should resolve the issues you're seeing. You may choose to exclude some packages which aren't related to KDE plasma. I decided not to exclude anything. I've no issues. --- The key to getting good answers is to ask good questions. OK. Tell me again how to enable the updates-testing repo--except that I have to do it in a CLI. The GUI is not available to me until I solve this, but the CLI is. I see you were already given the answer. FWIW, it would seem the push has happened. Not sure if all mirrors are synced. But a system here was updated without enabling updates-testing. --- The key to getting good answers is to ask good questions. ___ Problem solved! GUI restored, with all my settings. Thank you. Ed, if this community ever starts an awards program for Best Volunteer Technical Supporter, you have my vote. I have found your advice consistently sound, and have fresh reason to appreciate it. Temlakos ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Limit size of a btrfs subvolume?
On Fri, Jan 8, 2021 at 10:12 AM Qiyu Yan wrote: > I think https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-qgroup and > https://btrfs.wiki.kernel.org/index.php/Quota_support are what you are > looking for. > Thanks. That should do it! Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Backing up Btrfs (was: btrfs or ext4)
On Sat, 2021-01-02 at 20:02 -0700, Chris Murphy wrote: > On Sat, Jan 2, 2021 at 6:27 AM Patrick O'Callaghan > wrote: > > > > Brief recap: I'm currently using BorgBackup, which among other things > > does compression and deduplication. I'm looking at the pros and cons of > > changing to Btrfs for backup (I already use it as my main fs). The > > backup drives are currently ext4 so would need to be converted. > > > > Now read on. > > > > Following Chris Murphy's suggestion, I looked at: > > > > https://fedoramagazine.org/btrfs-snapshots-backup-incremental/ > > > > My question is whether I can use compression and deduplication on the > > backup even if these have not been enabled on the original fs. My > > instinct is to say no, but I could be wrong. > > You can use compression and/or dedup on the backup even if they are > not used on the original file system (whether ext4 or Btrfs). Thanks for the clarification. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Compression on Btrfs
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-434e-b1c4-a9af2c810d56 /home btrfs > > subvol=home,discard=async,compress-force=zstd 0 0 > > > > (this is an SSD, hence the discard-async) > > > > I then rebooted, but find: > > > > # btrfs prop get -t i /home compression > > # > > (i.e. no output) > > The 'btrfs property' method of setting compression per file, > directory, or subvolume, sets an xattr. The mount option method does > not. > > Also, the mount option is file system wide, it's not per subvolume. It > just seems like it could be this way due to fstab and the subvol mount > option (which is really just a bind mount behind the scenes). Does this mean that my VM image subvolume is being included in the compression? If that's the case I'll cease and desist. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Compression on Btrfs
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? > > > > # compsize /home > > Processed 373221 files, 936531 regular extents (1058479 refs), 155981 > > inline. > > Type Perc Disk Usage Uncompressed Referenced > > TOTAL 98% 1.1T 1.1T 1.0T > > none 100% 1.1T 1.1T1013G > > zstd46% 17G 38G 40G > > And are there any new subvolumes you've created below /home? Those are > not subject to -r, the defragment will stop at subvolume boundaries. > Any VM images? If they're nodatacow, they won't compress. And quite a > lot of media files will not compress because they're already > compressed. There is one VM image in its own subvolume, as discussed recently. It's quite large (over 900GB) so that would affect the numbers. > Based on the above numbers I don't think this is as likely the issue > but mention it anyway: Are there any snapshots? 'btrfs fi defragment' > is not snapshot aware and will split up shared extents (makes them > exclusive again, increasing space consumption). No snapshots at the moment. From what you say it seems I would need to consider the tradeoff between using snapshots (e.g. for backup staging) and compression. > Lower priority, more experimentation, purely anecdotal: Using zstd:1 > might result in faster writes to SSD; where zstd:3 (same as zstd) > might result in faster overall writes to HDD. For Fedora 34 the > proposal is 'compress=zstd:1' and that's a bit conservative but also > is low hanging fruit with the biggest gain for the effort. Folks who > don't care about performance or want to use this for archives can > experiment with even higher values. I tend to use zstd:7 on backups. > It does get quite slow eventually, around 11 or higher. But zstd is > fairly invariant to compression level on reads, as in I doubt anyone > can tell a difference on read between a file that was compressed with > 1 vs 9, and maybe not notice 15 unless they were paying attention or > timing it. OK, thanks. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: KDE Plasma desktop won't load
On 09/01/2021 14:20, Temlakos wrote: On 1/9/2021 12:12 AM, Ed Greshko wrote: On 09/01/2021 12:53, Temlakos wrote: I sincerely hope someone can help me with this. This morning, KDE seems to have pushed Plasma 5.20--and the push was incomplete. After I had the bad sense to force some updates, I found that my SDDM theme was gone, and I couldn't log on. Sounds like you forced updates which had dependency issues. You could enable the updates-testing and update from there and this should resolve the issues you're seeing. You may choose to exclude some packages which aren't related to KDE plasma. I decided not to exclude anything. I've no issues. --- The key to getting good answers is to ask good questions. OK. Tell me again how to enable the updates-testing repo--except that I have to do it in a CLI. The GUI is not available to me until I solve this, but the CLI is. I see you were already given the answer. FWIW, it would seem the push has happened. Not sure if all mirrors are synced. But a system here was updated without enabling updates-testing. --- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
