Windows mounting volumes that it already thinks it owns is a known issue with M$FT. Windows looks for the volume descriptor any time a volume is attached. When it sees one that it knows about it will not allow it to be mounted (although you might get by trying to force mount it under a mount point (i,e, c:\mnt\ ). As far as alternate host mounting, you can do a couple of things. Before attaching any of your LUNS to the new host, fire up diskpart.exe and tell it to automount disable. This will prevent the host from pulling in and asssigning drive letters to volumes. Then attach your volumes, and assign drive letters to the volumes manually. These will be persistant. To really make all this work properly you will need to develop some scripting to flush the disk buffers on the original host, initiate the snapshot, and then allow access to the snapshot from the mount host. It can be done. If/when OF gets FC connectivity, it will need this level of functionality to compete in the market space as everyone else are offering helper apps to handle that functionality.
Jason > > > ------------------------------ > > Message: 5 > Date: Sat, 18 Aug 2007 13:01:16 +0200 > From: "Peter Van Eeckhoutte" <[EMAIL PROTECTED]> > Subject: [OF-users] mounting snapshots in Windows : drive letter > conflicts ? > To: <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; format=flowed; charset="iso-8859-1"; > reply-type=original > > After playing for a while with openfiler and the snapshot functionality, I > stumbled across this problem > > I scheduled a snapshot on one of my luns. This lun is mounted as drive G: > on my windows server, via the Microsoft ISCSI Initiator. Works great. > > I want to mount the snapshot lun, so I edited /etc/ietd.conf (because the > GUI doesn't seem to include a way to do this. It allows you to 'share' the > snapshot, but does not allow to do so over iSCSI) > > part of ietd.conf file : > > Target iqn.2006-01.com.openfiler:storage3.lun3 > Lun 0 Path=/dev/storage3/lun3,ScsiSN=CZklf2-quoJ,Type=fileio > > #added manually > Target iqn.2006-01.com.openfiler:storage3ss.lun3 > Lun 0 Path=/dev/storage3/of.snapshot.lun3.sched0,Type=fileio > > > restarted iscsi-target, and the snapshot lun becomes visible in MS iSCSI > initiator, but I cannot mount the lun on the same system that has the > original lun3 mounted as drive G: > So I connected to the snapshot lun from another system, and I could > connect > just fine... but it mounted the snapshot lun as drive G:, so I guess > that's > the reason why I couldn't mount it on the original windows server. (drive > letter conflict ?) > > So what are my options ? I want to have one system that is responsible > for > backing up all of my snapshots. (I have 3 lun's, 2 of them are mounted > as > drive D: on 2 different systems, 1 is mounted as drive G:) > So I'd like to be able to mount the snapshots on one system, and have some > sort of control over the drive letter that will be assigned. > Any ideas ? > > thanks > > P > > > > > >
_______________________________________________ Openfiler-users mailing list [email protected] https://lists.openfiler.com/mailman/listinfo/openfiler-users
