Somehow this directory has appeared in a folder on NTFS drive (and it has
nothing to do with the “regular” volume info dir for that volume) and I
can’t enter it nor delete it (getting “access denied” all the time). Well, I
can’t do it directly. But if I map that folder over a network then I can
enter it or delete it. But! And this is what bothers me the most! I have a
filter on top of LanMan that for each successful create, before leaving
create dispatch, rolls synchronous IRP_MJ_QUERY_INFORMATION/FileNetworkInfo
IRP for the created file object and calls down with this IRP to LanMan to
get this info. And what I see in this case (and this is for “System Volume
Information” only) is that IoCallDriver returns with STATUS_PENDING making
me wait on the event associated with the IRP until the request is completed.
But this never happens! IRP never gets completed. LanMan is alive, I can
work with that network mapped drive (as long as I’m not touching that “SVI”
dir again). I’ve verified that IRQL is at PASSIVE_LEVEL when I do
IoCallDriver, so there must be something “special” about that directory in
combination with LanMan. Can anybody shed some light on what’s going on and
(most importantly) what can I do to avoid that hang?
TIA,
Vladimir
Vladimir,
You should not be deleting the “System Volume Information” directory.
This is a special directory used by many windows components to store
internal metadata. If the directory is not present, it is automatically
created by the mount manager when a volume is mounted. You can’t access
it because it only has a SYSTEM acl on it.
Neal Christiansen
Microsoft File System Filter Group
This posting is provided “AS IS” with no warranties, and confers no
rights.
From: Vladimir Chtchetkine [mailto:xxxxx@borland.com]
Sent: Saturday, February 15, 2003 1:49 PM
To: File Systems Developers
Somehow this directory has appeared in a folder on NTFS drive (and it
has nothing to do with the “regular” volume info dir for that volume)
and I can’t enter it nor delete it (getting “access denied” all the
time). Well, I can’t do it directly. But if I map that folder over a
network then I can enter it or delete it. But! And this is what bothers
me the most! I have a filter on top of LanMan that for each successful
create, before leaving create dispatch, rolls synchronous
IRP_MJ_QUERY_INFORMATION/FileNetworkInfo IRP for the created file object
and calls down with this IRP to LanMan to get this info. And what I see
in this case (and this is for “System Volume Information” only) is that
IoCallDriver returns with STATUS_PENDING making me wait on the event
associated with the IRP until the request is completed. But this never
happens! IRP never gets completed. LanMan is alive, I can work with that
network mapped drive (as long as I’m not touching that “SVI” dir again).
I’ve verified that IRQL is at PASSIVE_LEVEL when I do IoCallDriver, so
there must be something “special” about that directory in combination
with LanMan. Can anybody shed some light on what’s going on and (most
importantly) what can I do to avoid that hang?
TIA,
Vladimir
You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
>internal metadata. If the directory is not present, it is
automatically
created by the mount manager when a volume is mounted. You can’t
access
IIRC this is true for NTFS only.
Max
It’s there on FAT/FAT32 also - the system uses it to store restore data.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim
S. Shatskih
Sent: Thursday, February 27, 2003 12:49 PM
To: File Systems Developers
Subject: [ntfsd] RE: “System Volume Information” directory…
>internal metadata. If the directory is not present, it is
automatically
>created by the mount manager when a volume is mounted. You can’t
access
IIRC this is true for NTFS only.
Max
You are currently subscribed to ntfsd as: xxxxx@nryan.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
There is one other thing I forgot to mention. Having the mount manager
create the System Volume Information directory is something that is new
to Windows Server 2003. In XP and earlier it was the responsibility of
the applications that wanted to use this directory to make sure it
exists. A new API called RtlCreateSystemVolumeInformationFolder was
added to XP to make this task simpler.
Neal Christiansen
Microsoft File System Filter Group
This posting is provided “AS IS” with no warranties, and confers no
rights.
-----Original Message-----
From: Nicholas Ryan [mailto:xxxxx@nryan.com]
Sent: Thursday, February 27, 2003 12:57 PM
To: File Systems Developers
It’s there on FAT/FAT32 also - the system uses it to store restore data.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim
S. Shatskih
Sent: Thursday, February 27, 2003 12:49 PM
To: File Systems Developers
Subject: [ntfsd] RE: “System Volume Information” directory…
>internal metadata. If the directory is not present, it is
automatically
>created by the mount manager when a volume is mounted. You can’t
access
IIRC this is true for NTFS only.
Max
You are currently subscribed to ntfsd as: xxxxx@nryan.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com