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 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. > -- Luke Scharf, Systems Administrator Virginia Tech Aerospace and Ocean Engineering