Formatting & checking failed

Hi all,

I have a driver for NT4 that creates a drive letter symbolic link and
redirect the read/write access to network. The normal read/write accesses
works fine. But when I tried to format it in command prompt, I got error
message of “Error in IOCTL call”. Further more, when I tried to run chkdsk
on this drive letter, I got error message of “Cannot open volume for direct
access”.

What’s the IOCTL calls that a driver must support in order to support
format/chkdsk? I searched the DDK doc but it seems nowhere explains this.
There are a bunch of IOCTL_DISK_??? defined in NTDDDISK.H, but I guess it’s
not neccessary to support all of them. Am I right?

I am also required to support W2K in the future. Is there any differences
between NT and W2K on format/chkdsk issue? Thanks a lot.

Regards,
Mike


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You must support the partition calls; even if you must fake them.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of
xxxxx@3com.com
Sent: Monday, April 16, 2001 4:27 PM
To: NT Developers Interest List
Subject: [ntdev] Formatting & checking failed

Hi all,

I have a driver for NT4 that creates a drive letter symbolic link and
redirect the read/write access to network. The normal read/write accesses
works fine. But when I tried to format it in command prompt, I got error
message of “Error in IOCTL call”. Further more, when I tried to
run chkdsk
on this drive letter, I got error message of “Cannot open volume
for direct
access”.

What’s the IOCTL calls that a driver must support in order to support
format/chkdsk? I searched the DDK doc but it seems nowhere explains this.
There are a bunch of IOCTL_DISK_??? defined in NTDDDISK.H, but I
guess it’s
not neccessary to support all of them. Am I right?

I am also required to support W2K in the future. Is there any differences
between NT and W2K on format/chkdsk issue? Thanks a lot.

Regards,
Mike


You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

> What’s the IOCTL calls that a driver must support in order to support

format/chkdsk? I searched the DDK doc but it seems nowhere explains this.
There are a bunch of IOCTL_DISK_??? defined in NTDDDISK.H, but I guess
it’s
not neccessary to support all of them. Am I right?

IOCTL_DISK_xxx are all mandatory for a block device.
Also the following must work:

  • opening a drive letter with zero-length pathname must open the underlying
    block device
    for DASD access which will bypass the filesystem.

Max


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com