Date: Thu, 19 Jun 2003 02:40:19 -0400 (EDT) From: Jeff Roberson <jroberson@chesapeake.net> To: The Hermit Hacker <scrappy@hub.org> Cc: arch@freebsd.org Subject: Re: cvs commit: src/sys/fs/nullfs null.h null_subr.c null_vnops.c Message-ID: <20030619023935.W36168-100000@mail.chesapeake.net> In-Reply-To: <20030618202302.W51411@hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 18 Jun 2003, The Hermit Hacker wrote: > On Wed, 18 Jun 2003, Sheldon Hearn wrote: > > > On (2003/06/18 13:53), Poul-Henning Kamp wrote: > > > > > With that said, I will also add, that I will take an incredibly > > > dim view of anybody who tries to add more gunk in this area, and > > > that I am perfectly willing to derail unionfs and nullfs (or pretty > > > much anything else on the list above) if that is what it takes to > > > clean up the buffer cache. > > > > Makes sense. After all, these filesystems are only just now recovering > > from "we can fix these later" breakage introduced years ago. What's a > > few more years without 'em? :-) > > 'K, this kinda hurts ... there are a growing # of us that are actually > using unionfs and nullfs on production systems ... not small servers, but > several thousand processes with over 100 union mounts ... other then the > vnode leak stuff that David has been investigating, I've yet to see > anything that I would considering warranting the 'DO NOT USE / CAVEAT > EMPTOR' that is in the man pages ... :( > Yes, I also have great issue with breaking the stacking layers. Fixing the buffer cache should have no impact on them if this is done correctly. Lets please not try to break any more functionality. Cheers, Jeff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030619023935.W36168-100000>