Re: kernel BUG at /build/buildd/linux-3.2.0/fs/lockd/clntxdr.c:226!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2012-10-15 at 04:05 -0400, George Spelvin wrote:
> Trond.Myklebust@xxxxxxxxxx wrote:
> > 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...
> 
> Today's world includes a lot of yesterday's world.
> 
> I'm still running a SunOS 4.1.4 machine.  Yes, it does real (dusty
> deck) work; I just had to resurrect it when its HDD died.
> 
> I got to rediscover its 2 GB maximum FILESYSTEM size.
> 
> (When the hardware finally craps out for real, I'll probably
> punt to QEMU.  But I either have to add SunOS system call
> emulation to QEMU, or run the whole OS under hardware emulation.)
> 
> Anyway, most of its files are actually on a Linux NFS server
> with a proper RAID and backup system.
> 
> I'd kind of like to keep NFSv2 working, if you don't mind.
> 
> ("I do mind; install unfsd" is perhaps a legitimate response.)

I do mind; it is clearly starting to bitrot due to an absence of users.
Maintenance of unused code is actually _more_ of a pain, not less.

So unfsd is one solution. Keeping a VM with an older version of the
Linux kernel that still supports NFSv2 is another. Volunteering to
maintain the code is a third.

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com
��.n��������+%������w��{.n�����{��w���jg��������ݢj����G�������j:+v���w�m������w�������h�����٥



[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux