Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 27 Oct 2020 13:12:40 -0400
To:     Vasyl Vavrychuk <vvavrychuk@gmail.com>
Cc:     linux-nfs@vger.kernel.org
Subject: Re: Hard linking symlink does not work
Message-ID: <20201027171240.GA1644@fieldses.org>
References: <CAGj4m+5rpNqW=XnU2cxGmWiBi47w3XTvn9EGekVPjq74pHfFGA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAGj4m+5rpNqW=XnU2cxGmWiBi47w3XTvn9EGekVPjq74pHfFGA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
From:   bfields@fieldses.org (J. Bruce Fields)
Precedence: bulk

On Fri, Oct 23, 2020 at 01:13:02PM +0300, Vasyl Vavrychuk wrote:
> I have found that hard links for regular files works well for me over NFS:
> 
> $ touch bar
> $ ln bar tata
> 
> But if I try to make hard link for symlink, then it fails:
> 
> $ ln -s foo bar
> $ ln bar tata
> ln: failed to create hard link 'tata' => 'bar': Operation not permitted

Huh.  I'm not sure I even realized it was possible to hardlink symlinks.
Makes sense, I guess.

I think my first step debugging this would be to watch wireshark while
attempting the "ln", and see what happens.  That should tell us whether
it's the client or server that's failing the operation.

--b.

> 
> I am using NFSv4 with Vagrant, here is mount entry:
> 
> 172.28.128.1:PATH on /vagrant type nfs4
> (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=IP,local_lock=none,addr=IP)
> 
> I have also verified that rpc-statd is running on host.
> 
> Host machine is Ubuntu 18.04 with NFS packages version 1:1.3.4-2.1ubuntu5.3.
> 
> Will appreciate help on this.
> 
> Thanks,
> Vasyl