tintri SW Version: 5.6.0.1-12976.59611.26248 with Proxmox 8.3.0 - NFS

kellogs

Active Member
May 14, 2024
183
29
28
adding a NFS target if using 4.1 on proxmox would generate this error

From GUI
create storage failed: mount error: mount.nfs: Too many levels of symbolic links (500)

From dmesg
VFS: Lookup of 'tintri' in nfs4 0:52 would have caused loop

But if i added it via nfs 3, removed the storage and re added it back choosing 4.1 it would be added successfully.

anyone seen this behaviour before?
 
althought it accepted being mounted as version 4.1 from GUI but when checking via cli it shows v3

10.88.90.200:/tintri on /mnt/pve/tintri88200 type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.88.90.200,mountvers=3,mountport=2061,mountproto=tcp,local_lock=none,addr=10.88.90.200)
 
also after removing the storage under datacenter, if you go to each node cli .. you can still see the mounts

10.88.90.202:/tintri 61T 3.1G 61T 1% /mnt/pve/tintri88202
10.88.90.200:/tintri 44T 27T 18T 61% /mnt/pve/tintri88200
 
it works if i mount from command line

10.88.90.202:/ 61T 3.1G 61T 1% /mnt
root@node16-84:~# mount -t nfs -o rw,vers=4.1,proto=tcp 10.88.90.202:/ /mnt
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!