On Sun, 2021-06-20 at 08:50 +0800, Ed Greshko wrote:
> So, I've concluded that my NFS mounting issues are all related to
> running virtualization stuff.
I do run libvirtd (and virt-manager), though most of the time I have no
VMs active. I also don't have any NFS mounts (the VM I mostly use is
Wind
On 20/06/2021 17:32, Patrick O'Callaghan wrote:
On Sun, 2021-06-20 at 08:50 +0800, Ed Greshko wrote:
So, I've concluded that my NFS mounting issues are all related to
running virtualization stuff.
I do run libvirtd (and virt-manager), though most of the time I have no
VMs active. I also don't h
On Sun, 2021-06-20 at 17:53 +0800, Ed Greshko wrote:
> On 20/06/2021 17:32, Patrick O'Callaghan wrote:
> > On Sun, 2021-06-20 at 08:50 +0800, Ed Greshko wrote:
> > > So, I've concluded that my NFS mounting issues are all related to
> > > running virtualization stuff.
> > I do run libvirtd (and virt
On 20/06/2021 21:51, Patrick O'Callaghan wrote:
So I don't think libvirtd is the culprit in my case.
As long as you're issues allowed me to determine the cause of the issue I was
having, that's all that
matters. :-) :-)
--
Remind me to ignore comments which aren't germane to the thread.
On 19/06/2021 20:09, Patrick O'Callaghan wrote:
There are three files:
live-blame (output of systemd-analyze blame)
live-boot.svg (output of systemd-analyze plot)
live-journal (output of journal after logging into KDE)
Could you also upload the complete journal from start of boot until the log
On Sun, 2021-06-20 at 23:08 +0800, Ed Greshko wrote:
> On 19/06/2021 20:09, Patrick O'Callaghan wrote:
> > There are three files:
> >
> > live-blame (output of systemd-analyze blame)
> > live-boot.svg (output of systemd-analyze plot)
> > live-journal (output of journal after logging into KDE)
>
>
On 21/06/2021 00:16, Patrick O'Callaghan wrote:
On Sun, 2021-06-20 at 23:08 +0800, Ed Greshko wrote:
On 19/06/2021 20:09, Patrick O'Callaghan wrote:
There are three files:
live-blame (output of systemd-analyze blame)
live-boot.svg (output of systemd-analyze plot)
live-journal (output of journa
On Mon, 2021-06-21 at 02:41 +0800, Ed Greshko wrote:
> On 21/06/2021 00:16, Patrick O'Callaghan wrote:
> > On Sun, 2021-06-20 at 23:08 +0800, Ed Greshko wrote:
> > > On 19/06/2021 20:09, Patrick O'Callaghan wrote:
> > > > There are three files:
> > > >
> > > > live-blame (output of systemd-analyze
On 21/06/2021 02:50, Patrick O'Callaghan wrote:
On Mon, 2021-06-21 at 02:41 +0800, Ed Greshko wrote:
On 21/06/2021 00:16, Patrick O'Callaghan wrote:
On Sun, 2021-06-20 at 23:08 +0800, Ed Greshko wrote:
On 19/06/2021 20:09, Patrick O'Callaghan wrote:
There are three files:
live-blame (output
On 21/06/2021 02:50, Patrick O'Callaghan wrote:
On Mon, 2021-06-21 at 02:41 +0800, Ed Greshko wrote:
On 21/06/2021 00:16, Patrick O'Callaghan wrote:
On Sun, 2021-06-20 at 23:08 +0800, Ed Greshko wrote:
On 19/06/2021 20:09, Patrick O'Callaghan wrote:
There are three files:
live-blame (output
On Mon, 2021-06-21 at 03:48 +0800, Ed Greshko wrote:
> On 21/06/2021 02:50, Patrick O'Callaghan wrote:
> > On Mon, 2021-06-21 at 02:41 +0800, Ed Greshko wrote:
> > > On 21/06/2021 00:16, Patrick O'Callaghan wrote:
> > > > On Sun, 2021-06-20 at 23:08 +0800, Ed Greshko wrote:
> > > > > On 19/06/2021
On Mon, 2021-06-21 at 03:55 +0800, Ed Greshko wrote:
> On 21/06/2021 02:50, Patrick O'Callaghan wrote:
> > On Mon, 2021-06-21 at 02:41 +0800, Ed Greshko wrote:
> > > On 21/06/2021 00:16, Patrick O'Callaghan wrote:
> > > > On Sun, 2021-06-20 at 23:08 +0800, Ed Greshko wrote:
> > > > > On 19/06/2021
On 21/06/2021 05:48, Patrick O'Callaghan wrote:
$ systemd-analyze blame |grep dracut-initqueue.service
486ms dracut-initqueue.service
If I power on the dock on after startup is complete, one drive appears
immediately and the other takes 30 seconds or so, so the delay is not
being caused by th
On 21/06/2021 06:02, Ed Greshko wrote:
On 21/06/2021 05:48, Patrick O'Callaghan wrote:
$ systemd-analyze blame |grep dracut-initqueue.service
486ms dracut-initqueue.service
If I power on the dock on after startup is complete, one drive appears
immediately and the other takes 30 seconds or so
On 21/06/2021 06:02, Ed Greshko wrote:
On 21/06/2021 05:48, Patrick O'Callaghan wrote:
$ systemd-analyze blame |grep dracut-initqueue.service
486ms dracut-initqueue.service
If I power on the dock on after startup is complete, one drive appears
immediately and the other takes 30 seconds or so
On 6/20/21 3:48 PM, Patrick O'Callaghan wrote:
If I power on the dock on after startup is complete, one drive appears
immediately and the other takes 30 seconds or so, so the delay is not
being caused by the boot process itself. It must be the hardware (the
drive or the dock) taking that long for
On Sun, Jun 20, 2021 at 3:48 PM Patrick O'Callaghan
wrote:
>
> If I power on the dock on after startup is complete, one drive appears
> immediately and the other takes 30 seconds or so, so the delay is not
> being caused by the boot process itself. It must be the hardware (the
> drive or the dock)
Well it seems I am still subscribed to the list despite my having sent
unsubscribe mail. But anyway
I am subscribed at my other email address so I don;t care if this one works or
not. Time to change
providers I think. I'll try again to unsubscribe here.
___
One of the first things I did after installing F34 is disable swap-on-zram:
touch /etc/systemd/zram-generator.conf
and define a swap partition in fstab.
Bill
On 6/19/2021 12:45 AM, Stephen Morris wrote:
Hi,
I've noticed when trying remediate performance issues in F34 under a vm, that fedo
19 matches
Mail list logo
