Hi,
On Thu, 1 Jun 2000, Gregory Leblanc wrote:
> > -----Original Message-----
> > From: Gavin Clark [mailto:[EMAIL PROTECTED]]
> >
> > I guess I have a few choices about how to set this up.
> > 1) leave swap as /dev/hda2
> > 2) move swap to /dev/sda2 or /dev/sdb2
> > 3) join sda2 and sdb2 as md2 and put swap on the raid1
> > 4) some combination of the above
> >
> > I've been reading the archive and I can't get a clear picture
> > as to which
> > way to go.
> >
> > Mostly I'm looking for ressiliancy against drive failure.
>
> If your system never uses swap, then it's not a big deal, just configure two
> swap devices with the same priority (I've got 256MB of ram on my desktop, I
> only use swap when I've got 2+ vmware machines running). If you want to
> protect against failure of the disk(s) that swap is stored on, create a
> RAID1 for swap, and use the script that was just recently posted in place of
> swapon -a, because you can't have swap while a RAID set is reconstructing.
The solution I used (for maximum resilience) was to put a swap /file/ on
the RAID-1 root (instead of a seperate partition). This gets around the
problem of using swap during reconstruction, IIRC because swap works
slightly differently on a file rather than on a device. There is a small
speed penalty, but much better resiliancy.
As to options (1) and (2) above, remember that if the swapfile is used
after a disk fails, the machine will likely panic.
Regards,
Corin
/------------------------+-------------------------------------\
| Corin Hartland-Swann | Mobile: +44 (0) 79 5854 0027 |
| Commerce Internet Ltd | Tel: +44 (0) 20 7491 2000 |
| 22 Cavendish Buildings | Fax: +44 (0) 20 7491 2010 |
| Gilbert Street | |
| Mayfair | Web: http://www.commerce.uk.net/ |
| London W1Y 1FE | E-Mail: [EMAIL PROTECTED] |
\------------------------+-------------------------------------/
