Yes Matthew I think this is what is happing. On Aug 28, 2014, at 10:07 AM, Matthew Zito <matt@xxxxxxxxxxxxxxxxx> wrote: > Remember, it's ASM, so there's no mounting or unmounting! > > Changing the permissions *might* work, but on Linux, since you still do an > open() and get a file descriptor even when you're doing direct I/O, I think > it would bypass it if the database is already running (since it already has a > valid FD it's writing to/from). > > > > On Thu, Aug 28, 2014 at 1:03 PM, Mark W. Farnham <mwf@xxxxxxxx> wrote: > If this is Linux or Unix, then probably umount followed by a mount readonly > would do the trick if you’re writing to that disk at all. > > > > Possibly changing the permissions would intervene, but I think that varies > about whether that will stop a running application that already has a file > open. > > > > Heh. It was easier when there was a button on each drive you could toggle to > make it read only. > > > > >