STATUS_REPARSE

Hi,
Can anybody please explain the meaning of STATUS_REPARSE ?
I am getting this return value for IRP_MJ_CREATE is issued immediately after
ejecting and then re-inserting the floppy into the drive.
After ejecting the floppy, I had got return value denoting disk error.
I reinserted the floppy and again tried to refresh the listing of files in
NT explorer. The first IRP_MJ_CREATE returned STATUS_REPARSE. Next
IRP_MJ_CREATE got STATUS_SUCCESS.

Thanks in advance.

Josie

Joseph,

This means the FSD detected that the media changed by pinging the underlying
storage driver stack. In this scenario, the FSD returns STATUS_REPARSE to
the “IO Manager,” or “IOM,” to tell the IOM to re-parse the file path. This
causes the IOM to re-traverse the VPB thereby finding the new FSD device
that represents the new media. The IOM then re-issues the create IRP with
the new parameters.

There are actually two flavors of STATUS_REPARSE. If the FSD sets
irp->IoStatus.Information to IO_REPARSE and replaces the file object in the
IO stack location, then the IOM will re-parse the entire path. This is
useful for implementing symbolic links, and is demonstrated in a reparse
sample in the NT 4.0 DDK.

If the FSD requests the other flavor of STATUS_REPARSE by specifying
IO_REMOUNT in irp->IoStatus.Information, then the IOM will simply
re-traverse the VPB instead of parsing the entire path. This is
demonstrated in the sample file systems included with the IFS Kit. This is
the type of STATUS_REPARSE you’re observing.

Regards,

Rob

-----Original Message-----
From: Joseph _Arun [mailto:xxxxx@BBV.Satyam.com]
Sent: Thursday, April 20, 2000 6:29 AM
To: File Systems Developers
Subject: [ntfsd] STATUS_REPARSE

Hi,
Can anybody please explain the meaning of STATUS_REPARSE ?
I am getting this return value for IRP_MJ_CREATE is issued immediately after
ejecting and then re-inserting the floppy into the drive.

After ejecting the floppy, I had got return value denoting disk error.
I reinserted the floppy and again tried to refresh the listing of files in
NT explorer. The first IRP_MJ_CREATE returned STATUS_REPARSE. Next
IRP_MJ_CREATE got STATUS_SUCCESS.

Thanks in advance.

Josie

*cough*

Sorry in my haste, I said, “replaces the file object in the IO stack
location,” in the second paragraph. I meant, “replaces the filename in the
file object in the IO stack location.”

-----Original Message-----
From: Rob Fuller
Sent: Thursday, April 20, 2000 10:23 AM
To: ‘File Systems Developers’
Subject: RE: [ntfsd] STATUS_REPARSE

Joseph,

This means the FSD detected that the media changed by pinging the underlying
storage driver stack. In this scenario, the FSD returns STATUS_REPARSE to
the “IO Manager,” or “IOM,” to tell the IOM to re-parse the file path. This
causes the IOM to re-traverse the VPB thereby finding the new FSD device
that represents the new media. The IOM then re-issues the create IRP with
the new parameters.

There are actually two flavors of STATUS_REPARSE. If the FSD sets
irp->IoStatus.Information to IO_REPARSE and replaces the file object in the
IO stack location, then the IOM will re-parse the entire path. This is
useful for implementing symbolic links, and is demonstrated in a reparse
sample in the NT 4.0 DDK.

If the FSD requests the other flavor of STATUS_REPARSE by specifying
IO_REMOUNT in irp->IoStatus.Information, then the IOM will simply
re-traverse the VPB instead of parsing the entire path. This is
demonstrated in the sample file systems included with the IFS Kit. This is
the type of STATUS_REPARSE you’re observing.

Regards,

Rob

-----Original Message-----
From: Joseph _Arun [mailto:xxxxx@BBV.Satyam.com]
Sent: Thursday, April 20, 2000 6:29 AM
To: File Systems Developers
Subject: [ntfsd] STATUS_REPARSE

