I concur wholeheartedly with this assessment. My only concern was the
XSan might try to reinitialize the lun. Having contacted Apple XSan
support, would you agree that I should wait to hear that they say?
James
On Apr 8, 2006, at 4:38 PM, email@hidden wrote:
You need to rename the metadata LUN using the command line tools
back to the name of the original metadata LUN.
I forgot the name of the utility. It's something like cvname or
something along those lines. The LUN attributes need to be the
exact same as they were before. I think you can find that
information in the config file for Xsan (where you can see the LUN
names, or at least what they were suppose to be before the LUN
become unlabled).
After renaming the LUN, you can then go back and do a cvfsck. Make
sure to recover the journal first doing a cvfsck -j, and then do a
cvfsck -v (verbose) to see what's happening.
If you have Xsan support, I would suggest calling them, as the
LUN's becoming unlabled after a crash is not an unknown problem.
Hope this helps,
Jason
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xsan-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xsan-users/email@hidden
