On Sun, 2018-07-29 at 16:49 -0700, Samuel Sieb wrote:
> On 07/29/2018 03:08 PM, ToddAndMargo wrote:
> > On 07/28/2018 11:13 PM, Samuel Sieb wrote:
> > > On 07/28/2018 11:04 PM, ToddAndMargo wrote:
> > > > Actually it turned out not to be a typo. I was trying to open
> > > > a "dump" file in file-r
I have two computers, Fedora 27 and 28 that do not mount the nfs server
at boot. It works from root afterward without any difficulty but that is
a bit of an inconvenience. I put up with that problem with the Samba
server for a long time but two is too much!
This problem was unknown until I bui
On 07/30/18 22:40, Bob Goodwin wrote:
> I have two computers, Fedora 27 and 28 that do not mount the nfs server at
> boot. It
> works from root afterward without any difficulty but that is a bit of an
> inconvenience. I put up with that problem with the Samba server for a long
> time but
> two is
Hi.
On Mon, 30 Jul 2018 10:40:35 -0400 Bob Goodwin wrote:
> I have two computers, Fedora 27 and 28 that do not mount the nfs server
> at boot. It works from root afterward without any difficulty ...
This is perhaps (again) due to NetworkManager-wait-online.service
pretending too early that the
On Mon, 2018-07-30 at 22:57 +0800, Ed Greshko wrote:
> On 07/30/18 22:40, Bob Goodwin wrote:
> > I have two computers, Fedora 27 and 28 that do not mount the nfs server at
> > boot. It
> > works from root afterward without any difficulty but that is a bit of an
> > inconvenience. I put up with tha
On Mon, 2018-07-30 at 17:45 +0200, francis.montag...@inria.fr wrote:
> Hi.
>
> On Mon, 30 Jul 2018 10:40:35 -0400 Bob Goodwin wrote:
>
> > I have two computers, Fedora 27 and 28 that do not mount the nfs server
> > at boot. It works from root afterward without any difficulty ...
>
> This is per
On 07/30/18 10:57, Ed Greshko wrote:
In your fstab you can try changing it to something like
192.168.1.86:/home/exports /mnt/testb nfs4
rw,soft,intr,fg,comment=systemd.automount 0 0
You may not see it mounted at boot time but as soon as you access the directory
it
will become moun
On 07/30/18 12:01, Bob Goodwin wrote:
On 07/30/18 10:57, Ed Greshko wrote:
In your fstab you can try changing it to something like
192.168.1.86:/home/exports /mnt/testb nfs4
rw,soft,intr,fg,comment=systemd.automount 0 0
You may not see it mounted at boot time but as soon as you ac
On Mon, 30 Jul 2018 at 12:17, Bob Goodwin wrote:
> I have two computers, Fedora 27 and 28 that do not mount the nfs server
> at boot. It works from root afterward without any difficulty but that is
> a bit of an inconvenience. I put up with that problem with the Samba
> server for a long time but
On Mon, 30 Jul 2018 10:40:35 -0400
Bob Goodwin wrote:
> Fedora 27 and 28 that do not mount the nfs server
> at boot.
I always fix this using the big hammer work-around: mount them
from rc.local after a delay long enough to make sure the network
is really "up". This got more complicated when syst
On 07/30/2018 03:38 AM, Patrick O'Callaghan wrote:
On Sun, 2018-07-29 at 16:49 -0700, Samuel Sieb wrote:
On 07/29/2018 03:08 PM, ToddAndMargo wrote:
On 07/28/2018 11:13 PM, Samuel Sieb wrote:
On 07/28/2018 11:04 PM, ToddAndMargo wrote:
Actually it turned out not to be a typo. I was trying to
On Mon, 2018-07-30 at 13:11 -0700, ToddAndMargo wrote:
> dump is awesome for backing up servers in the middle of
> the night. dump/restore are also blazingly fast
IIRC one reason for that is that they don't walk the directory tree,
they just go through the inode table. This means that restoring
i
On 07/31/18 00:35, Bob Goodwin wrote:
> On 07/30/18 12:01, Bob Goodwin wrote:
>> On 07/30/18 10:57, Ed Greshko wrote:
>>> In your fstab you can try changing it to something like
>>>
>>> 192.168.1.86:/home/exports /mnt/testb nfs4
>>> rw,soft,intr,fg,comment=systemd.automount 0 0
>>>
>>>
On 07/30/18 17:46, Ed Greshko wrote:
If you do
journalctl -b 0 | grep mount
on the client, what does it show?
+
I guess this is not to long to send the entire result -
[bobg@Box10 ~]$ journalctl -b 0 | grep mount
Jul 30 11:44:50 localhost.localdomain kernel: EXT4-fs (sdb1): mounted
filesyst
On 07/30/2018 02:06 PM, Patrick O'Callaghan wrote:
> On Mon, 2018-07-30 at 13:11 -0700, ToddAndMargo wrote:
>> dump is awesome for backing up servers in the middle of
>> the night. dump/restore are also blazingly fast
>
> IIRC one reason for that is that they don't walk the directory tree,
> they
On 07/30/2018 02:56 PM, Bob Goodwin wrote:
> On 07/30/18 17:46, Ed Greshko wrote:
>> If you do
>>
>> journalctl -b 0 | grep mount
>>
>> on the client, what does it show?
> +
>
> I guess this is not to long to send the entire result -
>
> [bobg@Box10 ~]$ journalctl -b 0 | grep mount
> Jul 30 11:44
On 07/30/18 17:56, Bob Goodwin wrote:
On 07/30/18 17:46, Ed Greshko wrote:
If you do
journalctl -b 0 | grep mount
on the client, what does it show?
+
There are two servers shown there, box86, /mnt/testb is the one of
interest that has only recently quit connecting automatically. The smb
se
On 07/31/18 06:09, Rick Stevens wrote:
> On 07/30/2018 02:56 PM, Bob Goodwin wrote:
>> On 07/30/18 17:46, Ed Greshko wrote:
>>> If you do
>>>
>>> journalctl -b 0 | grep mount
>>>
>>> on the client, what does it show?
>> +
>>
>> I guess this is not to long to send the entire result -
> I expect this
On 07/30/18 18:09, Rick Stevens wrote:
I expect this is a race condition with NetworkManager-
wait-online.service. By default, it does a oneshot of:
nm-online -s -q --timeout=30
and nm-online COULD return a 1 if NM is running but hasn't brought up
the network yet due to a slow DHCP resp
On 07/31/18 06:38, Ed Greshko wrote:
> I'd never seen log entries like the type Bob posted.
Just as a test, I set up a VM as an NFS client with this in the fstab.
ds6:/volume1/misty /home/egreshko/misty nfs4
rw,soft,intr,fg,comment=systemd.automount 0 0
I then ssh'd into the sy
On 07/30/2018 04:45 PM, Ed Greshko wrote:
> On 07/31/18 06:38, Ed Greshko wrote:
>> I'd never seen log entries like the type Bob posted.
>
>
> Just as a test, I set up a VM as an NFS client with this in the fstab.
>
> ds6:/volume1/misty /home/egreshko/misty nfs4
> rw,soft,intr,fg,co
Hello,
Using Boxes, I installed a Windows 10 guest. I installed the spice drivers
from spice-space.org/download
(https://www.spice-space.org/download/windows/spice-guest-tools/spice-guest-tools-latest.exe)
and things look good.
However, when the guest is idle, cpu is 0-4% the host process is s
On 07/31/18 08:45, Rick Stevens wrote:
> On 07/30/2018 04:45 PM, Ed Greshko wrote:
>> On 07/31/18 06:38, Ed Greshko wrote:
>>> I'd never seen log entries like the type Bob posted.
>>
>> Just as a test, I set up a VM as an NFS client with this in the fstab.
>>
>> ds6:/volume1/misty /home/egres
I've learned two more things:
1. I installed an ubuntu guest OS, and it has the same high host cpu when the
guest is idle.
2. using strace, I see this is 97% of the system calls:
ppoll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=7, events=POLLIN},
{fd=8, events=POLLIN}, {fd=13, events=POLL
On 07/31/18 05:56, Bob Goodwin wrote:
> On 07/30/18 17:46, Ed Greshko wrote:
>> If you do journalctl -b 0 | grep mount on the client, what does it show?
> +
>
>
>
> Jul 30 11:46:47 Box10 systemd[1]: mnt-testb.automount: Got automount request
> for
> /mnt/testb, triggered by 1670 (wish)
> Jul 30 11
25 matches
Mail list logo
