On Wed, Oct 11, 2006 at 12:27:12PM -0400, Lennart Sorensen wrote: > On Wed, Oct 11, 2006 at 06:04:43PM +0200, Daniel Tryba wrote: > > with a generous 2Gb for / only and you "never" need to worry about it > > filling up. > > / is to valuable to lose. IMHO a single disk setup is a no go. > > > > new machines get (multiple (identical) disks with) 2 partitions on them: > > 1 - a small 2Gb (type fd) > > 2 - the rest (type fd) > > > > The small partitions are combined in a md0 array raid1, the others in > > whatever you like (most likely 5, 1 otherwise) md1 array. > > > > /dev/md0 will be used for /. > > /dev/md1 will be a pv for lvm. > > > > This adds redundancy, plus any of the partition that make up the raid1 > > for / can be mounted on its own (but writing to one will break the > > array). Adding a disk creates an other copy of /, and with the newer > > kernels a raid5 array can be expanded, so it can be used by the LVM. > > > > I like it. It matches how I setup all my machines. After having done > > Len Sorensen > > I am lucky in that my backup-set size is small; Its been tight on a 100 MB Zip disk and absolutley essential stuff (stuff I need to be able to access absolultly from anywhere, any time) fits on one floppy in gzipped plain-text. My approach for the new root drive was to buy the most reliable drive I could. If it dies, get a new drive and reinstall, restore from backup and carry on.
Your approach using Raid may be overkill for me, I don't know. The board itself has hardware SATA raid available. If I go for raid, then I'll ask here for the advantages/disadvantages. More to the point for me, though, is where can I get current howtos or guides on fixing problems when things are in raid or LVM? Its a whole new world for me and the LDP HOWTOs are too out of date, and debian-reference doesn't cover it. At this point I'm leaning to the single disk, regular / at 512 MB (/tmp is separate LV) and the rest PV. Since my / doesn't change much, when I add a second disk, just copy / and have a non-raid copy available to boot into. When I do make changes, just copy it over; could even make it part of the regular backup strategy. Thanks for the ideas, Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
