I’m issuing a non cached read using FltReadFile during pre-operation of a
cleanup.
This is during iostress. It is reading the file:
E:\stress\ole\saltstrs\stgsane\StrmTst
The passed in read length (buffer length) is 0x10000.
The passed in offset is 0.
FltReadFile returns a status of 0x00000080 (STATUS_ABANDONED or
STATUS_ABANDONED_WAIT_0) which passes NT_SUCCESS,
HOWEVER, the value returned in BytesRead is 0xfffff000.
All other parameters (file object, etc, appear to be normal.
Can someone explain how this can be happening and what is means?
Thanks,
Ken
Actually the status returned was a hex 0x00000050 not 80.
I also got a status return value of 0x00002690
In both cases the returned length is 0xFFFFF000
Ken
From: Ken Galipeau [mailto:xxxxx@emc.com]
Sent: Thursday, February 10, 2005 10:51 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Strange return from FltReadFile
I’m issuing a non cached read using FltReadFile during pre-operation of a
cleanup.
This is during iostress. It is reading the file:
E:\stress\ole\saltstrs\stgsane\StrmTst
The passed in read length (buffer length) is 0x10000.
The passed in offset is 0.
FltReadFile returns a status of 0x00000080 (STATUS_ABANDONED or
STATUS_ABANDONED_WAIT_0) which passes NT_SUCCESS,
HOWEVER, the value returned in BytesRead is 0xfffff000.
All other parameters (file object, etc, appear to be normal.
Can someone explain how this can be happening and what is means?
Thanks,
Ken
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com