From: Robert Hancock <hancockrwd@gmail.com>
To: Bartosz SKOWRON <getxsick@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libata - anomaly performance with NCQ
Date: Fri, 30 Jan 2009 23:18:02 -0600 [thread overview]
Message-ID: <4983DF0A.6030402@gmail.com> (raw)
In-Reply-To: <77887e110901301725p64f5ab4fk341a9bfaf6715a7b@mail.gmail.com>
Bartosz SKOWRON wrote:
> On Sat, Jan 31, 2009 at 2:07 AM, Robert Hancock <hancockr@shaw.ca> wrote:
>
>>> 1) cause the title contains "with hdparm"...does it mean that
>>> physically the performance is OK and only hdparm shows something
>>> wrong?
>> Well, hdparm is a fairly crude benchmark but there's likely at least some
>> impact in other usage.
>
> It's not an answer for my question. So, should I check with other
> benchmarks? I thought that this's issue is investigated and the answer
> is common. Do you recommend any "not crude" benchmarks? :)
bonnie++ is one I've used, I'm sure there are others.. Of course, what
do you compare the results to..
>
>
>>> 2) there is an information about upgrading firmware. as far as i know
>>> Seagate doesn't publish firmwares. So the only way is to contact
>>> seagate support, send the hdd and wait for the new one?
>> I think Seagate can provide firmware updaters for the user to use, but
>> normally only if you contact support I think.
>
> I will send the email cause there is no phone line for my country.
> BTW. upgrade firmware == damage data?
It shouldn't, but some people with the recent 7200.11 drives that did
firmware upgrades reported it bricked the drive, so backing up the data
first would definitely be a good idea..
next prev parent reply other threads:[~2009-01-31 5:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 0:23 libata - anomaly performance with NCQ Bartosz SKOWRON
2009-01-31 1:07 ` Robert Hancock
2009-01-31 1:25 ` Bartosz SKOWRON
2009-01-31 5:18 ` Robert Hancock [this message]
2009-02-02 2:29 ` Bartosz SKOWRON
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=4983DF0A.6030402@gmail.com \
--to=hancockrwd@gmail.com \
--cc=getxsick@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.