Discussion:
Another ISM query - remove "write protected" status
(too old to reply)
Malc P
2013-01-04 08:36:37 UTC
Permalink
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
Malc P
2013-01-04 12:19:18 UTC
Permalink
Ah hold on - the expiry date on that volume is 11/4/2012, obviously in
the past.
OK; how do I reset an expiry date to a point in the future?
Jason Harris
2013-01-04 13:02:15 UTC
Permalink
Hi Malc,

You may be able to extend the volume by:
1. use ism_show -volume to get an ssid
2. use nsrmm -S ssid -e date to extend the expiry

I don't think it will solve your problem.

Full is full, I think you will need a new volume.

HTH,

Jason
Malc P
2013-01-04 14:19:37 UTC
Permalink
Post by Jason Harris
Full is full, I think you will need a new volume.
... but but but it's a disk file volume with 0.7Tb of space in it!
Jason Harris
2013-01-04 22:16:54 UTC
Permalink
Post by Malc P
Post by Jason Harris
Full is full, I think you will need a new volume.
... but but but it's a disk file volume with 0.7Tb of space in it!
All the problems and difficulties configuring and using ISM for back up to disk revolve around the fact that ISM thinks it's a tape.
Loading...