On 04/05/10 09:59, Nicolas Williams wrote:
Will F. suggests that setting sync=barrier on /var should yield an
unsupported system. I'd be happy with that too.
In PSARC contexts, I generally prefer to avoid using words like
"supported" and "unsupported", since they are statements about the
likely future behavior of support personnel rather than direct promises
about the behavior of the system.
How about:
"Setting sync=barrier on the currently active root or /var filesystem
may result in out-of-spec behavior, application data loss and increased
vulnerability to replay attacks".
Another instance where sync=barrier could subtly cause trouble is for
any SMTP listener (sendmail or alternative). SMTP requires that the
receiver have the message in stable storage before sending the "ok" to
the sender, so that in the event of a crash, messages get duplicated
rather than dropped.
But, on the other hand, it seems like it might be clever to temporarily
set sync=barrier during package operations on a freshly-cloned alternate
BE -- if the package operation doesn't complete, you have to torch the
BE, anyway.
- Bill
_______________________________________________
opensolaris-arc mailing list
[email protected]
