Luke Scharf wrote: > The issue appears to have cleared up after I applied a BIOS update to my > Asus P4P800S-X motherboard. I guess VMWare was the only application I > had that worked the I/O hard enough to expose the bug.... > > I guess the cobbler's children had no shoes at my house! Seriously, I > know to patch *everything*, but I just neglected to update the BIOS. > > -Luke Wow...that is VERY interesting...as I wouldn't think that the BIOS would have anything to do with it....so I'll put that one in the memory banks and back pocket. Interestingly, I just heard when I was at the computer shop that a person just updated his BIOS and it messed up all of his Linux stuff...to the point that it wouldn't even boot anymore...so the BIOS can be all important, I guess...and some of the VERY LATEST bios's don't play nice with the Linux Kernel...especially some of the newest ACPI schemes, I'm finding out (unrelated to this thread, I know...but you brought up an interesting problem). Thanks for the tip.. Bob > Luke Scharf wrote: > >> I've been having trouble with VMWare 5 and SL4... I've submitted a >> big-report the VMWare folks -- but they can't/won't replicate it. >> >> The problem is that after I use VMWare for a while, it will cause the >> device holding /home (/dev/mapper/VolWhatever) to become read-only. >> Remounting doesn't help -- I have to reboot before I can write to >> /home again. I've rebuilt the machine from scratch and I see the same >> behavior. >> >> I'm running a pair of mirrored HDDs, with LVM running in /dev/md2, and >> then ext3 filesystems on top of LVM. (The /dev/md1 device is used is >> /boot.) >> >> Has anyone seen anything similar? Any suggestions? >> >> Thanks, >> -Luke >> >> P.S. It doesn't seem to happen on my work-computer, which is running >> SL4 on non-mirrored drives. The /home volume is delivered by an NFS >> automunt on that computer, though. >> > > -- Of all the animals, the boy is the most unmanageable. -- Plato