On Mon, Oct 15, 2012 at 07:34:56AM -0700, Larry McVoy wrote: > On Mon, Oct 15, 2012 at 04:38:02AM +0000, Myklebust, Trond wrote: > > On Sun, 2012-10-14 at 20:43 -0400, Bruce Fields wrote: > > > On Sat, Oct 13, 2012 at 06:42:15PM -0700, Larry McVoy wrote: > > > > > PS: you are presumably running NFSv2 on your Macs. Odd that they should > > > > > default to that... > > > > > > > > I dunno if they default to that or we force that. We have had lots of > > > > problems with Linux NFS, we export our home directories but they are > > > > more or less read only. > > > > > > > > Maybe things have gotten better but back in the day I could crash the > > > > kernel with a bk clone to a NFS directory. > > > > > > Bug reports welcomed if any of those bugs are still around. > > > > The other thing to note is that at this point, NFSv2 has been legacy > > code for more than 10 years on Linux and is starting to suffer big time > > from bit rot. We should probably aim to remove it entirely in the next > > 1-2 years. There is no place in today's world for a protocol that can > > only deal with a 2GB maximum file size... > > Well, we support ancient machines (why? damn good question) that only > speak NFSv2 so it would sorta suck for us if you pulled it. At least on the server side, I'd prefer to be more conservative about removing NFSv2 support. --b. -- 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