Hi,
Can anybody please explain the meaning of STATUS_REPARSE ?
I am getting this return value for IRP_MJ_CREATE is issued immediately after
ejecting and then re-inserting the floppy into the drive.

After ejecting the floppy, I had got return value denoting disk error.
I reinserted the floppy and again tried to refresh the listing of files in
NT explorer. The first IRP_MJ_CREATE returned STATUS_REPARSE. Next
IRP_MJ_CREATE got STATUS_SUCCESS.

Thanks in advance.

Josie

STATUS_REPARSEAn to refine this alittle more, I suspect you ment the
filename in the file object, not in the IO stack location; semantics :slight_smile:
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Rob Fuller
Sent: Thursday, April 20, 2000 8:25 AM
To: File Systems Developers
Subject: [ntfsd] RE: STATUS_REPARSE

*cough*

Sorry in my haste, I said, “replaces the file object in the IO stack
location,” in the second paragraph. I meant, “replaces the filename in the
file object in the IO stack location.”
-----Original Message-----
From: Rob Fuller
Sent: Thursday, April 20, 2000 10:23 AM
To: ‘File Systems Developers’
Subject: RE: [ntfsd] STATUS_REPARSE

Joseph,

This means the FSD detected that the media changed by pinging the
underlying storage driver stack. In this scenario, the FSD returns
STATUS_REPARSE to the “IO Manager,” or “IOM,” to tell the IOM to re-parse
the file path. This causes the IOM to re-traverse the VPB thereby finding
the new FSD device that represents the new media. The IOM then re-issues
the create IRP with the new parameters.

There are actually two flavors of STATUS_REPARSE. If the FSD sets
irp->IoStatus.Information to IO_REPARSE and replaces the file object in the
IO stack location, then the IOM will re-parse the entire path. This is
useful for implementing symbolic links, and is demonstrated in a reparse
sample in the NT 4.0 DDK.

If the FSD requests the other flavor of STATUS_REPARSE by specifying
IO_REMOUNT in irp->IoStatus.Information, then the IOM will simply
re-traverse the VPB instead of parsing the entire path. This is
demonstrated in the sample file systems included with the IFS Kit. This is
the type of STATUS_REPARSE you’re observing.

Regards,

Rob

-----Original Message-----
From: Joseph _Arun [mailto:xxxxx@BBV.Satyam.com]
Sent: Thursday, April 20, 2000 6:29 AM
To: File Systems Developers
Subject: [ntfsd] STATUS_REPARSE

Hi,
Can anybody please explain the meaning of STATUS_REPARSE ?
I am getting this return value for IRP_MJ_CREATE is issued immediately
after ejecting and then re-inserting the floppy into the drive.

After ejecting the floppy, I had got return value denoting disk error.
I reinserted the floppy and again tried to refresh the listing of
files in NT explorer. The first IRP_MJ_CREATE returned STATUS_REPARSE. Next
IRP_MJ_CREATE got STATUS_SUCCESS.

Thanks in advance.

Josie

Hi Rob and Jamey,
Thanks a lot for the information.
Josie


From: Rob Fuller
Reply To: File Systems Developers
Sent: Thursday, April 20, 2000 8:53 PM
To: File Systems Developers
Subject: [ntfsd] RE: STATUS_REPARSE

Joseph,

This means the FSD detected that the media changed by pinging the
underlying storage driver stack. In this scenario, the FSD returns
STATUS_REPARSE to the “IO Manager,” or “IOM,” to tell the IOM to re-parse
the file path. This causes the IOM to re-traverse the VPB thereby finding
the new FSD device that represents the new media. The IOM then re-issues
the create IRP with the new parameters.

There are actually two flavors of STATUS_REPARSE. If the FSD sets
irp->IoStatus.Information to IO_REPARSE and replaces the file object in
the IO stack location, then the IOM will re-parse the entire path. This
is useful for implementing symbolic links, and is demonstrated in a
reparse sample in the NT 4.0 DDK.

