Re: cvs commit: src/sys/fs/nullfs null.h null_subr.c null_vnops.c

From: The Hermit Hacker (scrappy_at_hub.org)
Date: 06/19/03

  • Next message: Tim J. Robbins: "Re: cvs commit: src/sys/fs/nullfs null.h null_subr.c null_vnops.c" 
    Date: Wed, 18 Jun 2003 20:28:37 -0300 (ADT)
To: Sheldon Hearn <sheldonh@starjuice.net>

    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 ... :(
    _______________________________________________
    freebsd-arch@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-arch
    To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"

  • Next message: Tim J. Robbins: "Re: cvs commit: src/sys/fs/nullfs null.h null_subr.c null_vnops.c"