Cmd View eva / spmgr disagree

[David G Ledger]

I have a Vdisk (...-0157-...) that has been presented to hosts A and B; and mounted on one or the other at different times. It has been un-presented from host B, where it had been presented as Lun 5

Another vdisk (created as a snapshot, ...-01b7-...) has been presented as Lun 5 to host B. The Command View eva GUI and reports generated using SSSU confirm that this is the case.

However, 'spmgr display' on host B reports that the WWlunID on Lun 5 is ...-0157-... not ...-01b7-...

If the second (...-01b7-...) Vdisk is un-presented to host B, 'spmgr display' on host B reports that Lun 5 still has ...-0157-..., but with a '****FAILED' status. Controller & Path_Instance values are the same in each case. No data from spmgr seems to refer to the Vdisk that the eva says is presented on Lun 5.

Attempts to mount the device on Lun 5 give "unrecognized file system" while the second Vdisk is presented, which is what highlighted the problem.

I am investigating Snapshot mounts, so the is not something which has worked before.

While the first Vdisk was presented to both hosts, another Vdisk was presented to host B as Lun 6, and is still there, so Luns 1-4 & 6 are permanent through all this.

Ideas and pointers please.

David

[Wayne Green]

David,

Did you get a resolution to this. I am seeing the same problem when presenting a snapclone to the same host to run a backup. When I repeat the process spmgr still shows the first snapclone WWLUNID for that device. Unpresenting it still shows the original WWLUNID as FAILED. Bit of a problem when I'm trying to script it all.

I am thinking after unpresenting the original I will have to run a spmgr delete WWLUNID.

[David Ledger_1]

Replying to Wayne Green

I ended up just using spmgr to delete the old paths. I get the impression that it's up to us to keep things consistent, not the system.

I too was scripting a snapshot sequence, and I got it to work for basic non-LVM raw volumes. Not sure if LVM gives you anything when using a SAN (it's on my list of questions for HP World), but it certainly makes snapshot scripting more complex. That's as far as I got when we discovered the educational discount on the HP s/w for the job (it was at a university).

David