If the FSD requests the other flavor of STATUS_REPARSE by specifying
IO_REMOUNT in irp->IoStatus.Information, then the IOM will simply
re-traverse the VPB instead of parsing the entire path. This is
demonstrated in the sample file systems included with the IFS Kit. This
is the type of STATUS_REPARSE you’re observing.

Regards,

Rob

-----Original Message-----
From: Joseph _Arun [mailto:xxxxx@BBV.Satyam.com]
Sent: Thursday, April 20, 2000 6:29 AM
To: File Systems Developers
Subject: [ntfsd] STATUS_REPARSE

Hi,
Can anybody please explain the meaning of STATUS_REPARSE ?
I am getting this return value for IRP_MJ_CREATE is issued
immediately after ejecting and then re-inserting the floppy into the
drive.

After ejecting the floppy, I had got return value denoting disk
error.
I reinserted the floppy and again tried to refresh the listing of
files in NT explorer. The first IRP_MJ_CREATE returned STATUS_REPARSE.
Next IRP_MJ_CREATE got STATUS_SUCCESS.

Thanks in advance.

Josie

I don’t think so… “replaces the filename in the file object in the IO stack
location.” looks good to me (atmost refined to “current IO stack location”).

Originally he said: “replaces the file object in the IO stack location”
which is grossly wrong, since FO remains the same, just the full-path needs
to be reparsed.

I have never checked this, but the IO manger might allocate a new FO in
response to this REPARSE request (just might, no reason to actually do so,
since same FO can be used… well not sure about that either… ). FSD cannot
change the FO on its own.

Shweta.

An to refine this alittle more, I suspect you ment the filename in the file
object, not in the IO stack location; semantics :slight_smile:
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Rob Fuller
Sent: Thursday, April 20, 2000 8:25 AM
To: File Systems Developers
Subject: [ntfsd] RE: STATUS_REPARSE

*cough*

Sorry in my haste, I said, “replaces the file object in the IO stack
location,” in the second paragraph. I meant, “replaces the filename in the
file object in the IO stack location.”
-----Original Message-----
From: Rob Fuller
Sent: Thursday, April 20, 2000 10:23 AM
To: ‘File Systems Developers’
Subject: RE: [ntfsd] STATUS_REPARSE

Joseph,

This means the FSD detected that the media changed by pinging the underlying
storage driver stack. In this scenario, the FSD returns STATUS_REPARSE to
the “IO Manager,” or “IOM,” to tell the IOM to re-parse the file path. This
causes the IOM to re-traverse the VPB thereby finding the new FSD device
that represents the new media. The IOM then re-issues the create IRP with
the new parameters.

There are actually two flavors of STATUS_REPARSE. If the FSD sets
irp->IoStatus.Information to IO_REPARSE and replaces the file object in the
IO stack location, then the IOM will re-parse the entire path. This is
useful for implementing symbolic links, and is demonstrated in a reparse
sample in the NT 4.0 DDK.

If the FSD requests the other flavor of STATUS_REPARSE by specifying
IO_REMOUNT in irp->IoStatus.Information, then the IOM will simply
re-traverse the VPB instead of parsing the entire path. This is
demonstrated in the sample file systems included with the IFS Kit. This is
the type of STATUS_REPARSE you’re observing.

Regards,

Rob

-----Original Message-----
From: Joseph _Arun [mailto:xxxxx@BBV.Satyam.com]
Sent: Thursday, April 20, 2000 6:29 AM
To: File Systems Developers
Subject: [ntfsd] STATUS_REPARSE

Hi,
Can anybody please explain the meaning of STATUS_REPARSE ?
I am getting this return value for IRP_MJ_CREATE is issued immediately after
ejecting and then re-inserting the floppy into the drive.

After ejecting the floppy, I had got return value denoting disk error.
I reinserted the floppy and again tried to refresh the listing of files in
NT explorer. The first IRP_MJ_CREATE returned STATUS_REPARSE. Next
IRP_MJ_CREATE got STATUS_SUCCESS.

Thanks in advance.

Josie


FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup