Malc P
2013-01-04 08:36:37 UTC
Hi
We back up the database and loglogs to file (for reasons too
complicated to go into in detail), but last night due to an unforseen
blowup, the filesystem filled up and ISM then altered the backup paths
to "write proteced" status.
I fixed the main issue and the filesystem now has plenty of space
again but when I try to remount the paths as read/write (using ism_op -
mount <devname>) it still comes back as "write protected".
e.g. ism_show -volumes reports:
LOGLOGS ISMDiskLogs 588 GB full
11/04/12
...the 'full' obviously referring back to when the filesystem filled
up but now there's loads of space I want to be able use that specific
volume again. Any clues as to how I force ISM to do this?
TIA
Malc
We back up the database and loglogs to file (for reasons too
complicated to go into in detail), but last night due to an unforseen
blowup, the filesystem filled up and ISM then altered the backup paths
to "write proteced" status.
I fixed the main issue and the filesystem now has plenty of space
again but when I try to remount the paths as read/write (using ism_op -
mount <devname>) it still comes back as "write protected".
e.g. ism_show -volumes reports:
LOGLOGS ISMDiskLogs 588 GB full
11/04/12
...the 'full' obviously referring back to when the filesystem filled
up but now there's loads of space I want to be able use that specific
volume again. Any clues as to how I force ISM to do this?
TIA
Malc