On 5/11/05, Robert Locke <lists@xxxxxxxxx> wrote: > To be honest, I would be surprised if this ever worked. I think, you > are correct in your assumption that the primary issue is a caching > issue. But it's not just the "write-cache". There is a read-cache. > How does the "hibernating" operating system know that a change has been > made to one of the "drives/partitions"? These operating systems and > their interactions with the hard disk make a HUGE ASSUMPTION - that they > are the only one accessing the disk/partition/filesystem. This is why > clustering is not a slam dunk and requires a different filesystem. > > What you would need to do is modify the "hibernate" scripts to > drop/umount or something the "shared" filesystem and the "wakeup" > scripts to pickup/mount or something the "shared" filesystem. This way, > only one operating system has the partition/filesystem open at a time > and life returns to sanity.... > > HTH, > > --Rob > Try shuting down the operating systems instead of hibernating them. If this solves the problem, then modify the hibernate/ wakup scripts as Rob suggested. Dotan Cohen http://Song-Lirics.com/ http://Song-Lyriks.com/
