Hello Bruce, thanks... On Thursday 17 November 2016, J. Bruce Fields wrote: > On Thu, Nov 17, 2016 at 09:32:47PM +0100, Ulrich Gemkow wrote: > > Hello, > > > > we use Linux NFS clients with a Linux NFS server in an configuration > > where NFS mounts are done on client boot _and_ on user login in a > > session; umounts are done on users logout from the session. > > > > We see occasionally several different problems which all may have > > the same root cause: > > > > - When a client accesses a file which was accessed before > > from the same client in a previous session the server > > prevents access to the file until a timeout happens. > > > > The timeout has a duration of about 1-3 minutes. > > In this case the "blocked" file can not even be deleted > > on the server. > > > > --> What causes this timeout? I found nothing in the > > server code which has such a timeout How can I debug what > > the server is waiting for or why he is blocking access > > to the file? > > > > - Sometimes client processes hang in the middle of a session > > on some file. After a timeout the file is accessible again. > > The timeout can take 1 upto several minutes. The file is > > also blocked on the server, it cannot be accessed. > > > > I think all theses problemes are caused by something like > > dangling locks or another invalid state on the server. > > > > The clients show no network error like dropped packets > > or something like this. > > > > --> How can I debug such hangs? > > > > We use Linux NFS server and client from vanilla kernel 4.4.31 > > with sec=sys. > > > > Can anyone help? Does "a bell ring"? > > The lease period is 90 seconds by default, and there are several cases > where you can end up waiting for a lease period. I found the 90sec lease time period but the timeout is sometimes much longer than 90 sec, often up to 3minutes or longer. Is there something which may cause these longer delays (I played with the 90sec constant and it did not help :-) > For example, if the client held some delegations that it didn't return > on unmount, and then it denied knowledge of them when the server tried > to recall them, then the server would have to wait a lease period to > forcibly remove them. But, the client should be returning delegations > on unmount, so I don't see how this happens. > > For locks and opens and other state, again the client should be > returning them on unmount. And anyway the server isn't going to > forcibly remove those ever, unless the entire client goes away > completely, e.g. in a client crash or network partition. > > So, I don't know. Are you sure there aren't client crashes or network > problems? It happens that clients crash but IMHO the server should notice this by dropped connections. We have no network problems in these cases. > Also I'd personally try to arrange things so you, say, just mount /home/ > on boot instead of automounting /home/bfields when bfields logs in. > But, I don't know your situation. Sure, we can do this. But we are in an unsecure environment and it gives additional (required) security to use more specific mounts (we make the export on the server when the user has authenticated with our own daemon). What I really miss is an option to disable locks in NFSv4. Maybe you can point me to the right place in the source..? Any more ideas? Thanks again and best regards -Ulrich > > --b. > -- |----------------------------------------------------------------------- | Ulrich Gemkow |----- | Universität Stuttgart | Institut für Kommunikationsnetze und Rechnersysteme (IKR) |----- | University of Stuttgart | Institute of Communication Networks and Computer Engineering (IKR) |----- | Pfaffenwaldring 47, D 70569 Stuttgart, Germany | mailto:ulrich.gemkow@xxxxxxxxxxxxxxxxxxxx http://www.ikr.uni-stuttgart.de |----------------------------------------------------------------------- -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
