From: Giuliano Pochini <pochini@denise.shiny.it>
To: Uwe Bonnes <bon@elektron.ikp.physik.tu-darmstadt.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems even with 512 block size MOs
Date: Sat, 05 May 2001 13:20:45 +0200 [thread overview]
Message-ID: <3AF3E20D.94B62929@denise.shiny.it> (raw)
In-Reply-To: <15088.18199.487902.514295@hertz.ikp.physik.tu-darmstadt.de>
> recent 2.4 kernels have incredible bad performance for me when handling MO
> drives. Going back 2.2 shows better performance.
> Copying a 6.5 MByte file with cp returns nearly immediately on the
> commandline, but umount nearly takes forever. Maximum rate detected by
> xosview during umount was about 30 kByte.
I have this one:
Vendor: FUJITSU Model: MCD3130SS Rev: 0020
and it works very well with 2.4. 2.2 kernel perform really badly because of
the famous merging problem.
> Are all my MO disks rotten? Are the MO drives broken? Are my SCSI adapters
> broken? Or is there a bug in the SCSI layer?
No probs here. I have an Adaptec SCSI card.
Bye.
prev parent reply other threads:[~2001-05-06 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 17:42 Problems even with 512 block size MOs Uwe Bonnes
2001-05-02 17:53 ` Alan Cox
2001-05-05 11:20 ` Giuliano Pochini [this message]
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=3AF3E20D.94B62929@denise.shiny.it \
--to=pochini@denise.shiny.it \
--cc=bon@elektron.ikp.physik.tu-darmstadt.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox