On Tue, Oct 12, 2004 at 12:58:53PM -0700, Eric Hopper wrote: > First, it could be updates to /etc/lvm while the filesystem is > suspended. This shouldn't be done at all. First, a journal of what the > planned change is should be written to /etc/lvm, the filesystem > suspended, the change made, the filesystem unsuspended, then a marker > indicating that the change succeeded to /etc/lvm. Sounds like a good starting point. Other interesting cases are swap on LVM, and rolling back the root fs to a snapshot. > Second, it could be the fact that the LVM executable is demand paged. > It could be that a page of the executable is read in while the > filesystem is suspended. This is trickier to solve, and having the > problem is much more excusable than the first. mlockall(2)? Regards, Bill Rugolsky _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
