Comment 5 for bug 1322190

@john-griffith

As an example, any driver that rely on the locking decorators to provide mutual exclusion on accesses to their backend will suddenly find that doesn't work.

This is a relatively new feature and the sort of bugs it causes are the sort that only show up after lots of run-time. I'm sure some drivers will be absolutely fine, while others might not be, and it changes assumptions that were true at the time drivers were written... it will cause issues with LVM and a shared disk array for a concrete example, since nothing stops two managers trying to update the metadata at the same time, but that bug might not show up in basic testing.

I'm trying to think of a softer version of 'not supported / recommended', but can't come up with a good phrase.