CASTalk.com

rbassett99 · Guest

Summary: if a shared partition resides on a disk that is "late" arriving,
then lanmanserver will not present the share, even after the disk arrives.
Net stop lanmanserver, net start lanmanserver is sufficient to have the newly
arrived share presented.

Question: is there something less severe to have lanmanserver notice the
disk partition's arrival?

To demonstrate: My example here uses iSCSI, although I imagine this will
happen any time a disk arrives well after bootup (for example, a hot
pluggable disk is plugged in and a Rescan Disks brings it back into LDM).
There is an iSCSI target host (ISCSITARGET), a client (CLIENT), and a 3rd
machine accessing the share on CLIENT.

ISCSITARGET:
Configure a 200GB logical unit.
Map the logical unit to CLIENT.

CLIENT:
Installed iSCSI initiator 1.06.
Open iSCSI initiator control panel.
Target Portals, Add..., ISCSITARGET.
Available Targets, Select ISCSITARGET, Log on, tick "automatically restore
at reboot", OK
Verify you're connected in Active Sessions.
Open Computer Management
Select Storage, Disk Management.
Rescan Disks, see the 200GB iSCSI disk.
Create Partition, Extended Partition, keep default maximum size 200GB, Finish.
New Logical Drive, Partition Size 1024MB, E:, NTFS, Quick Format
Right-click E:\, Properties, Sharing, New Share..., "SHARE", OK

THIRDHOST:
dir \\CLIENT\SHARE works, no files found
echo hello >\\client\share\hello.txt works

CLIENT:
Reboot CLIENT.
Wait for CLIENT to come back up.
Log in to CLIENT.
Verify that connection to 200GB iSCSI was restored and that E:\ is present.
Right-click E:\, Properties, Sharing, now says not shared.

THIRDHOST:
dir \\client\share fails, "The network name cannot be found."

CLIENT:
net stop lanmanserver (other services will be stopped too)
net start lanmanserver (and then start up other services, too)

THIRDHOST:
dir \\client\share works, shows hello.txt

(end)

Thanks,
Robert Bassett

rbassett99 · Guest

Perhaps the iSCSI scenario is not the best demostration. The iSCSI release
notes describe setting a dependency of lanmanserver on msiscsi. This will
ensure that the iSCSI disks are all 'started' before lanmanserver goes
through them to present shares from them.

However, the original question I posted is more general than the specific
iSCSI illustration. In general, when a disk arrives after lanmanserver has
started, is there a way to have lanmanserver notice without net stop/net
start? (Something like a "rescan shares" for lanmanserver, complementary to
"rescan disks" for Disk Management?)

	CASTalk.com Forum Index -> Storage System	All times are GMT
Page 1 of 1