Dhananjay Phadke
Guest
|
 Posted:
Wed Sep 07, 2005 10:23 pm Post subject:
RE: automounting snapshot volume (iSCSI) doesn't work with w |
|
|
It seems that the LDM changes the signature of the snapshot volume. Following
event was obvserved in the event log.
===================================================
Event Type: Warning
Event Source: PartMgr
Description:
Changing the disk signature of disk 2 because it is equal to the disk
signature of disk 1.
===================================================
Here, disk1 is original volume, disk2 is snapshot created on the iSCSI
target. The snapshot was reset/refreshed using target's management interface,
so it has same data as that of original volume. So LDM finds same "on-disk"
signature on both disk1 and disk2, and it changes signature of disk2.
If the mount manager (mountmgr) is using "on-disk" signature to look-up it's
database, it won't find the drive letter for the volume with new signature.
I suppose the mount manager behaviour is different after w2k3 SP1, because
before SP1 the drive letter for the snapshot volume (disk2) was restored
properly after reboot.
Any more clues?
Thanks,
Dhananjay
"Dhananjay Phadke" wrote:
| Quote: | Hi,
Here's a peculiar problem:
A iSCSI volume is mounted from windows 2003 SP1 server with MS initiator v2.0.
A snapshot (created on iSCSI target using management interface) for this
volume is also mounted from same host.
The snapshot is reset using the management interface to the iSCSI target.
When the host (initiator) is rebooted, it's not able to mount (assign drive
letter) the snapshot volume automatically, but the original volume gets a
drive letter.
Note that this works on w2k3 host without SP1 (initiator version is same).
Is automount of basic volumes disabled by SP1? Could this be the cause of
the problem mentioned above?
Thanks in advance for your answers.
Dhananjay
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in