On 22/04/2009 15:02, Goswin von Brederlow wrote:
John Robinson <john.robinson@xxxxxxxxxxxxxxxx> writes:
Another issue might be the LVM layer; does that need to be stopped or
switched to read-only too?
Debian does
/sbin/vgchange -aln --ignorelockingfailure || return 2
before S60mdadm-raid, S60umountroot and S90reboot.
But that's not going to switch any VG with a still-mounted filesystem
(e.g. /) to read-only or make it go away, it's going to fail. Still
probably a good idea for other circumstances, though.
I've been using a 1GB / for years and years now so that won't be a
problem. As for the rest one can also bind mount /usr, /var, /home to
/mnt/space/* respectively. I.e. have just 2 (/ and everything else)
partitions.
Well, I have just 2, /boot and everything else, but I might in the
future switch to your suggestion.
Esspecially for XEN hosts I find LVM verry usefull. Makes it easy to
create new logical volumes for new xen domains.
My thoughts exactly :-)
Many thanks,
John.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
