On Mon, 22 Nov 1999, Dirk Lutzebaeck wrote:
Niklas Paulsson writes:
The lack of a journaling fs is also a major show stopper at our site,
once we have a relaible journaling fs that works well together with sw
(and hw) raid , we will begin thinking of a migration path to linux on
our big
On Sun, Nov 21, 1999 at 02:43:27PM -0500, Alex H. Vandenham wrote:
It would be VERY HELPFUL if someone involved in this project could update some
of the information on the linux raid tools and patches. It's not a big task
and it would make it much easier for users to figure out what to use
Dirk,
Depending on your application, you may want to consider getting
_two_ linux boxes and setting up some form of clustered configuration.
Solaris or Linux, if you're relying on just one box for a mission
critical app - it's going to let you down sooner or later.
Maintenance tasks are much
Our local supplier will do fast turnaround (2 to 4 hours) Monday thru
Sunday - no matter what Operating System we haveThe only problem we have
with Linux is that you really need an on-site Linux expert to fix/patch any
OS glitches/security problems..and an expert in the first place to ensure
Niklas Paulsson wrote:
Thomas Waldmann wrote:
There is no problem with patching 2.2.11 or 2.2.12 or 2.2.13 with the 0824
patches - I (and many other people) verified the rejects and there is no real
problem - the stuff rejected simply already IS in the standard kernel.
This is also
Michel,
Thanks for that. It makes things much clearer.
Nov 16 13:36:28 korak kernel: sdb4's event counter: 0016
Nov 16 13:36:28 korak kernel: sda4's event counter: 0017
Nov 16 13:36:28 korak kernel: md: superblock update time inconsistency
-- using
the most recent one
Nov 16
On 22 Nov, Matthew Clark wrote:
Our local supplier will do fast turnaround (2 to 4 hours) Monday thru
Sunday - no matter what Operating System we haveThe only problem we have
with Linux is that you really need an on-site Linux expert to fix/patch any
OS glitches/security problems..and an
thanks to the online version of the Software-RAID HowTo (the one that
comes with the raidtools 0.90 is hopelessly out of date), I was able
to build a system totally running on RAID1 volumes.
If you have the up-to-date raidtools, you have a (near enough) up-to-date HOWTO.
I bet you just looked
While doing the mkraid --force i accidentially mounted the /dev/md without
ext2fsing it. This probably damaged the persistent superblock and mkraid
stopped. Redoing the mkraid was not possible!
How did you manage to mount a device which did not have a filesystem on it? Did
you apply the RAID
On Mon, 22 Nov 1999, Matthew Clark wrote:
Ummm... You should have an on-site expert for any OS if it's mission
critical. And if it's not, you should probably still open a contract
with one in case you need him/her.
Yes - my point (made unclearly, I admit) is that finding a Linux
I take it you're talking about booting from a raid device right from LILO?
I prefer having a simple boot partition on each drive of the RAID 1. Sure
it's more work to maintain two copies of /boot but I don't update the
kernel that often. This method is so simple and it's so reliable.
Anyone
-Original Message-
From: Roeland M.J. Meyer [EMAIL PROTECTED]
Check out http://www.raidzone.com However they don't have bootable Linux
for
it yet (1Q00 or 2Q00).
RAIDZONE includes complete BIOS support for the Intel
bootstrap mechanism. You can use it to boot any OS
including DOS,
Jason Clifford wrote:
On Mon, 22 Nov 1999, Matthew Clark wrote:
Ummm... You should have an on-site expert for any OS if it's mission
critical. And if it's not, you should probably still open a contract
with one in case you need him/her.
Yes - my point (made unclearly, I admit)
Title: RE: Request for Advice
Watch Out!
Not many hot-swap drive enclosure vendors support ultra2 (low voltage differential). Many have limits of only a couple of LVD devices per bus, if they support it at all.
Check out Adjile Systems for a LVD drive can. Note: I have no association with
John Burton wrote:
Simple (in they eyes of the check writers :-), buy a *name* brand and it
fails, its the name brand's problem and you chalk it up to experience.
Buy a *noname* brand and it fails and its *your* problem because you
accepted the risk of going with an unknown quantity - risk
Around here, the SysAdmins do not buy the gear, the platform architects do.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Luis Costabile
Sent: Monday, November 22, 1999 8:26 AM
To: Matthew Clark
Cc: [EMAIL PROTECTED]
Subject: RE: my sunday
I wouldn't like it either grin. It is an architect's job to NOT allow
domination. Also around here, Architects are required to have 10 years in
software development, 5 years in development management, and more than a
year or two exposure to sales/marketing. I guess that qualifies for the
"suit"
17 matches
Mail list logo
