Why is this necessary? Filesystem drivers should be attached to partitions,
not to entire disks. My understanding of the storage stack is nothing
compared to a lot of people on this list, but I believe at least this much
is true.
-- arlie
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@attotech.com
Sent: Tuesday, August 09, 2005 10:32 AM
To: Windows File Systems Devs Interest List
Subject: SPAM-LOW: [ntfsd] Non-standard partitioning schemes
Gurus,
I'm experimenting with an FSD based on Fastfat. The problem is that the FS
uses a non-MBR, non-GPT based partitioning scheme, so when the drive is
attached, the I/O Manager doesn't see any partitions and therefore never
sends my driver IRP_MN_MOUNT_VOLUME. (I was assuming that for unknown
partition schemes, I/O Manager would just try to mount the entire physical
disk. This does not appear to be the case.) The only solution I can think
of to this problem is to write a lower filter for disk.sys, and fake an
MBR-style partition based on the actual partition information. This seems a
bit extreme, however, and it would probably break if some other driver
similarly filters the disk. Is there any other approach that is safer
and/or easier to implement?
TIA,
Jason
Questions? First check the IFS FAQ at
You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ''
To unsubscribe send a blank email to xxxxx@lists.osr.com