Re: Regarding storage drivers.

Sorry Maxim.
I have confused a lot.
Below is the detailed description of the problem:
My mirror driver is a storage filter driver. It is legacy driver and
it belongs to filter Group. Its location in the windows storage stack is
below the File system and above the Volume manager. Basically its an upper
filter driver for Volume manager. It is interfacing
with File system and Volume manager.

We do two fundamental operations in this driver.Replication and access
control.
Access control makes sure that only the
source node can write to the disk and no one on the other node can write to
the disk. We achieve this functionality by using a global flag within our
driver. This flag blocks/allows all kinds of IRPs to be sent to the
lower layers. On the source node, once the disk is online, then IRPs are
passed down. If the disk is offline, then IRPs are blocked. However on the
remote disk, the IRPs are always blocked. Only the replicated content is sent
to the disk there by ensuring data integrity.

My issue is:

After creating a mirror drive when I plug in and plug out any pnp device(for
example : usb memory stick)
The mirror drive letter in the explorer window is missing when plugging out
the device.

Anaylsis:

IOCTL_MOUNTDEV_QUERY_DEVICE_NAME is passed by mount manager when it receives
the pnp notification.
Since our filter driver blocks all the IOCTLS in the target node this IOCTL
gets rejected and the drive letter goes missing in the explorer window.

When I tried supporting this IOCTL in my filter driver by passing it down to
the volume manager by drive becomes accessible which should not occur.
For passing the IOCTL down the stack I am modifying the global flag. Due to
this my mirror drive in the target node becomes accessible.
I have analysed the problem but have doubts in fixing it.
My mirror drive should not be accessible in the target node.
At the same time IOCTL_MOUNTDEV_QUERY_DEVICE_NAME should be processed by
mount manager for it to get the drive letters.
How can this be done.
Hope the problem is clear now.




"qwert" wrote:

there is plug and play notification to the mount manager during the arrival
of volume interface.
Is there any similar notification to mount manager when the volume
goes.(removal of pnp device)
The drive letter is missing in the explorer window.
when a open the disk management console and right click the volume for
properties it shows a messgae saying that there is an internal error and the
property window doesnt appear.

thanks in advance

"qwert" wrote:

Thank u Maxim.

I have problem.
I have a mirror filter driver which sits below filesystem driver and above
volume manager.I have a drive which is mirrored between 2 nodes.I make one as
source and the destination.The destination is controlled by my application.no
other application can access it.any IOCTL I send to the destination nodes
gets rejected as my application takes control of that drive.

when I insert a plug and play device to the destination node my mirror drive
is missing in the explorer window as the IOCTL
(IOCTL_MOUNTDEV_QUERY_DEVICE_NAME) send by my mount manager is being rejected.
when I supported the above IOCTL by just passing it thru my driver so that
volume manager takes care of it,now I see the my mirror drive in the explorer
window,but when I remove the plug and play device from the destination node
my drive is missing again.

Initially my mirror drive was missing when I plugged in the pnp device(for
example memory stick).Now after supporting the above IOCTL my mirror drive is
missing when I remove the pnp device.

Is there any thing I need to take care in my filetr drive.

Thaks in advance

"Maxim S. Shatskih" wrote:

when pnp manager detects a pnp device in the system.
which driver will respong to this IOCTL.Is it the partition
manager.partmanager.sys.
or volume manager?????

Volume manager - FtDisk or DmIo

For removable media, Disk or CdRom will respond.

I am I making any sense here.I am confused.who will respond to this IOCTL.

Volume manager.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@xxxxxxxxxxxxxxxx
http://www.storagecraft.com


.

Relevant Pages

  • Re: system just recoered from a serious error
    ... App/Device Driver File Name Manufacturer Help ... Network Card Supported Not Required Troubleshooter ... Local Disk 34% More Info ... Are there any yellow question marks in Device Manager? ...
    (microsoft.public.windowsxp.basics)
  • Re: Windows 2003 Server hangs at splash screen / acpitabl.dat afte
    ... using the most recent SATA RAID driver, the system came up and reported the ... By far the best method to restore your server is to ... If you failed to make a backup prior to ther upgrade, ... Remove the primary disk from your mirror set. ...
    (microsoft.public.windows.server.general)
  • Recovering a broken SNAP server?
    ... 00:00.0 Host bridge: ServerWorks GCNB-LE Host Bridge ... driver i2c-dev dummy driver registered. ... raid1: device hda2 operational as mirror 0 ...
    (comp.arch.storage)
  • Re: Recovering a broken SNAP server?
    ... Discovered primary peer bus 01 [IRQ] ... driver i2c-dev dummy driver registered. ... raid1: device hda2 operational as mirror 0 ...
    (comp.arch.storage)
  • Re: Virtual Monitor in VB.Net?
    ... But it's performance is simular to GDI BitBlt. ... the screen to a video, ... You can try SuperVNC, which support Mini-port driver. ...
    (microsoft.public.dotnet.languages.vb)