IRP_MN_VERIFY_VOLUME

NTFSD
1

When the floppy is accessed across (before and after) the floppy
removal, the FS (here FASTFAT) gets the IRP_MN_VERIFY_VOLUME.
How does IO Manager detects the removal?

2

Read the source code for the floppy driver. You might want to read the
specifications for floppy controller chip. The floppy driver is composed of
floppy.sys and fdc.sys.

“Mani” wrote in message news:xxxxx@ntfsd…
> When the floppy is accessed across (before and after) the floppy
> removal, the FS (here FASTFAT) gets the IRP_MN_VERIFY_VOLUME.
> How does IO Manager detects the removal?
>
>
>

3

Search for DO_VERIFY_VOLUME in the DDK and source code for the
classpnp.sys( class.c ) and flpydisk.sys( floppy.c. )

“Mani” wrote in message news:xxxxx@ntfsd…
> When the floppy is accessed across (before and after) the floppy
> removal, the FS (here FASTFAT) gets the IRP_MN_VERIFY_VOLUME.
> How does IO Manager detects the removal?
>
>
>

4

When the floppy driver detects the possible removal (sometimes by timer),
it sets the DO_VERIFY_VOLUME bit in the device object and then starts to fail
the IO with STATUS_VERIFY_REQUIRED.
This forces the IO manager and the FSD to start the volume verification
procedure.

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

----- Original Message -----
From: “Mani”
Newsgroups: ntfsd
To: “Windows File Systems Devs Interest List”
Sent: Tuesday, May 30, 2006 8:14 AM
Subject: [ntfsd] IRP_MN_VERIFY_VOLUME

> When the floppy is accessed across (before and after) the floppy
> removal, the FS (here FASTFAT) gets the IRP_MN_VERIFY_VOLUME.
> How does IO Manager detects the removal?
>
>
>
> —
> Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com