On 27/11/2018 22:16, Mike Pumford wrote:
On 27/11/2018 21:27, Havard Eidnes wrote:
So for now just assume duff hardware. Sorry for the noise and thanks for
the suggestions.
Now confirmed as a very broken disk. Currently reconstructing a new
raid1 onto a 4TB disk at 172MB/s :) Haven't
On 27/11/2018 21:27, Havard Eidnes wrote:
It could be that the caching settings on the new drive is
different from the old one. Check and adjust with "dkctl", using
"getcache" and "setcache" as required.
Just checked that and the settings are the same. I've also disassembled
and
> [...] I'm doing a raid1 reconstruct which should
> be a straight read from disk A, write to disk B. The data from systat
> backs that up. Each disk is doing ~110 transfers per second. wd1 the
> source disk is reading at 7MB/s and wd2 the destination is writing at
> 7MB/s.
It could be that the
On 24/11/2018 09:19, Mike Pumford wrote:
On 23/11/2018 22:20, Jaromir Dolecek wrote:
Can you perhaps try interrupt count via intrctl? iirc someone
complained about some interrupt storm coming from acpi.
Didn't know about that one. That gives:
interrupt id CPU0 CPU1 CPU2 CPU3
On 23/11/2018 22:20, Jaromir Dolecek wrote:
Can you perhaps try interrupt count via intrctl? iirc someone
complained about some interrupt storm coming from acpi.
Didn't know about that one. That gives:
interrupt id CPU0 CPU1 CPU2 CPU3 device name(s)
ioapic0 pin 9 0*0
Can you perhaps try interrupt count via intrctl? iirc someone complained about
some interrupt storm coming from acpi.
> Le 23 nov. 2018 à 21:15, Mike Pumford a écrit :
>
>
>
>> On 23/11/2018 20:01, Michael van Elst wrote:
>> mpumf...@mudcovered.org.uk (Mike Pumford) writes:
I'm seeing
On 23/11/2018 20:01, Michael van Elst wrote:
mpumf...@mudcovered.org.uk (Mike Pumford) writes:
I'm seeing a write speed of 7MB/s which means my 2TB reconstruct is
going to take 72+hours! Last time I did it it took about 3 hours if I'm
remembering correctly.
Just updated this to a build
mpumf...@mudcovered.org.uk (Mike Pumford) writes:
>> I'm seeing a write speed of 7MB/s which means my 2TB reconstruct is
>> going to take 72+hours! Last time I did it it took about 3 hours if I'm
>> remembering correctly.
>Just updated this to a build from the 17th and there is no change. :(
On 23/11/2018 19:30, Mike Pumford wrote:
Due to a disk failure I'm having to do a full raid1 reconstruct on one
of my systems and the performance seems much slower than last time I did
it on this system.
I'm seeing a write speed of 7MB/s which means my 2TB reconstruct is
going to take
Due to a disk failure I'm having to do a full raid1 reconstruct on one
of my systems and the performance seems much slower than last time I did
it on this system.
I'm seeing a write speed of 7MB/s which means my 2TB reconstruct is
going to take 72+hours! Last time I did it it took about 3
10 matches
Mail list logo
