On Mon, Nov 3, 2008 at 4:09 PM, Huegel, Thomas <[EMAIL PROTECTED]> wrote:
> After all one would never do a SIO without following it with a TIO... Like many analogies, this one stretches it. I decided to ignore Chuckie's unsolicited Education on Programming, blaming it on Halloween. When we're into the "there is no problem because there is no solution" mode, then there is little value in further contribution to global warming. Since that part of CMS is OCO I can't argue the complexity of such a solution, and it may be that it would only address a small percentage of the cases. It's not SFS stability, but probably more a matter of (lack of) operating procedures. I know of no storage admin person who would simply take a volume away when it is in use. But I know several who would simply let an SFS server fill up or restart it to update a configuration file. I avoid using remote file pools for service machines etc, but use a file pool that runs on the same system. This ensures that a system can run on its own without needing its sibling. It also works out well because such service machines tend to run on each system and this way you keep their stuff apart. And you're still able to access the data from another VM system for non-critical purposes. -Rob
