🚀 go-pugleaf

> In addition to the fact that for me at least, an SFS is a lot easier to
> deal with than the 10,000 minidisks that I have now,

The issue at hand isn't the disk space for thousands of users, but for
one service DVM.  I.e., one virtual disk to define and then leave in
place "forever".

> limits can be set
> on a per user basis as to how much space can be used.

Question: does the SFS *guarantee* that the sum of per-user limits is
less than or equal to the actual size of the available disk space?  If
not, does SFS allow a given quota to be dedicated to a given user so
that it's always available, no matter what other users do?  If not, then
Mailer should not be stuffed into a storage pool with other users.

> So preserving the
> concept of a maximum mail file size can not only be used with SFS, but
> it can also be set to a finer granularity since you allocate SFS space
> in 4k blocks rather than in whole cylinders.

The point is not to limit the size of mail file that a user can send
(by restricting Mailer's disk space), but to set aside *enough* disk
space to guarantee that Mailer can handle the largest file that might
be expected to hit it.  I don't think I need to dwell on the horrors
of what happens when a file arrives that is ever so slightly too big!
I would far rather round up to the next whole cylinder than risk
being short by a few Kbytes.
                                       John