The problem comes in when another system writes to the same space
AHEAD of the cache in the same area of the disk. It only needs to be a
few bytes, and the cache then become useless because as the read
operations progress, the cache is actually loading the new data, and
then you get data corruption. And if we expand the caching concept,
how much do you cache and how do you reflect updates made by other
Its much easier to use to provided tools to access Windows drives,
usually via the network.
On Fri, 14 Jan 2005 19:09:42 +0000, Nuno Lucas <ml-colinux@...> wrote:
> Hilmar Preusse, dando pulos de alegria, escreveu :
> >>This is also why the linux NTFS driver will never work with colinux
> >>(can work, but with high corruption risk) and we need things like
> >>the experimental cofuse module, which use the host OS API to "talk"
> >>to the file system, avoiding so any corruption issues.
> > I.e. I can't mount a Windows partition of my running Windows from
> > coLinux even R/O?
> Right. It has to do with how all operating systems cache disk data
> into memory for faster access, which can't be seen from colinux.
> Even a shared FAT32 partition is not safe, because of that caching.
> It would be possible to write an unsafe r/o module to read windows
> partitions, but why would anyone do it if it would always be an unsafe
> thing to use?
> There is the experimental (and buggy, right now) cofs driver to access
> windows partitions that will solve this issue, and there are a lot of
> different ways of doing it from the network (smbfs/cifs-samba, ssh, ftp,
> ~Nuno Lucas
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> coLinux-users mailing list