> -----Message d'origine----- > De : Tobi Oetiker [mailto:tobi@xxxxxxxxxx] > Envoyé : 19 août 2008 10:29 > > Hi Vincent, > > Today Fortier,Vincent [Montreal] wrote: > > > Hi Thomas, > > > > I saw this post from you: > > http://marc.info/?l=linux-nfs&m=121345713729459&w=2 > > > > Have you found any way to solve the problem? > > > > Until now I have only seen that behaviour on a 64bit 2.6.24 kernel > > (running debian etchnhalf). I was about to check wether it does it or > > not in 32bit. > > > > Help greatly appreciated! > > > > > we have not yet solved the problem ... we see it with a > 2.6.24 server and 2.6.24 client both 64bit .... > > since the message comes from the server, I imagine the probem > is with the server ... but maybe the client strokes the > server the wrong way ... > > did you figure anything out ? It has to be client-side... I have not seen this with any previous kernels on the client-side (either old redhat 7.3 with 2.4.20 kernels or Debian Sarge with 2.6.8 to 2.6.23.17). Also my server side is unchanged with a RHEL 4 (2.6.9 based kernel). This is a totally new behaviour to me wich only occured with installation of 64bit 2.6.24 kernel based debian etch clients (have not yet tried 32bit to confirm wether it is 2.6.24 OR amd64 based). Although I cannot reproduce it with a 2.6.23.17 32-bit. If the problem reside with 2.6.24 kernel (and not 64bit specific) it should be "easy" to git bisect where it comes from (although did not catch the details of git bisect just yet :) Note: Added linux-nfs in CC. - vin -- 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
