Neil Brown wrote: > On Wednesday July 16, SteveD@xxxxxxxxxx wrote: >>>> Enable retry if the mount call returns EIO, as that is what happens >>>> if the UDP requests to portmap get no response. >>> I would rather see this one addressed in the kernel. I think the EIO >>> return is a kernel bug. If the server doesn't support a particular >>> transport protocol for portmap, mountd, or NFS, the mount(2) system >>> call should always return EPROTONOSUPPORT. >> Since EIO has so many meanings... I think it should stay as a fatal >> error as well... >> > > That would be best. But the reality is that there are kernels in the > wild where -EIO indicates and error that isn't really fatal. Yeah I know... and thats the problem.. EIO is basically a catch all errno.. > > We already do kernel-detection in mount. How about extending it like > this? > > Thanks, > NeilBrown > > From: Neil Brown <neilb@xxxxxxx> > Date: Thu, 17 Jul 2008 12:23:03 +1000 > Subject: [PATCH] mount: Recognised EIO from early kernels as possibly indicating a protocol error. > > In kernels up to and including 2.6.26, mount reports "connection > refused" type messages as EIO rather than EPROTONOSUPPORT. > So detect those kernels and don't treat EIO as so fatal. Should we just fix the kernel to do the right thing? steved. -- 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
