From: Riccardo <rollei@tiscalinet.it>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Hanging with kernels >= 2.4.22
Date: Sun, 22 Feb 2004 15:46:08 +0100 [thread overview]
Message-ID: <4038C0B0.F7D1708A@tiscalinet.it> (raw)
In-Reply-To: 20040221170508.GB14198@baldric.uwo.ca
Carlos O'Donell wrote:
>
> > Thanks! Changing NCR_700_MAX_TAGS to 1 in drivers/scsi/53c700.h did the
> > trick. Will I now have poor disk performance? If so, might I get away
> > with setting it to something higher, like 2 or 4, maybe?
>
> I could never run IO stably at anything higher than 1. The drives don't
> seem to handle it properly, the error recovery mechanisms seem less
> than perfect, and the box just hangs.
It really depends on the drive. I have a Fujitsu Enterprise and it has a
specified tag queue of 128 commands. So if something fails, it is the
driver or HP's hardware.
I have a 715 scorpio and when I used ext2 or reiser with a tag queue of
16 I had very frequent freezes up to a point were the system wouldn't
even mount the partition.
There was a discussion that hp set it to 2 for workstations and to 8 for
servers. I have set it right now to 8 (since mavbe the NCR 7100 I have
doesn't even support more) and I use XFS instead of reiser. I had no
more problems...
I would set the tag queue as default to 8 and not to 16, to stay on the
safe side. Couldn't it be made configurable from the kernel
configuration menu?
What I notivced that some drives seem to be incompatible. I had 2 hard
disks that worked together (an original quantum divre rebranded HP and
an IBM disk). Since my ibm disk died I substitued it with the Fujitsu,
used a new Filesystem and a newer kernel. There was no way to see both
disks when linux booted. I had to remove the original HP disk and
substitute it (a nuisance, since it contained the home directories).
Attaching each time only one of the two disks recognized the correct
disk respectively but both disk weren't. Another disk had no problem.
-Riccardo
next prev parent reply other threads:[~2004-02-22 14:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 23:52 [parisc-linux] Hanging with kernels >= 2.4.22 Stuart Brady
2004-02-19 6:29 ` Grant Grundler
2004-02-21 7:58 ` Stuart Brady
2004-02-21 17:05 ` Carlos O'Donell
2004-02-21 18:24 ` Matthew Wilcox
2004-02-22 6:04 ` Carlos O'Donell
2004-02-22 14:46 ` Riccardo [this message]
2004-02-22 15:30 ` Joel Soete
2004-02-22 17:16 ` Riccardo
2004-02-22 17:54 ` Joel Soete
2004-02-22 6:21 ` Grant Grundler
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=4038C0B0.F7D1708A@tiscalinet.it \
--to=rollei@tiscalinet.it \
--cc=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.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