They're the dominant carrier in my area, so these sorts of screwups make me nervous. I can't easily avoid using them without a fair amount of inconvenience.
They're the dominant carrier in my area, so these sorts of screwups make me nervous. I can't easily avoid using them without a fair amount of inconvenience.
This is a long-standing issue with zvols which affects overall system stability, and has no real solution as of yet.
It's also not as easy as GB/s/core, since cores aren't entirely uniform, and data access may be across core complexes.
That's worth explaining: it's automated code deletion, but the owner of the code (a committer to that directory hierarchy) must approve it, so it's rare there's ever a false deletion.
Logs are always generated, and logs include some amount of data about the user, if only environmental.
It's quite plausible that the spellchecker does not store your actual user data, but information about the request, or error logging includes more UGC than intended.
Note: I don't have any insider knowledge about their spellcheck API, but I've worked on similar systems which have similar language for little more than basic request logging.