:> No I want mfs to grow and shrink its filesystem dynamically.
:MFS has never done so.  MFS is simply a UFS which uses (swap-backed)
:memory instead of a physical disk; it relies on the filesystem to
:avoid touching blocks that it doesn't need, and on the VM system to
:avoid wasting memory on allocated-but-untouched address space.
:Historically, MFS would waste time copying disk blocks twice on their
:way to the user, but I think this may have been fixed by Matt Dillon.

    Both MFS and VN have the ability to dynamically allocate and free
    their swap backing store.

    However, due to limitations in the way filesystems 'free' blocks,
    only 'full block frees' can be returned to the system.  Since
    files often contain fragments, neither MFS or VN can fully free
    the backing store related to a file.  At a minimum the inode and
    bitmap blocks will always remain persistent, and filesystem blocks
    used to store file fragments will tend to remain persistent even
    when the underlying files have been deleted.


    MFS is very inefficient.  I didn't fix that... it isn't possible to
    fix it without a lot of work.  Data must still be copied twice.  Even
    worse, data is cached twice in the system rather then once, so the
    active data set is bloated over what it could be.

    VN and MD do not have this problem.  Poul is working on integrating
    the feature of VN, MFS, and MD all into MD.

    The VN device is probably one's best bet on sharing swap efficiently
    with a temp filesystem.

    That said, I do *NOT* recommend any sort of temp/swap sharing, because
    it makes for a very fragile system.  If anything fills up swap, your
    temp filesystem is screwed.  If anything fills up your temp filesystem,
    your swap is screwed.  Bad news all around.  Today's hard drives are
    large enough that you should keep them separate.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to