IRP_NOCACHE

Hi Write requests be forced to be non-cached by using the above
IRP flag and massaging the write buffer and data to be sector size
aligned? One reason is that if the request extends the file size
by doing this, I have seen NTFS.sys raise an exception STATUS_CANT_WAIT.
Is the above only valid as long as the file size is no modified?
If that is correct, should I flush and purge the cache for the last
block of data at the end of the file first, extend the file first,
then write the block (now within the file size), and then reset the
file size once the write is done?

Thanks
Steve

Please, search some recent post in this forum.
We’ve already discussed it two times in the last
month or two.

L.

----- Original Message -----
From: “Steve Goddard”
To: “Windows File Systems Devs Interest List”
Sent: Monday, November 29, 2004 8:17 PM
Subject: [ntfsd] IRP_NOCACHE

Hi Write requests be forced to be non-cached by using the above
IRP flag and massaging the write buffer and data to be sector size
aligned? One reason is that if the request extends the file size
by doing this, I have seen NTFS.sys raise an exception STATUS_CANT_WAIT.
Is the above only valid as long as the file size is no modified?
If that is correct, should I flush and purge the cache for the last
block of data at the end of the file first, extend the file first,
then write the block (now within the file size), and then reset the
file size once the write is done?

Thanks
Steve


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

Use explicit CcFlushCache instead.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

----- Original Message -----
From: “Steve Goddard”
To: “Windows File Systems Devs Interest List”
Sent: Monday, November 29, 2004 10:17 PM
Subject: [ntfsd] IRP_NOCACHE

Hi Write requests be forced to be non-cached by using the above
IRP flag and massaging the write buffer and data to be sector size
aligned? One reason is that if the request extends the file size
by doing this, I have seen NTFS.sys raise an exception STATUS_CANT_WAIT.
Is the above only valid as long as the file size is no modified?
If that is correct, should I flush and purge the cache for the last
block of data at the end of the file first, extend the file first,
then write the block (now within the file size), and then reset the
file size once the write is done?

Thanks
Steve


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