On Sat, Nov 28, 2020 at 4:20 AM Richard Kimberly Heck
wrote:
> On 11/26/20 3:26 PM, Tom H wrote:
>>
>> You have to be careful when using "fsid=0".
>>
>> 1) If you don't set it for any of the shares:
>>
>> a) "/" is the "fsid=0" filesystem by default (this wasn't the
>> case in early nfsv4 implemen
On 11/26/20 3:26 PM, Tom H wrote:
On Wed, Nov 25, 2020 at 11:41 PM Richard Kimberly Heck
wrote:
This problem seems to have been solved. I believe that the issue
was a misconfiguration of the NFS server. I had:
/home/rikiheck/files 192.168.1.0/24(rw,sync,no_subtree_check,fsid=0)
/home/nancy/fil
On Wed, Nov 25, 2020 at 11:41 PM Richard Kimberly Heck
wrote:
>
> This problem seems to have been solved. I believe that the issue
> was a misconfiguration of the NFS server. I had:
>
> /home/rikiheck/files 192.168.1.0/24(rw,sync,no_subtree_check,fsid=0)
> /home/nancy/files192.168.1.0/24(rw,sy
On Nov 25, 2020, at 17:41, Richard Kimberly Heck wrote:
>
> But /home/rikiheck/files was an ordinary directory that I want to export, not
> the root for NFSv4. It was being mounted as NFSv3 (trying to mount with nfs4
> would fail). But I'm guessing that it was being treated inconsistently
> be
On 26/11/2020 06:40, Richard Kimberly Heck wrote:
This problem seems to have been solved. I believe that the issue was a
misconfiguration of the NFS server. I had:
/home/rikiheck/files 192.168.1.0/24(rw,sync,no_subtree_check,fsid=0)
/home/nancy/files 192.168.1.0/24(rw,sync,no_subtree_check)
/h
This problem seems to have been solved. I believe that the issue was a
misconfiguration of the NFS server. I had:
/home/rikiheck/files 192.168.1.0/24(rw,sync,no_subtree_check,fsid=0)
/home/nancy/files 192.168.1.0/24(rw,sync,no_subtree_check)
/home/photos 192.168.1.0/24(rw,sync,no_subtree_check
On 11/25/20 4:28 PM, Richard Kimberly Heck wrote:
On 11/25/20 12:56 PM, Ed Greshko wrote:
On 25/11/2020 22:51, Richard Kimberly Heck wrote:
I can mount fine. The problem is that various programs (LyX,
LibreOffice) freeze when attempting to open files on those
filesystems. In LyX, I was able
On 11/25/20 4:28 PM, Richard Kimberly Heck wrote:
On 11/25/20 12:56 PM, Ed Greshko wrote:
On 25/11/2020 22:51, Richard Kimberly Heck wrote:
I can mount fine. The problem is that various programs (LyX,
LibreOffice) freeze when attempting to open files on those
filesystems. In LyX, I was able
On 11/25/20 12:56 PM, Ed Greshko wrote:
On 25/11/2020 22:51, Richard Kimberly Heck wrote:
I can mount fine. The problem is that various programs (LyX,
LibreOffice) freeze when attempting to open files on those
filesystems. In LyX, I was able to trace the problem to a call to
lockd, which nev
On 26/11/2020 03:36, Robert wrote:
My fstab entry is as follows.
192.168.2.100:/STUF/STUFF /home/me/STUFF nfs rw 0 0
OK. Using just nfs on the fstab entry would mean that it should use the
default protocol on the
server. I am using a Centos7 server that hasn't been modified. So, nfs-v4 is
On 25/11/2020 22:51, Richard Kimberly Heck wrote:
I can mount fine. The problem is that various programs (LyX, LibreOffice) freeze when attempting to open files on those filesystems. In LyX, I was able to trace the problem to a call to lockd, which never returns. So it seems there is some proble
On 11/25/20 5:23 AM, Ed Greshko wrote:
On 25/11/2020 09:40, Ed Greshko wrote:
Can you confirm that the NFS server is on a Centos7 system?
Is NFS-v3 required, or can you switch to NFS-v4?
FWIW, I installed a Centos7 VM. And enabled nfs-server.service. The
server has the following:
[root@co
On 25/11/2020 09:40, Ed Greshko wrote:
Can you confirm that the NFS server is on a Centos7 system?
Is NFS-v3 required, or can you switch to NFS-v4?
FWIW, I installed a Centos7 VM. And enabled nfs-server.service. The server has
the following:
[root@cos7 etc]# firewall-cmd --get-active-zones
On 25/11/2020 07:59, Richard Kimberly Heck wrote:
On 11/24/20 5:53 PM, Ed Greshko wrote:
On 25/11/2020 05:43, Richard Kimberly Heck wrote:
On 11/24/20 2:12 PM, Jonathan Billings wrote:
On Tue, Nov 24, 2020 at 02:06:46PM -0500, Richard Kimberly Heck wrote:
This looks like the issue:
Nov 22 23
On 11/24/20 5:53 PM, Ed Greshko wrote:
On 25/11/2020 05:43, Richard Kimberly Heck wrote:
On 11/24/20 2:12 PM, Jonathan Billings wrote:
On Tue, Nov 24, 2020 at 02:06:46PM -0500, Richard Kimberly Heck wrote:
This looks like the issue:
Nov 22 23:10:03 rkhstudy kernel: lockd: server 192.168.1.2 n
On 25/11/2020 05:43, Richard Kimberly Heck wrote:
On 11/24/20 2:12 PM, Jonathan Billings wrote:
On Tue, Nov 24, 2020 at 02:06:46PM -0500, Richard Kimberly Heck wrote:
This looks like the issue:
Nov 22 23:10:03 rkhstudy kernel: lockd: server 192.168.1.2 not responding,
still trying
This was wo
On 11/24/20 2:12 PM, Jonathan Billings wrote:
On Tue, Nov 24, 2020 at 02:06:46PM -0500, Richard Kimberly Heck wrote:
This looks like the issue:
Nov 22 23:10:03 rkhstudy kernel: lockd: server 192.168.1.2 not responding,
still trying
This was working fine in Fedora 32, though, so I'm puzzled wha
On Tue, Nov 24, 2020 at 02:06:46PM -0500, Richard Kimberly Heck wrote:
> This looks like the issue:
>
> Nov 22 23:10:03 rkhstudy kernel: lockd: server 192.168.1.2 not responding,
> still trying
>
> This was working fine in Fedora 32, though, so I'm puzzled what's wrong now.
> There's no firewall
On 11/24/20 7:55 AM, Jonathan Billings wrote:
On Nov 23, 2020, at 22:08, Richard Kimberly Heck wrote:
I believe it is v3 on the server.
If so, you need to make sure that the rpc.lockd can communicate on both sides.
That is probably why locking fails, and any program that is hanging is because
On 11/24/20 2:18 AM, Stephen Morris wrote:
On 24/11/20 1:55 pm, Richard Kimberly Heck wrote:
On 11/23/20 9:17 PM, Jonathan Billings wrote:
On Nov 23, 2020, at 19:05, Richard Kimberly Heck
wrote:
LyX refuses to start, blocking at a call to
lockf(fd, F_LOCK, 0) at support/filetools.cpp, during
On Nov 23, 2020, at 22:08, Richard Kimberly Heck wrote:
>
> I believe it is v3 on the server.
If so, you need to make sure that the rpc.lockd can communicate on both sides.
That is probably why locking fails, and any program that is hanging is because
locks are hanging.
--
Jonathan Billings
On 24/11/20 1:55 pm, Richard Kimberly Heck wrote:
On 11/23/20 9:17 PM, Jonathan Billings wrote:
On Nov 23, 2020, at 19:05, Richard Kimberly Heck
wrote:
LyX refuses to start, blocking at a call to
lockf(fd, F_LOCK, 0) at support/filetools.cpp, during startup. (I
believe that fd here points at
On 11/23/20 9:17 PM, Jonathan Billings wrote:
On Nov 23, 2020, at 19:05, Richard Kimberly Heck wrote:
LyX refuses to start, blocking at a call to
lockf(fd, F_LOCK, 0) at support/filetools.cpp, during startup. (I
believe that fd here points at a file on the NFS share.)
Did you end up using N
On Nov 23, 2020, at 19:05, Richard Kimberly Heck wrote:
>
> LyX refuses to start, blocking at a call to
> lockf(fd, F_LOCK, 0) at support/filetools.cpp, during startup. (I believe
> that fd here points at a file on the NFS share.)
Did you end up using NFSv4? It sounds like a locking problem b
Hi, all,
Since upgrading to Fedora 33, I am having some problems accessing files
on NFS shares. I should say first that, immediately after the upgrade,
the shares would not mount at all. I was getting the error:
mount.nfs4: Operation not permitted when mounting NFS device
even when attemptin
25 matches
Mail list logo
