From: Reindl Harald <h.reindl@thelounge.net>
To: linux-raid@vger.kernel.org
Subject: Re: problem with recovered array
Date: Thu, 2 Nov 2023 13:46:35 +0100 [thread overview]
Message-ID: <b9d087e8-04f9-4485-9a4e-b11b280fb493@thelounge.net> (raw)
In-Reply-To: <e0af14b5-9522-4148-abbe-ccb207304a61@eyal.emu.id.au>
Am 02.11.23 um 13:29 schrieb eyal@eyal.emu.id.au:
> See update further down.
>
> Interestingly, after about 1.5 hours, when there were 1GB of dirty
> blocks, the whole lot was cleared fast:
>
> 2023-11-02 23:08:49 Dirty: 1018924 kB
> 2023-11-02 23:08:59 Dirty: 1018640 kB
> 2023-11-02 23:09:09 Dirty: 1018732 kB
> 2023-11-02 23:09:19 Dirty: 592196 kB
> 2023-11-02 23:09:29 Dirty: 1188 kB
> 2023-11-02 23:09:39 Dirty: 944 kB
> 2023-11-02 23:09:49 Dirty: 804 kB
> 2023-11-02 23:09:59 Dirty: 60 kB
>
> And iostat saw it too:
> Device tps kB_read/s kB_wrtn/s
> kB_dscd/s kB_read kB_wrtn kB_dscd
> 23:09:12 md127 2.80 0.00 40.40
> 0.00 0 404 0
> 23:09:22 md127 1372.33 0.80 47026.17
> 0.00 8 470732 0
> 23:09:32 md127 75.80 0.80 54763.20
> 0.00 8 547632 0
> 23:09:42 md127 0.00 0.00 0.00
> 0.00 0 0 0
it's pretty easy: RAID6 behaves terrible in degraded state especially
*with rotating disks* and for the sake of god as long it is degraded and
not fully rebuilt you should avoid any load which isn't strictly necessary
the chance that another disk dies is increasing especially in the
rebuild-phase and then start to pray becuase the next unrecoverable read
error will kill the array
a RAID10 couldn't care less at that point because it don't need to seek
like crazy on the drives
---------
what i don't understand is why people don't have replacement disks in
the shelf for every array they operate, replace the drive and leave it
in peace until the rebuild is finished
i am responsible for 7 machines at 5 locations with mdadm RAID of
different sizes and there is a replacement disk for each of them - if a
disk dies or smartd complains it's replaced and the next drive will be
ordered
next prev parent reply other threads:[~2023-11-02 13:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 13:35 problem with recovered array eyal
2023-10-30 16:14 ` Roger Heflin
2023-10-31 2:35 ` eyal
2023-10-31 2:50 ` eyal
2023-10-31 3:21 ` Carlos Carvalho
2023-10-31 6:25 ` eyal
2023-10-31 9:29 ` eyal
2023-10-31 10:24 ` Roger Heflin
2023-10-31 21:40 ` eyal
2023-11-01 10:30 ` Roger Heflin
2023-11-01 13:08 ` eyal
2023-11-01 14:29 ` Roger Heflin
2023-11-02 8:34 ` Johannes Truschnigg
2023-11-02 11:27 ` eyal
2023-11-02 11:57 ` Roger Heflin
2023-11-02 13:05 ` eyal
2023-11-02 17:05 ` Roger Heflin
2023-11-02 23:23 ` eyal
2023-11-03 12:08 ` Roger Heflin
2023-11-02 12:29 ` eyal
2023-11-02 12:46 ` Reindl Harald [this message]
2023-11-03 14:16 ` Carlos Carvalho
2023-11-03 14:32 ` Dirty page flushing regression in 6.5.x vs 6.1.x Roman Mamedov
2023-11-03 15:57 ` problem with recovered array Roger Heflin
2023-11-03 22:38 ` eyal
2023-11-04 0:48 ` eyal
2023-11-04 1:01 ` Roger Heflin
2023-11-04 10:04 ` eyal
2023-10-31 12:39 ` Carlos Carvalho
2023-10-31 14:19 ` Roger Heflin
2023-10-31 19:20 ` Carlos Carvalho
2023-10-31 21:44 ` problem with recovered array [more details] eyal
2023-10-31 22:00 ` eyal
2023-11-01 4:31 ` [now urgent] problem with recovered array eyal
2023-11-01 6:44 ` eyal
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=b9d087e8-04f9-4485-9a4e-b11b280fb493@thelounge.net \
--to=h.reindl@thelounge.net \
--cc=linux-raid@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