re: File Write / possible failure/corruption
- From: "Sue Loh [MS]" <sloh@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 16 Aug 2005 09:22:01 -0700
The object store file system has four 4k temporary buffers it uses as a write-back cache. It won't write back until you call FlushFileBuffers, close the file, or touch enough other file data that the cache buffers get evicted. To be safe you probably should call FlushFileBuffers after you write.
Sue
sloh@xxxxxxxxxxxxx (remove "online" from reply-to address)
Now writing to a different blog!
http://blogs.msdn.com/ce_base/
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no rights.
_____________________________________________________________
-----Original Message-----
From: Roopak@xxxxxxxxxxxxxxxxxxxxxxxxx
Posted At: Friday, August 05, 2005 2:16 AM
Posted To: microsoft.public.windowsce.app.development
Conversation: File Write / possible failure/corruption
Subject: File Write / possible failure/corruption
Hi, we have developed an application(a simple database) that does frequent
read-writes to files on PocketPC(for 2002). The application used to work ok,
all of a sudden we are seeing some corruption issues in file that we are
writing. It seems that even though we write 16k of data to a given file (out
of may be 20) only first 4k is committed to the file system, some data is
lost SOMETIME. Is there a known bug, has anybody encountered such a scenario?
Is it possible that the write on a file fails without write returning an
error?
Roopak
.
- Follow-Ups:
- re: File Write / possible failure/corruption
- From: Roopak
- re: File Write / possible failure/corruption
- Prev by Date: re: Qtek 8020 & Embedded Tools
- Next by Date: Re: ASP error for CreateObject
- Previous by thread: File Write / possible failure/corruption
- Next by thread: re: File Write / possible failure/corruption
- Index(es):
Relevant Pages
|
