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
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
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
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
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?
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
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
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
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
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
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
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
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
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?
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
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
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
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,
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
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:
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
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
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
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
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:
> > > >
> > > >
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
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.
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,
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
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
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
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
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
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
> >
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?
> >
> > #
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
36 matches
Mail list logo
