On 22/06/2021 11:41, Gordon Messmer wrote:
On 6/21/21 6:17 AM, Robert McBroom via users wrote:
@RobertPC ~]# mount -v -t nfs [fd2e:cb3b:f005::ec1]:/mnt/HD/HD_a2/mcstuffy
/mnt/mcstuffy
mount.nfs: timeout set for Mon Jun 21 06:42:25 2021
mount.nfs: trying text-based options
'vers=4.2,addr=fd2e:c
On 22/06/2021 11:41, Gordon Messmer wrote:
On 6/21/21 6:17 AM, Robert McBroom via users wrote:
@RobertPC ~]# mount -v -t nfs [fd2e:cb3b:f005::ec1]:/mnt/HD/HD_a2/mcstuffy
/mnt/mcstuffy
mount.nfs: timeout set for Mon Jun 21 06:42:25 2021
mount.nfs: trying text-based options
'vers=4.2,addr=fd2e:c
On 6/21/21 6:17 AM, Robert McBroom via users wrote:
@RobertPC ~]# mount -v -t nfs
[fd2e:cb3b:f005::ec1]:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy
mount.nfs: timeout set for Mon Jun 21 06:42:25 2021
mount.nfs: trying text-based options
'vers=4.2,addr=fd2e:cb3b:f005::ec1,clientaddr=fd2e:cb3b:f005::ec1
On 2021-06-21 4:29 p.m., Stephen Morris wrote:
On 20/6/21 02:22, Ed Greshko wrote:
On 19/06/2021 21:44, Stephen Morris wrote:
My system has been upgraded from versions without ZRAM. That is the
reason my system has a defined swap
partition on disk.
I don't see the connection between Video Me
On 22/06/2021 05:41, Patrick O'Callaghan wrote:
On Mon, 2021-06-21 at 21:18 +0800, Ed Greshko wrote:
On 21/06/2021 20:31, Patrick O'Callaghan wrote:
On Mon, 2021-06-21 at 20:02 +0800, Ed Greshko wrote:
I thought I mentioned they should have been taken at the same time.
journal starts at
Jun
On 22/06/2021 07:34, Tom Horsley wrote:
On Tue, 22 Jun 2021 07:25:23 +0800
Ed Greshko wrote:
Could you define a bit more what you mean by "name resolution"? Or are you
thinking about
the Stateless IP assignment I mention in a different reply?
I have no idea :-). Maybe what I read about had s
On Tue, 22 Jun 2021 07:25:23 +0800
Ed Greshko wrote:
> Could you define a bit more what you mean by "name resolution"? Or are you
> thinking about
> the Stateless IP assignment I mention in a different reply?
I have no idea :-). Maybe what I read about had something to do with mdns
providing sy
On 20/6/21 02:22, Ed Greshko wrote:
On 19/06/2021 21:44, Stephen Morris wrote:
On 19/6/21 15:31, Ed Greshko wrote:
On 19/06/2021 12:45, Stephen Morris wrote:
Hi,
I've noticed when trying remediate performance issues in F34
under a vm, that fedora does not have a swap specification in fsta
On 22/06/2021 00:48, Tom Horsley wrote:
On Tue, 22 Jun 2021 00:37:56 +0800
Ed Greshko wrote:
Oh, I forgot to mention that your IPv6 addresses appear to be Dynamically
assigned IP
addresses. Meaning they are not "fixed" and may change. Not the best for uses
in a
client/server environment.
I
On Mon, 2021-06-21 at 11:47 -0600, Joe Zeff wrote:
> On 6/21/21 3:14 AM, Patrick O'Callaghan wrote:
> > Yes, that's been established (strictly, I haven't bothered swapping
> > the
> > drives in the dock to see what happens, but it's immaterial). Again,
> > the issue is not that one drive takes time
On Mon, 2021-06-21 at 13:13 -0600, Chris Murphy wrote:
> On Mon, Jun 21, 2021 at 10:58 AM Chris Murphy
>
> wrote:
> >
> > Jun 19 12:47:12 fedora kernel: sd 6:0:0:1: tag#2
> > uas_eh_abort_handler
> > 0 uas-tag 2 inflight: IN
> > Jun 19 12:47:12 fedora kernel: sd 6:0:0:1: tag#2 CDB: Mode Sense(6)
On Saturday, June 19, 2021 2:38:02 PM WEST Patrick Dupre wrote:
> Hello,
>
> There is a new version of gsl (2.7).
> http://www.gnu.org/software/gsl/
>
> What are the plans to have it available in fc34?
Historically all the new releases of gsl where never released in stable
distributions.
I am
On Mon, 2021-06-21 at 21:18 +0800, Ed Greshko wrote:
> On 21/06/2021 20:31, Patrick O'Callaghan wrote:
> > On Mon, 2021-06-21 at 20:02 +0800, Ed Greshko wrote:
> > > On 21/06/2021 19:48, Patrick O'Callaghan wrote:
> > > > To avoid ambiguity, maybe you should tell me the journal
> > > > options
> >
On Mon, Jun 21, 2021 at 7:18 AM Tim Evans wrote:
>
> $ uname -a
> Linux harrier 5.12.11-300.fc34.x86_64 #1 SMP Wed Jun 16 15:47:58 UTC
> 2021 x86_64 x86_64 x86_64 GNU/Linux
>
> As I sit here, my Lenovo T530 laptop is reporting packagekitd is taking
> anywhere from 20 to 40 percent of CPU, per 'top
On Mon, Jun 21, 2021 at 1:25 PM Samuel Sieb wrote:
>
> On 2021-06-21 1:05 a.m., Bill Shirley wrote:
> > The server is running on Raid-1 SSDs with 64GB of RAM
> >
> > Bill
> >
> > On 6/21/2021 3:41 AM, Samuel Sieb wrote:
> >> On 6/20/21 7:25 PM, Bill Shirley wrote:
> >>> One of the first things I d
On Mon, Jun 21, 2021 at 10:51 AM Barry Scott wrote:
>
> The SSDs are a lot slower than compressing a page into RAM.
>
> There was extensive discussion on the Fedora Devel list when this change was
> proposed.
>
> Personally I was convinced that this change is an improvement for any system
> that
On 2021-06-21 1:05 a.m., Bill Shirley wrote:
The server is running on Raid-1 SSDs with 64GB of RAM
Bill
On 6/21/2021 3:41 AM, Samuel Sieb wrote:
On 6/20/21 7:25 PM, Bill Shirley wrote:
One of the first things I did after installing F34 is disable
swap-on-zram:
touch /etc/systemd/zram-gene
On Mon, Jun 21, 2021 at 10:58 AM Chris Murphy wrote:
>
> Jun 19 12:47:12 fedora kernel: sd 6:0:0:1: tag#2 uas_eh_abort_handler
> 0 uas-tag 2 inflight: IN
> Jun 19 12:47:12 fedora kernel: sd 6:0:0:1: tag#2 CDB: Mode Sense(6) 1a
> 00 08 00 18 00
Yeah and in the install-boot log it happens again:
On 22/06/2021 02:36, Robert McBroom via users wrote:
On 6/21/21 12:37 PM, Ed Greshko wrote:
On 22/06/2021 00:35, Ed Greshko wrote:
On 21/06/2021 22:47, Robert McBroom via users wrote:
Web interface. It shows
IPv6 IP Address
fe80::200:1eb5:75df:b84:98d1 , 2600:1702:4860:9dd0:21d:60ff:fe35:b81
On 6/21/21 12:37 PM, Ed Greshko wrote:
On 22/06/2021 00:35, Ed Greshko wrote:
On 21/06/2021 22:47, Robert McBroom via users wrote:
Web interface. It shows
IPv6 IP Address
fe80::200:1eb5:75df:b84:98d1 ,
2600:1702:4860:9dd0:21d:60ff:fe35:b813/64
exports configuration is "*"
Then the IPv6 a
On 6/21/21 3:14 AM, Patrick O'Callaghan wrote:
Yes, that's been established (strictly, I haven't bothered swapping the
drives in the dock to see what happens, but it's immaterial). Again,
the issue is not that one drive takes time to spin up, but that the
system start-up waits for it when it does
On 6/21/21 8:17 AM, Robert McBroom via users wrote:
Trying to connect to NAS with nfs using the ipv6 addressing.
@RobertPC ~]#ping fd2e:cb3b:f005::ec1
PING fd2e:cb3b:f005::ec1(fd2e:cb3b:f005::ec1) 56 data bytes
64 bytes from fd2e:cb3b:f005::ec1: icmp_seq=1 ttl=64 time=0.120 ms
64 bytes from fd2e
> On 21 Jun 2021, at 17:48, Tom Horsley wrote:
>
> On Tue, 22 Jun 2021 00:37:56 +0800
> Ed Greshko wrote:
>
>> Oh, I forgot to mention that your IPv6 addresses appear to be Dynamically
>> assigned IP
>> addresses. Meaning they are not "fixed" and may change. Not the best for
>> uses in a
>
On Mon, Jun 21, 2021 at 3:20 AM Patrick O'Callaghan
wrote:
>
> The logs are now publicly visible at:
> https://drive.google.com/drive/folders/1nGwVkeTJh5hz4dYRBD7Ikpx6q4MaPki9?usp=sharing
From the live boot (the least complicated one to look at for
starters), there is an anomaly:
Jun 19 08:46:41
> On 21 Jun 2021, at 14:18, Tim Evans wrote:
>
> $ uname -a
> Linux harrier 5.12.11-300.fc34.x86_64 #1 SMP Wed Jun 16 15:47:58 UTC 2021
> x86_64 x86_64 x86_64 GNU/Linux
>
> As I sit here, my Lenovo T530 laptop is reporting packagekitd is taking
> anywhere from 20 to 40 percent of CPU, per 't
The SSDs are a lot slower than compressing a page into RAM.
There was extensive discussion on the Fedora Devel list when this change was
proposed.
Personally I was convinced that this change is an improvement for any system
that is under
memory pressure. I'm not going to try to recall the discu
On Tue, 22 Jun 2021 00:37:56 +0800
Ed Greshko wrote:
> Oh, I forgot to mention that your IPv6 addresses appear to be Dynamically
> assigned IP
> addresses. Meaning they are not "fixed" and may change. Not the best for
> uses in a
> client/server environment.
Isn't there some sort of automagic
On 22/06/2021 00:35, Ed Greshko wrote:
On 21/06/2021 22:47, Robert McBroom via users wrote:
Web interface. It shows
IPv6 IP Address
fe80::200:1eb5:75df:b84:98d1 , 2600:1702:4860:9dd0:21d:60ff:fe35:b813/64
exports configuration is "*"
Then the IPv6 address you want to use is 2600:1702:4860:9
On 21/06/2021 22:47, Robert McBroom via users wrote:
Web interface. It shows
IPv6 IP Address
fe80::200:1eb5:75df:b84:98d1 , 2600:1702:4860:9dd0:21d:60ff:fe35:b813/64
exports configuration is "*"
Then the IPv6 address you want to use is 2600:1702:4860:9dd0:21d:60ff:fe35:b813
--
Remind me to
On 6/21/21 10:16 AM, Ed Greshko wrote:
On 21/06/2021 22:06, Robert McBroom via users wrote:
On 6/21/21 9:49 AM, Ed Greshko wrote:
On 21/06/2021 21:17, Robert McBroom via users wrote:
Trying to connect to NAS with nfs using the ipv6 addressing.
@RobertPC ~]#ping fd2e:cb3b:f005::ec1
PING fd2e:c
On 21/06/2021 22:06, Robert McBroom via users wrote:
On 6/21/21 9:49 AM, Ed Greshko wrote:
On 21/06/2021 21:17, Robert McBroom via users wrote:
Trying to connect to NAS with nfs using the ipv6 addressing.
@RobertPC ~]#ping fd2e:cb3b:f005::ec1
PING fd2e:cb3b:f005::ec1(fd2e:cb3b:f005::ec1) 56 da
On 6/21/21 9:49 AM, Ed Greshko wrote:
On 21/06/2021 21:17, Robert McBroom via users wrote:
Trying to connect to NAS with nfs using the ipv6 addressing.
@RobertPC ~]#ping fd2e:cb3b:f005::ec1
PING fd2e:cb3b:f005::ec1(fd2e:cb3b:f005::ec1) 56 data bytes
64 bytes from fd2e:cb3b:f005::ec1: icmp_seq=1
On 21/06/2021 21:17, Robert McBroom via users wrote:
What is needed to get the ipv6 connection?
Oh, and of course, you'll need the appropriate entry in the server's exports
file.
--
Remind me to ignore comments which aren't germane to the thread.
_
On 21/06/2021 21:17, Robert McBroom via users wrote:
Trying to connect to NAS with nfs using the ipv6 addressing.
@RobertPC ~]#ping fd2e:cb3b:f005::ec1
PING fd2e:cb3b:f005::ec1(fd2e:cb3b:f005::ec1) 56 data bytes
64 bytes from fd2e:cb3b:f005::ec1: icmp_seq=1 ttl=64 time=0.120 ms
64 bytes from fd2
On 21/06/2021 20:31, Patrick O'Callaghan wrote:
On Mon, 2021-06-21 at 20:02 +0800, Ed Greshko wrote:
On 21/06/2021 19:48, Patrick O'Callaghan wrote:
To avoid ambiguity, maybe you should tell me the journal options
you´d
like (the timestamps in the uploaded logs don´t show wallclock
time).
The
$ uname -a
Linux harrier 5.12.11-300.fc34.x86_64 #1 SMP Wed Jun 16 15:47:58 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
As I sit here, my Lenovo T530 laptop is reporting packagekitd is taking
anywhere from 20 to 40 percent of CPU, per 'top.' There is continuous
disk activity. Nothing going on wi
Trying to connect to NAS with nfs using the ipv6 addressing.
@RobertPC ~]#ping fd2e:cb3b:f005::ec1
PING fd2e:cb3b:f005::ec1(fd2e:cb3b:f005::ec1) 56 data bytes
64 bytes from fd2e:cb3b:f005::ec1: icmp_seq=1 ttl=64 time=0.120 ms
64 bytes from fd2e:cb3b:f005::ec1: icmp_seq=2 ttl=64 time=0.100 ms
64
On Mon, 2021-06-21 at 20:02 +0800, Ed Greshko wrote:
> On 21/06/2021 19:48, Patrick O'Callaghan wrote:
> > To avoid ambiguity, maybe you should tell me the journal options
> > you´d
> > like (the timestamps in the uploaded logs don´t show wallclock
> > time).
>
> The journal times of what you've s
On 21/06/2021 18:17, Patrick O'Callaghan wrote:
I thought the contents of dmesg were already in the journal, but I may
have misunderstood their relationship.
I asked for dmesg since there is a gap in dmesg but not a corresponding gap in
the journal.
[ 30.093669] logitech-hidpp-device 0003:0
On 21/06/2021 19:48, Patrick O'Callaghan wrote:
To avoid ambiguity, maybe you should tell me the journal options you´d
like (the timestamps in the uploaded logs don´t show wallclock time).
The journal times of what you've supplied seem fine. They show
Jun 20 15:44:50 for example
and dmesg -T
On Mon, 2021-06-21 at 18:57 +0800, Ed Greshko wrote:
> On 21/06/2021 18:27, Ed Greshko wrote:
> > On 21/06/2021 18:17, Patrick O'Callaghan wrote:
> > > On Mon, 2021-06-21 at 17:43 +0800, Ed Greshko wrote:
> > > > On 21/06/2021 17:20, Patrick O'Callaghan wrote:
> > > > > The logs are now publicly vi
On 21/06/2021 18:27, Ed Greshko wrote:
On 21/06/2021 18:17, Patrick O'Callaghan wrote:
On Mon, 2021-06-21 at 17:43 +0800, Ed Greshko wrote:
On 21/06/2021 17:20, Patrick O'Callaghan wrote:
The logs are now publicly visible at:
https://drive.google.com/drive/folders/1nGwVkeTJh5hz4dYRBD7Ikpx6q4Ma
On 21/06/2021 18:17, Patrick O'Callaghan wrote:
On Mon, 2021-06-21 at 17:43 +0800, Ed Greshko wrote:
On 21/06/2021 17:20, Patrick O'Callaghan wrote:
The logs are now publicly visible at:
https://drive.google.com/drive/folders/1nGwVkeTJh5hz4dYRBD7Ikpx6q4MaPki9?usp=sharing
I've included my home-
On Mon, 2021-06-21 at 17:43 +0800, Ed Greshko wrote:
> On 21/06/2021 17:20, Patrick O'Callaghan wrote:
> > The logs are now publicly visible at:
> > https://drive.google.com/drive/folders/1nGwVkeTJh5hz4dYRBD7Ikpx6q4MaPki9?usp=sharing
> >
> > I've included my home-grown 'dock' scripts for completen
[0 07:20:34 root@yoda33 ~]$ swapon
NAME TYPE SIZE USED PRIO
/dev/sdc1 partition 64G 9.7M 300
/dev/sdd1 partition 64G 9.4M 300
[0 03:06:33 root@yoda33 ~]$ uptime
03:08:30 up 23 days, 18:33, 2 users, load average: 0.01, 0.01, 0.00
On 6/21/2021 4:18 AM, Ed Greshko wrote:
On 21/06/2021 1
On 21/06/2021 17:20, Patrick O'Callaghan wrote:
The logs are now publicly visible at:
https://drive.google.com/drive/folders/1nGwVkeTJh5hz4dYRBD7Ikpx6q4MaPki9?usp=sharing
I've included my home-grown 'dock' scripts for completeness, plus logs
of a Fedora Live boot (with no delay) and my current i
On Mon, 2021-06-21 at 06:19 +0800, Ed Greshko wrote:
> 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
On Sun, 2021-06-20 at 18:00 -0600, Chris Murphy wrote:
> 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 th
On Sun, 2021-06-20 at 17:40 -0600, Joe Zeff wrote:
> 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 itsel
On Mon, 2021-06-21 at 06:59 +0800, Ed Greshko wrote:
> 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
On 21/06/2021 16:05, Bill Shirley wrote:
The server is running on Raid-1 SSDs with 64GB of RAM
I suppose the follow-up question would be are you seeing the swap partition
actually being used?
Does "swapon" show it has been used?
--
Remind me to ignore comments which aren't germane to the th
The server is running on Raid-1 SSDs with 64GB of RAM
Bill
On 6/21/2021 3:41 AM, Samuel Sieb wrote:
On 6/20/21 7:25 PM, Bill Shirley wrote:
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
On 6/20/21 7:25 PM, Bill Shirley wrote:
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.
Why?
___
users mailing list -- users@lists.fedoraprojec
53 matches
Mail list logo
