On Sat, Oct 29, 2005 at 01:00:36AM +0200, S?ren Schmidt wrote:
On 29/10/2005, at 0:41, Mikhail Teterin wrote:
Look in smartmontools I provided patches for that, its not rocket
science you know...
This attitude -- on top of the API change itself -- is not really
encouraging
for
If this drive doesn't support tagged-queueing, is the write cache
disabled? I get that sort of performance from a (PATA) disk with
the cache disabled (hw.ata.wc=0 in loader.conf)
No, just checked -- the hw.ata.wc is set to 1. Is there anything else to look
at?
According to smartctl, the
Mikhail Teterin wrote:
idle temperature seems to be 54C.
According to smartctl, the drive runs at 56C during the copying. Its
I'd double-check that (eg with a finger). If the drive really is
running at 56°C, it won't last very long.
It sure feels hot to the touch, but
Indeed, 55C is way to high for 24/7 usage, and it might be that the
drive is choking on it and barely is able to compensate..
The reads are pretty quick... I'd like to be able to spin it down, but
ataidle is broken :-(
What does SMART say ? any unusual like high correction rates or
Ask the maintainer to get it [ataidle -mi] fixed, but be warned experience
says it might hose your data...
The maintainer did not break it. An incompatible change to the API did :) You
are, probably, in the best position to show us, how the new API should be
used.
Now, you say read speed is
Look in smartmontools I provided patches for that, its not rocket
science you know...
This attitude -- on top of the API change itself -- is not really encouraging
for ISVs, you know :-)
You need to find out what the transfer rates are for the RAW disk, ie
by doing a dd from /dev/zero
Hmm, that does sound as problems with that disk, or maybe disk vs
diskcontroller. Any chance you could try the disk on something else ?
I'll try...
One other thing, how much mem do you have in there ? more than 4G and
bounce buffering might get into the picture ruining the transfer
On Fri, Oct 28, 2005 at 07:09:55PM -0400, Mikhail Teterin wrote..
Hmm, that does sound as problems with that disk, or maybe disk vs
diskcontroller. Any chance you could try the disk on something else ?
I'll try...
One other thing, how much mem do you have in there ? more than 4G and
On Fri, Oct 28, 2005 at 01:18:03AM -0400 I heard the voice of
Mikhail T., and lo! it spake thus:
According to smartctl, the drive runs at 56C during the copying. Its
idle temperature seems to be 54C.
That sounds a little high to me. Smartctl has been weird lately, and
it only shows temp on
On Fri, 2005-Oct-28 01:18:03 -0400, Mikhail T. wrote:
I've got a new Hitachi drive with 16Mb of cache:
ad8: 476940MB HDS725050KLA360 K2AOA11A at ata4-master SATA150
and am trying to use it to store backups online. Unfortunately, writing
to the disk is painfully slow (by today's standards)
At 07:48 PM 10/28/2005 +1000, Peter Jeremy wrote:
| On Fri, 2005-Oct-28 01:18:03 -0400, Mikhail T. wrote:
| I've got a new Hitachi drive with 16Mb of cache:
|
| ad8: 476940MB HDS725050KLA360 K2AOA11A at ata4-master SATA150
|
| and am trying to use it to store backups online. Unfortunately,
Hi!
I've got a new Hitachi drive with 16Mb of cache:
ad8: 476940MB HDS725050KLA360 K2AOA11A at ata4-master SATA150
and am trying to use it to store backups online. Unfortunately, writing
to the disk is painfully slow (by today's standards) -- it can barely
keep 7Mb/second and my other
On Fri, 2005-Oct-28 12:45:27 -0400, Mikhail Teterin wrote:
No, just checked -- the hw.ata.wc is set to 1. Is there anything else to look
at?
That exhausts my ideas, sorry. Sören might be able to suggest something.
According to smartctl, the drive runs at 56C during the copying. Its
idle
On 28/10/2005, at 22:48, Peter Jeremy wrote:
On Fri, 2005-Oct-28 12:45:27 -0400, Mikhail Teterin wrote:
No, just checked -- the hw.ata.wc is set to 1. Is there anything
else to look
at?
That exhausts my ideas, sorry. Sören might be able to suggest
something.
Not really, however I have
On 28/10/2005, at 23:45, Mikhail Teterin wrote:
Indeed, 55C is way to high for 24/7 usage, and it might be that the
drive is choking on it and barely is able to compensate.
The reads are pretty quick... I'd like to be able to spin it down, but
ataidle is broken :-(
Ask the maintainer to
On 29/10/2005, at 0:03, Mikhail Teterin wrote:
Ask the maintainer to get it [ataidle -mi] fixed, but be warned
experience
says it might hose your data...
The maintainer did not break it. An incompatible change to the API
did :) You
are, probably, in the best position to show us, how the
On 29/10/2005, at 0:41, Mikhail Teterin wrote:
Look in smartmontools I provided patches for that, its not rocket
science you know...
This attitude -- on top of the API change itself -- is not really
encouraging
for ISVs, you know :-)
Sigh, ataidle is a hack and the author had no
On 29/10/2005, at 1:09, Mikhail Teterin wrote:
Hmm, that does sound as problems with that disk, or maybe disk vs
diskcontroller. Any chance you could try the disk on something else ?
I'll try...
One other thing, how much mem do you have in there ? more than 4G and
bounce buffering might
Søren Schmidt wrote:
On 28/10/2005, at 23:45, Mikhail Teterin wrote:
Indeed, 55C is way to high for 24/7 usage, and it might be that the
drive is choking on it and barely is able to compensate.
The reads are pretty quick... I'd like to be able to spin it down, but
ataidle is broken :-(
19 matches
Mail list logo
