From: Steve Johnson <Steve.Johnson@math.tamu.edu>
To: ultralinux@vger.kernel.org
Subject: Re: ultrapenguin as High Availability Raid Server
Date: Fri, 08 May 1998 16:14:15 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90222356530991@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90222356530990@msgid-missing>
Douglas Bowyer wrote:
>
> We are preparing to implement a High Availability Raid Server, using dual
> ultrasparc systems controlling a Raid 5 assembly. It will be primarily
> configured for NFS. In its current status, would any of you use
> ultrapenguin?
I'd like to, but a couple of important parts are missing. First, we
need a journalled filesystem (jfs). Under Slowlaris with DiskSuite, a
jfs is setup with 2 partitions, one for the real filesystem, and one for
the log. In a HA environment, the secondary server would be detect that
the primary is down and mount the primary's partitions that live out on
the RAID. With a jfs, the secondary should be able to quickly assume
the duties of the primary server. Without it, however, a potentially
long fsck would be needed before the partition could be mounted. The
other part that's missing for us is support for ATM NICs.
Patience, patience...
- Steve
--
// Steve Johnson, Systems Administrator
// Dept of Mathematics, Texas A&M University, College Station, TX 77843
// http://www.math.tamu.edu/~Steve.Johnson/ Phone: (409)845-4267
next prev parent reply other threads:[~1998-05-08 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-08 15:50 ultrapenguin as High Availability Raid Server Douglas Bowyer
1998-05-08 16:14 ` Steve Johnson [this message]
1998-05-11 9:58 ` Miguel Barreiro Paz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ultrasparc-90222356530991@msgid-missing \
--to=steve.johnson@math.tamu.edu \
--cc=ultralinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.