Re: Proxmox and NetApp NFS volumes
tmac <[email protected]> Wed, 12 Nov 2025 06:37:27 -0500
| Newsgroups | gmane.comp.hardware.netapp |
|---|---|
| Message-ID | <CAL9X-_HnQNPDVahLgpP5KtN1MFL_90E-efouETELDh4VwG5+sw@mail.gmail.com> |
--===============8300110804688585453== Content-Type: multipart/alternative; boundary="0000000000001885910643643195" --0000000000001885910643643195 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable You can modify the nfs server: [-tcp-max-xfer-size <integer>] - TCP Maximum Transfer Size (bytes) (privilege: advanced) This optional parameter specifies the maximum transfer size (in bytes) that the storage system negotiates with the client for TCP transport of data for NFSv3 and NFSv4.x protocols. The range is 8192 to 1048576 Setting to the max of 1048576 will allow the client to be set to the same If your nfs client supports it, you can use =E2=80=9Cnconnect=E2=80=9D set = to 4 to also help Sent from Gmail Mobile. On Wed, Nov 12, 2025 at 5:56=E2=80=AFAM Florian Schmid via toasters < [email protected]> wrote: > > > > ---------- Forwarded message ---------- > From: Florian Schmid <[email protected]> > To: "Parisi, Justin" <[email protected]> > Cc: toasters <[email protected]> > Bcc: > Date: Wed, 12 Nov 2025 10:55:50 +0000 > Subject: Re: Proxmox and NetApp NFS volumes > Hello Justin, > > Thank you very much for your reply. > > Actually, we won't need the additional security NFSv4 would bring. > Advanced locking is also not an issue, as the VM disks are always only us= ed > on a single node. > > Do you have any real life experience with NetApp and Proxmox using NFS? > NFSv3 has always worked for us, should we stay there? > > When using NFSv3, rsize and wsize are always at 65536. Can this be > increased and if yes, should I do this? > We have 25 Gbit from Proxmox to NetApp with MTU of 1500. > > Any other tweaks here: > rw,relatime,vers=3D3,rsize=3D65536,wsize=3D65536,namlen=3D255,hard,proto= =3Dtcp,timeo=3D600,retrans=3D2,sec=3Dsys,mountaddr=3D172.16.4.3,mountvers= =3D3,mountport=3D635,mountproto=3Dudp,local_lock=3Dnone,addr=3D172.16.4.3 > 0 0 > > Best regards, > Flo > > > ------------------------------ > *From:* Parisi, Justin <[email protected]> > *Sent:* Monday, 10 November 2025 16:10 > *To:* tmac <[email protected]>; Florian Schmid <[email protected]> > *Cc:* toasters <[email protected]> > *Subject:* RE: Proxmox and NetApp NFS volumes > > > With any move from NFSv3 to NFSv4.x, you have to take into consideration > the major changes in how the protocols work. In a virt use case, you main= ly > would care most about the change in stateful vs. stateless, where storage > failovers could introduce more delay/disruption in NFSv4.x than v3, due t= o > locks and states. NFSv4.2 has no mount options avoiding this, but you can > tune some of the lock grace periods on the SVM if needed. > > > > TR-4067 covers the differences in the protocol versions on page 42 and ha= s > some information about nondisruptive operations on page 63. > > > > https://www.netapp.com/pdf.html?item=3D/media/10720-tr-4067.pdf > > > > While NFSv3 is indeed old, it is still very viable for most use cases, > provided you don=E2=80=99t require the added security or locking benefits= in > NFSv4.x. > > > > *From:* tmac <[email protected]> > *Sent:* Friday, November 7, 2025 10:32 PM > *To:* Florian Schmid <[email protected]> > *Cc:* toasters <[email protected]> > *Subject:* Re: Proxmox and NetApp NFS volumes > > > > *EXTERNAL EMAIL - USE CAUTION when clicking links or attachments * > > > > > https://docs.netapp.com/us-en/netapp-solutions-virtualization/proxmox/ind= ex.html# > <https://docs.netapp.com/us-en/netapp-solutions-virtualization/proxmox/in= dex.html> > > > > > Sent from Gmail Mobile. > > > > > > On Fri, Nov 7, 2025 at 7:52=E2=80=AFAM Florian Schmid via toasters < > [email protected]> wrote: > > > > > ---------- Forwarded message ---------- > From: Florian Schmid <[email protected]> > To: toasters <[email protected]> > Cc: > Bcc: > Date: Fri, 7 Nov 2025 12:52:00 +0000 > Subject: Proxmox and NetApp NFS volumes > > Hello, > > > > we are moving to Proxmox now and I would need some help from you. > > > > In the past, I have always used NFSv3, because in our KVM environment, we > had issues with NFSv4.1 and head fail-overs -> VMs got paused > > I think also VMware had such issues. Problem I think is that NFSv4.1 is > stateful and on a head fail-over, this state got lost. > > > > I'm on 9.14.1. > > > > As NFSv3 is quite old and Proxmox is using a newer kernel, I wanted to > ask, if someone of you have experience with Proxmox and NFS volumes from > NetApp. > > > > Do you use special mount options? > > Is NFSv4.2 working fine with head fail-overs -> VMs are not pausing or > don't even notice it? > > We have 25 Gbit network interfaces as a bond to our NetApp, are here any > special options to configure? > > Are you using on VM disks "cache=3Dnone" or something different? > > > > Unfortunately, Proxmox has not much experience with NetApp either, so tha= t > I hope someone from you can help me here to create a good, fast and stabl= e > setup. > > > > This is how a mount point looks like with default options from Proxmox an= d > NFSv3: > > *nfs-root-01:/pve_DC_nfs_root_01 /mnt/pve/nfs-v3-root-01 nfs > rw,relatime,vers=3D3,rsize=3D65536,wsize=3D65536,namlen=3D255,hard,proto= =3Dtcp,timeo=3D600,retrans=3D2,sec=3Dsys,mountaddr=3D172.16.4.3,mountvers= =3D3,mountport=3D635,mountproto=3Dudp,local_lock=3Dnone,addr=3D172.16.4.3 > 0 0* > > > > This is from our old virtualization oVirt: > > *nfs-root-01:/oVirt_DC_nfs_root_01 > /rhev/data-center/mnt/nfs-root-01:_oVirt__DC__nfs__root__01 nfs > rw,relatime,vers=3D3,rsize=3D65536,wsize=3D65536,namlen=3D255,soft,nolock= ,nosharecache,proto=3Dtcp,timeo=3D600,retrans=3D6,sec=3Dsys,mountaddr=3D172= .16.4.3,mountvers=3D3,mountport=3D635,mountproto=3Dudp,local_lock=3Dall,add= r=3D172.16.4.3 > 0 0* > > > > - oVirt was using soft, but this I think, I shouldn't use on Proxmox > and instead use hard. oVirt had a special watchdog for this. > > > > Best regards, > > Florian > > > > > > > ---------- Forwarded message ---------- > From: Florian Schmid via toasters <[email protected]> > To: toasters <[email protected]> > Cc: > Bcc: > Date: Fri, 7 Nov 2025 12:52:00 +0000 > Subject: Proxmox and NetApp NFS volumes > _______________________________________________ > toasters mailing list -- [email protected] > To unsubscribe send an email to [email protected] > > > > > ---------- Forwarded message ---------- > From: Florian Schmid via toasters <[email protected]> > To: "Parisi, Justin" <[email protected]> > Cc: toasters <[email protected]> > Bcc: > Date: Wed, 12 Nov 2025 10:55:50 +0000 > Subject: Re: Proxmox and NetApp NFS volumes > _______________________________________________ > toasters mailing list -- [email protected] > To unsubscribe send an email to [email protected] > --0000000000001885910643643195 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">You can modify the nfs server:</div><div dir=3D"auto"><di= v><dt style=3D"margin:0px 0px 0.3125em;padding:0px;direction:ltr;font-size:= 20px;line-height:1.5;font-weight:bold;font-family:"source sans pro&quo= t;,sans-serif;font-style:normal;letter-spacing:normal;text-indent:0px;text-= transform:none;white-space:normal;word-spacing:0px;color:rgb(69,69,69)"><co= de style=3D"font-family:monospace,monospace;font-size:0.9375em;font-weight:= 400;margin:0px;display:inline-block;line-height:1.45;padding:0.1em 0.5ex;le= tter-spacing:0px;word-spacing:-0.15em;border-radius:4px;font-style:normal!i= mportant;background-color:rgb(247,247,248);color:rgba(0,0,0,0.9)">[-tcp-max= -xfer-size <integer>]</code>=C2=A0- TCP Maximum Transfer Size (bytes)= =C2=A0(privilege: advanced)</dt><dd style=3D"margin:0px 0px 12px 1.125em;pa= dding:0px;direction:ltr;font-family:"source sans pro",sans-serif;= font-size:20px;font-style:normal;font-weight:400;letter-spacing:normal;text= -indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:r= gb(69,69,69)"><p style=3D"margin:0px 0px 24px;padding:0px;direction:ltr;fon= t-weight:300;font-size:16px;line-height:1.5;letter-spacing:0px;font-style:n= ormal;text-align:inherit;text-indent:0px;text-transform:none;font-family:&q= uot;source sans pro",sans-serif;color:rgb(69,69,69)">This optional par= ameter specifies the maximum transfer size (in bytes) that the storage syst= em negotiates with the client for TCP transport of data for NFSv3 and NFSv4= .x protocols. The range is 8192 to 1048576</p></dd></div>Setting to the max= of 1048576 will allow the client to be set to the same</div><div dir=3D"au= to"><br></div><div dir=3D"auto">If your nfs client supports it, you can use= =E2=80=9Cnconnect=E2=80=9D set to 4 to also help<br clear=3D"all"><br clea= r=3D"all"><div dir=3D"auto"><div dir=3D"ltr" class=3D"gmail_signature" data= -smartmail=3D"gmail_signature">Sent from Gmail Mobile.</div></div></div><di= v><br></div><div><br><div class=3D"gmail_quote gmail_quote_container"><div = dir=3D"ltr" class=3D"gmail_attr">On Wed, Nov 12, 2025 at 5:56=E2=80=AFAM Fl= orian Schmid via toasters <<a href=3D"mailto:[email protected]= ">[email protected]</a>> wrote:<br></div><blockquote class=3D"= gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border= -left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><br>= <br><br>---------- Forwarded message ----------<br>From:=C2=A0Florian Schmi= d <<a href=3D"mailto:[email protected]" target=3D"_blank">fschmid@ubime= t.com</a>><br>To:=C2=A0"Parisi, Justin" <<a href=3D"mailto:= [email protected]" target=3D"_blank">[email protected]</a>>= ;<br>Cc:=C2=A0toasters <<a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a>><br>Bcc:=C2=A0<br>Date:=C2=A0Wed, = 12 Nov 2025 10:55:50 +0000<br>Subject:=C2=A0Re: Proxmox and NetApp NFS volu= mes<br> <div dir=3D"ltr"> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> Hello Justin,</div> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> <br> </div> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> Thank you very much for your reply.</div> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> <br> </div> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> Actually, we won't need the additional security NFSv4 would bring. Adva= nced locking is also not an issue, as the VM disks are always only used on = a single node.</div> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> <br> </div> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> Do you have any real life experience with NetApp and Proxmox using NFS?</di= v> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> NFSv3 has always worked for us, should we stay there?</div> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> <br> </div> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> When using NFSv3, rsize and wsize are always at 65536. Can this be increase= d and if yes, should I do this?</div> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> We have 25 Gbit from Proxmox to NetApp with MTU of 1500.</div> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> <br> </div> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> Any other tweaks here:</div> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> rw,relatime,vers=3D3,rsize=3D65536,wsize=3D65536,namlen=3D255,hard,proto=3D= tcp,timeo=3D600,retrans=3D2,sec=3Dsys,mountaddr=3D172.16.4.3,mountvers=3D3,= mountport=3D635,mountproto=3Dudp,local_lock=3Dnone,addr=3D172.16.4.3 0 0</d= iv> <div id=3D"m_6798933129253282645Signature"> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> <br> </div> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> Best regards,</div> <div style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Cali= bri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"> Flo</div> <p style=3D"margin-top:1em;margin-bottom:0cm"><span style=3D"font-family:Ap= tos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;fon= t-size:12pt;color:rgb(179,179,179)"><br> </span></p> </div> <div id=3D"m_6798933129253282645appendonsend"></div> <hr style=3D"display:inline-block;width:98%"> <div id=3D"m_6798933129253282645divRplyFwdMsg" dir=3D"ltr"><font face=3D"Ca= libri, sans-serif" style=3D"font-size:11pt;font-family:Calibri,sans-serif;c= olor:rgb(0,0,0)"><b style=3D"font-family:Calibri,sans-serif">From:</b> Pari= si, Justin <<a href=3D"mailto:[email protected]" target=3D"_blank= " style=3D"font-family:Calibri,sans-serif">[email protected]</a>>= <br> <b style=3D"font-family:Calibri,sans-serif">Sent:</b> Monday, 10 November 2= 025 16:10<br> <b style=3D"font-family:Calibri,sans-serif">To:</b> tmac <<a href=3D"mai= lto:[email protected]" target=3D"_blank" style=3D"font-family:Calibri,sans-s= erif">[email protected]</a>>; Florian Schmid <<a href=3D"mailto:fschmi= [email protected]" target=3D"_blank" style=3D"font-family:Calibri,sans-serif">fs= [email protected]</a>><br> <b style=3D"font-family:Calibri,sans-serif">Cc:</b> toasters <<a href=3D= "mailto:[email protected]" target=3D"_blank" style=3D"font-family:Calib= ri,sans-serif">[email protected]</a>><br> <b style=3D"font-family:Calibri,sans-serif">Subject:</b> RE: Proxmox and Ne= tApp NFS volumes</font> <div>=C2=A0</div> </div></div><div dir=3D"ltr"> <div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"overflow-wrap: = break-word;"> <div> <p>With any move from NFSv3 to NFSv4.x, you have to take into consideration= the major changes in how the protocols work. In a virt use case, you mainl= y would care most about the change in stateful vs. stateless, where storage= failovers could introduce more delay/disruption in NFSv4.x than v3, due to locks and state= s. NFSv4.2 has no mount options avoiding this, but you can tune some of the= lock grace periods on the SVM if needed.</p> <p>=C2=A0</p> <p>TR-4067 covers the differences in the protocol versions on page 42 and h= as some information about nondisruptive operations on page 63.</p> <p>=C2=A0</p> <p><a href=3D"https://www.netapp.com/pdf.html?item=3D/media/10720-tr-4067.p= df" target=3D"_blank">https://www.netapp.com/pdf.html?item=3D/media/10720-t= r-4067.pdf</a></p> <p>=C2=A0</p> <p>While NFSv3 is indeed old, it is still very viable for most use cases, p= rovided you don=E2=80=99t require the added security or locking benefits in= NFSv4.x.</p> <p>=C2=A0</p> <div> <div style=3D"border-width:1pt medium medium;border-style:solid none none;p= adding:3pt 0in 0in;border-color:rgb(225,225,225) currentcolor currentcolor"= > <p><b><span style=3D"font-size:11pt;font-family:Calibri,sans-serif">From:</= span></b><span style=3D"font-size:11pt;font-family:Calibri,sans-serif"> tma= c <<a href=3D"mailto:[email protected]" target=3D"_blank" style=3D"font-f= amily:Calibri,sans-serif">[email protected]</a>> <br> <b style=3D"font-family:Calibri,sans-serif">Sent:</b> Friday, November 7, 2= 025 10:32 PM<br> <b style=3D"font-family:Calibri,sans-serif">To:</b> Florian Schmid <<a h= ref=3D"mailto:[email protected]" target=3D"_blank" style=3D"font-family:Ca= libri,sans-serif">[email protected]</a>><br> <b style=3D"font-family:Calibri,sans-serif">Cc:</b> toasters <<a href=3D= "mailto:[email protected]" target=3D"_blank" style=3D"font-family:Calib= ri,sans-serif">[email protected]</a>><br> <b style=3D"font-family:Calibri,sans-serif">Subject:</b> Re: Proxmox and Ne= tApp NFS volumes</span></p> </div> </div> <p>=C2=A0</p> <table border=3D"1" cellspacing=3D"0" cellpadding=3D"0" align=3D"left" styl= e=3D"background:0% 0% repeat rgb(243,109,109)"> <tbody> <tr> <td style=3D"padding:5pt"> <p><b><span style=3D"font-family:Arial,sans-serif;color:black">EXTERNAL EMA= IL - USE CAUTION when clicking links or attachments </span></b></p> </td> </tr> </tbody> </table> <p style=3D"margin-bottom:12pt"><br> <br> </p> <div> <div> <div> <p><a href=3D"https://docs.netapp.com/us-en/netapp-solutions-virtualization= /proxmox/index.html" target=3D"_blank">https://docs.netapp.com/us-en/netapp= -solutions-virtualization/proxmox/index.html#</a></p> </div> <p><br clear=3D"all"> <br> <br> </p> <div> <div> <p>Sent from Gmail Mobile.</p> </div> </div> </div> <div> <p>=C2=A0</p> </div> <div> <p>=C2=A0</p> <div> <div> <p>On Fri, Nov 7, 2025 at 7:52<span style=3D"font-family:Arial,sans-serif">= =E2=80=AF</span>AM Florian Schmid via toasters <<a href=3D"mailto:toaste= [email protected]" target=3D"_blank">[email protected]</a>>= ; wrote:</p> </div> <blockquote style=3D"border-width:medium medium medium 1pt;border-style:non= e none none solid;padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0i= n;border-color:currentcolor currentcolor currentcolor rgb(204,204,204)"> <p><br> <br> <br> ---------- Forwarded message ----------<br> From:=C2=A0Florian Schmid <<a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a>><br> To:=C2=A0toasters <<a href=3D"mailto:[email protected]" target=3D"_b= lank">[email protected]</a>><br> Cc:=C2=A0<br> Bcc:=C2=A0<br> Date:=C2=A0Fri, 7 Nov 2025 12:52:00 +0000<br> Subject:=C2=A0Proxmox and NetApp NFS volumes</p> <div> <div> <p><span style=3D"color:black">Hello,</span></p> </div> <div> <p><span style=3D"color:black">=C2=A0</span></p> </div> <div> <p><span style=3D"color:black">we are moving to Proxmox now and I would nee= d some help from you.</span></p> </div> <div> <p><span style=3D"color:black">=C2=A0</span></p> </div> <div> <p><span style=3D"color:black">In the past, I have always used NFSv3, becau= se in our KVM environment, we had issues with NFSv4.1 and head fail-overs -= > VMs got paused</span></p> </div> <div> <p><span style=3D"color:black">I think also VMware had such issues. Problem= I think is that NFSv4.1 is stateful and on a head fail-over, this state go= t lost.</span></p> </div> <div> <p><span style=3D"color:black">=C2=A0</span></p> </div> <div> <p><span style=3D"color:black">I'm on 9.14.1.</span></p> </div> <div> <p><span style=3D"color:black">=C2=A0</span></p> </div> <div> <p><span style=3D"color:black">As NFSv3 is quite old and Proxmox is using a= newer kernel, I wanted to ask, if someone of you have experience with Prox= mox and NFS volumes from NetApp.</span></p> </div> <div> <p><span style=3D"color:black">=C2=A0</span></p> </div> <div> <p><span style=3D"color:black">Do you use special mount options?</span></p> </div> <div> <p><span style=3D"color:black">Is NFSv4.2 working fine with head fail-overs= -> VMs are not pausing or don't even notice it?</span></p> </div> <div> <p><span style=3D"color:black">We have 25 Gbit network interfaces as a bond= to our NetApp, are here any special options to configure?</span></p> </div> <div> <p><span style=3D"color:black">Are you using on VM disks "cache=3Dnone= " or something different?</span></p> </div> <div> <p><span style=3D"color:black">=C2=A0</span></p> </div> <div> <p><span style=3D"color:black">Unfortunately, Proxmox has not much experien= ce with NetApp either, so that I hope someone from you can help me here to = create a good, fast and stable setup.</span></p> </div> <div> <p><span style=3D"color:black">=C2=A0</span></p> </div> <div> <p><span style=3D"color:black">This is how a mount point looks like with de= fault options from Proxmox and NFSv3:</span></p> </div> <div> <p><i><span style=3D"font-size:10pt;color:black">nfs-root-01:/pve_DC_nfs_ro= ot_01 /mnt/pve/nfs-v3-root-01 nfs rw,relatime,vers=3D3,rsize=3D65536,wsize= =3D65536,namlen=3D255,hard,proto=3Dtcp,timeo=3D600,retrans=3D2,sec=3Dsys,mo= untaddr=3D172.16.4.3,mountvers=3D3,mountport=3D635,mountproto=3Dudp,local_l= ock=3Dnone,addr=3D172.16.4.3 0 0</span></i><span style=3D"color:black"></span></p> </div> <div> <p><span style=3D"color:black">=C2=A0</span></p> </div> <div> <p><span style=3D"color:black">This is from our old virtualization oVirt:</= span></p> </div> <div> <p><i><span style=3D"font-size:10pt;color:black">nfs-root-01:/oVirt_DC_nfs_= root_01 /rhev/data-center/mnt/nfs-root-01:_oVirt__DC__nfs__root__01 nfs rw,= relatime,vers=3D3,rsize=3D65536,wsize=3D65536,namlen=3D255,soft,nolock,nosh= arecache,proto=3Dtcp,timeo=3D600,retrans=3D6,sec=3Dsys,mountaddr=3D172.16.4= .3,mountvers=3D3,mountport=3D635,mountproto=3Dudp,local_lock=3Dall,addr=3D1= 72.16.4.3 0 0</span></i><span style=3D"color:black"></span></p> </div> <div> <p><span style=3D"color:black">=C2=A0</span></p> </div> <div> <ul type=3D"disc"> <li style=3D"color:black">oVirt was using soft, but this I think, I shouldn= 't use on Proxmox and instead use hard. oVirt had a special watchdog fo= r this.</li></ul> </div> <div> <p><span style=3D"color:black">=C2=A0</span></p> </div> <div> <p><span style=3D"color:black">Best regards,</span></p> </div> <div> <p><span style=3D"color:black">Florian</span></p> </div> <div> <p><span style=3D"color:black">=C2=A0</span></p> </div> </div> <p><br> <br> <br> ---------- Forwarded message ----------<br> From:=C2=A0Florian Schmid via toasters <<a href=3D"mailto:toasters@lists= .teaparty.net" target=3D"_blank">[email protected]</a>><br> To:=C2=A0toasters <<a href=3D"mailto:[email protected]" target=3D"_b= lank">[email protected]</a>><br> Cc:=C2=A0<br> Bcc:=C2=A0<br> Date:=C2=A0Fri, 7 Nov 2025 12:52:00 +0000<br> Subject:=C2=A0Proxmox and NetApp NFS volumes<br> _______________________________________________<br> toasters mailing list -- <a href=3D"mailto:[email protected]" tar= get=3D"_blank"> [email protected]</a><br> To unsubscribe send an email to <a href=3D"mailto:[email protected]= arty.net" target=3D"_blank"> [email protected]</a></p> </blockquote> </div> </div> </div> </div> </div> </div> <br><br><br>---------- Forwarded message ----------<br>From:=C2=A0Florian S= chmid via toasters <<a href=3D"mailto:[email protected]" targe= t=3D"_blank">[email protected]</a>><br>To:=C2=A0"Parisi, = Justin" <<a href=3D"mailto:[email protected]" target=3D"_bla= nk">[email protected]</a>><br>Cc:=C2=A0toasters <<a href=3D"ma= ilto:[email protected]" target=3D"_blank">[email protected]</a>>= <br>Bcc:=C2=A0<br>Date:=C2=A0Wed, 12 Nov 2025 10:55:50 +0000<br>Subject:=C2= =A0Re: Proxmox and NetApp NFS volumes<br>__________________________________= _____________<br> toasters mailing list -- <a href=3D"mailto:[email protected]" tar= get=3D"_blank">[email protected]</a><br> To unsubscribe send an email to <a href=3D"mailto:[email protected]= arty.net" target=3D"_blank">[email protected]</a><br> </blockquote></div></div> --0000000000001885910643643195-- --===============8300110804688585453== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ toasters mailing list -- [email protected] To unsubscribe send an email to [email protected] --===============8300110804688585453==--