Another ISM query - remove "write protected" status
Malc P found ISM volumes marked write protected and full after a backup filesystem filled, even though space was freed; the volume's expiry date was in the past. Jason Harris suggested extending expiry with nsrmm -S ssid -e date, but doubted it would help since full is full and a new volume may be needed. He noted ISM treats disk like tape. Unresolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
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
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?
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
On Jan 4, 1:02 pm, Jason Harris <j...@jgharris.com> wrote: > 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!
On Friday, 4 January 2013 22:19:37 UTC+8, Malc P wrote: > On Jan 4, 1:02 pm, Jason Harris <j...@jgharris.com> wrote: > > > 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.