From: Aric Cyr <Aric.Cyr@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13 (was 2.6.11.11) and rsync oops (SATA or NFS related?)
Date: Thu, 8 Sep 2005 02:37:16 +0000 (UTC) [thread overview]
Message-ID: <loom.20050908T042646-261@post.gmane.org> (raw)
In-Reply-To: <431F21DB.2010504@thinrope.net>
Kalin KOZHUHAROV <kalin <at> thinrope.net> writes:
> ata1: dev 0 configured for UDMA/100
> ata2: dev 0 configured for UDMA/100
> scsi1 : sata_sil
> Vendor: ATA Model: WDC WD360GD-00FL Rev: 21.0
> Type: Direct-Access ANSI SCSI revision: 05
> Vendor: ATA Model: ST3300831AS Rev: 3.03
> Type: Direct-Access ANSI SCSI revision: 05
Looks like UDMA/100 is set up fine for both your drives.
> # hdparm -t /dev/sdb
>
> /dev/sdb:
> Timing buffered disk reads: 176 MB in 3.01 seconds = 58.43 MB/sec
> HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl
> for device
>
> I don't like the error MSG above, but 58MB/s is not bad, compared to 36.5MB/s
> with ide-sata driver!
This is normal. hdparm doesn't know much about SCSI drives... SATA drives are
closer to SCSI than IDE. In particular the various direct IDE ioctls are not
supported by the SCSI layer. Don't worry about these errors.
> Might be a stupid question... but is UDMA relevant to SATA drives run by
> libata??
> If yes, how do I get the current value of it?
See above.
> And upgrading firmware to a harddrive is done how?
> Done on my BIOSes, my Plextor CD-Rs and DVD+RWs, but on a hard drive?
> Any pointers, or that was just a random thought
>
> According to linux-2.6.13/drivers/scsi/sata_sil.c:94 my drives are not
> blacklisted.
Sorry, I thought your drive might be blacklisted, but I didn't actually check
the driver for your model. You are getting UDMA/100 so your drive is just
fine, no firmware update is required. If you were interested though, poking
around seagates site would probably turn up some firmware updates, if any are
available. I did have a blacklisted seagate drive, but it works fine after
the firmware update and removal from the blacklist.
Regards
prev parent reply other threads:[~2005-09-08 2:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 0:17 2.6.11.11 and rsync oops (SATA related?) Kalin KOZHUHAROV
2005-09-05 8:13 ` 2.6.13 (was 2.6.11.11) and rsync oops (SATA or NFS related?) Kalin KOZHUHAROV
2005-09-05 14:12 ` Kalin KOZHUHAROV
2005-09-06 8:24 ` Kalin KOZHUHAROV
2005-09-07 4:00 ` Aric Cyr
2005-09-07 17:22 ` Kalin KOZHUHAROV
2005-09-08 2:37 ` Aric Cyr [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=loom.20050908T042646-261@post.gmane.org \
--to=aric.cyr@gmail.com \
--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
all inboxes | Powered by JetHome®