mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: gjohnson@research.canon.com.au (Greg Johnson)
To: scott@spiteful.org (Scott Murray)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Big-ish SCSI disks
Date: Fri, 25 May 2001 16:22:36 +1000 (EST)	[thread overview]
Message-ID: <20010525062236.8CC1837530@zapff.research.canon.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0105250015550.15333-100000@godzilla.spiteful.org> from "Scott Murray" at May 25, 2001 12:29:05

Thanks. Interesting that you mention the Severworks LE chipset. We
have 2 identical machines with the intel STL MOBO wich uses
the Severworks LE. They are both dual PIII 1GHz 1GB mem and ultra
160 drives. I have had nothing but trouble getting RedHat 7.1 beta-1,
7.1 beta-2 and 7.1 release. The OS tended to install ok 
but on beta1, only the up kernel would boot. On beta-2 and release
both up and smp kernels would boot. On neither of the systems
have I managed to build a kernel up or smp, new or same version
as was installed. When I tried to boot the kernel I had built,
the scsi driver would fail to load. This also happen on the Redhat
installed smp kernel in beta-1 and on any of the redhat installed
kernels in either of beta-2 or release when I tried to use disk
striping.

Have you experienced any issues like this?
Have you successfuly built a kernel that booted on these machines?

Regards

Greg.

Quoth Scott Murray:
> 
> On Fri, 25 May 2001, Greg Johnson wrote:
> 
> > Hi kernel poeple,
> >
> > Can anyone out there say for certain that 76GB SCSI disks should
> > just work with kernel versions 2.2 and/or 2.4? We need to get some
> > big disk space and have heard reports of problems with disks
> > bigger than 30GB under linux.
> 
> I set up a machine at work a few months ago with two Seagate 73GB
> Ultra160 drives (model ST173404LW) using the Adaptec AIC-7899 adapter
> on board a ServerWorks LE chipset based motherboard.  Everything has
> been working fine using the stock RedHat 7.0 2.2.16-22smp kernel.  I
> also played with some 2.4.1-ac kernels to try out ReiserFS, and also
> had no problems using the disks.
> 
> Scott
> 
> 
> -- 
> =============================================================================
> Scott Murray                                        email: scott@spiteful.org
> http://www.spiteful.org (coming soon)                 ICQ: 10602428
> -----------------------------------------------------------------------------
>      "Good, bad ... I'm the guy with the gun." - Ash, "Army of Darkness"
> 


-- 
+------------------------------------------------------+
| Do you want to know more? www.geocities.com/worfsom/ |
|              ..ooOO Greg Johnson OOoo..              |
| HW/SW Engineer        gjohnson@research.canon.com.au |
| Canon Information Systems Research Australia (CISRA) |
| 1 Thomas Holt Dr., North Ryde, NSW, 2113,  Australia |
|      "I FLEXed my BISON and it went YACC!" - me.     |
+------------------------------------------------------+


  reply	other threads:[~2001-05-25  6:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-25  0:05 Greg Johnson
2001-05-25  4:29 ` Scott Murray
2001-05-25  6:22   ` Greg Johnson [this message]
2001-05-25  9:59     ` Rico Tudor
2001-05-25 14:17     ` Mark Frazer
2001-05-25 16:44 ` Joel Jaeggli

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=20010525062236.8CC1837530@zapff.research.canon.com.au \
    --to=gjohnson@research.canon.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott@spiteful.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®