a lot of filesystems use a write-behind cache. calling sync() is a way of saying "make sure this data is actually on the disk"
Lizard Lizard wrote: > On Tue, Dec 20, 2011 at 3:18 PM, Thomas Mueller > <[email protected]> wrote: >> Hi, >>> Also, while this is off-topic, the "network drive" isn't; the location >>> of the database file is on the c:\ drive, same as the server and the >>> running app. In other words, it can't become "unavailable" if the app >>> is running in the first place, so I find the error very odd. >> >> Maybe sync simply isn't supported by this file system? >> > Well, the file system is Windows 7 Home Premium, if that helps. > > What triggers the *need* to sync? I'm getting the impression that it's > not something happening at the H2 level. > > I am, still, somewhat confused about what the file system is trying to > sync *with*. When I've restarted the computer and then try to connect > to the DB using a local path, and get the io sync error, I am not sure > what's trying to sync up with what; I can understand if the database > was corrupt and unreadable due to write errors, but my understanding > here is that this error is generated outside of H2. Various google > searches have not revealed a lot of detail on this error; it's > apparently not a common problem. > > I ultimately deleted the disk file and re-imported the data, and at > the moment, it's looking good. > > I will also take a look at my general threading code; it's possible I > may be sharing file resources improperly between threads, and the > tests I've been running have been extreme, straining my system in ways > likely to cause disk contention and other issues that might not occur > with smaller test runs. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
