Author: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
Date: Mon, 4 Jun 2012 10:42:21 -0400
A recent SAN system upgrade sort-of killed 19TB of storage volumes, making them "read only". Since we are having pathing issues, plus we need to perform fsck on these volumes due to the journal being
Author: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
Date: Mon, 4 Jun 2012 11:01:54 -0400
Thanks. That pretty much confirms that OFFLINE is useless to me since I don't want to loose the data, if at all possible. 19TB is a lot to restore from dozens of offsite tapes. Zoltan Forray TSM Soft
Author: Rick Harderwijk <rick.harderwijk AT GMAIL DOT COM>
Date: Mon, 4 Jun 2012 16:57:59 +0200
clicked send to soon.... I believe it does not do anything to the files on the volumes, it just tells TSM that it cannot access the files. I think it will generate errors when trying to move/copy fil
Author: Shawn Drew <shawn.drew AT AMERICAS.BNPPARIBAS DOT COM>
Date: Mon, 4 Jun 2012 11:28:37 -0400
Just remember, "status" and "access" are 2 different things. You can set the access to "unavailable", but that has nothing to do with the status of a volume. The status is not set with "upd volume" a
Author: Rick Harderwijk <rick.harderwijk AT GMAIL DOT COM>
Date: Mon, 4 Jun 2012 16:54:58 +0200
Zoltan, Update volume wherestatus=offline would mean to do something to volumes that have a status of offline. I'd think you would have to use update volume * access=unavailable wherestgpool=<SANSTGV
Author: "Huebner,Andy,FORT WORTH,IT" <Andy.Huebner AT ALCONLABS DOT COM>
Date: Mon, 4 Jun 2012 13:46:05 -0500
If it helps, we have taken random volumes off-line when an array restart was required. We also had our AIX admin unmount the volumes. Once the array was on-line we reversed the changes and all was go