From: "John Stoffel" <john@stoffel.org>
To: Reindl Harald <h.reindl@thelounge.net>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Need help increasing raid scan efficiency.
Date: Wed, 4 Jun 2025 08:24:29 -0400 [thread overview]
Message-ID: <26688.15101.386901.684@quad.stoffel.home> (raw)
In-Reply-To: <e6252171-45b5-4739-b2b7-683c1464de2d@thelounge.net>
>>>>> "Reindl" == Reindl Harald <h.reindl@thelounge.net> writes:
> Am 03.06.25 um 03:05 schrieb David Niklas:
>> My PC suffered a rather nasty case of HW failure recently where the MB
>> would break the CPU and RAM. I ended up with different data on different
>> members of my RAID6 array.
>>
>> I wanted to scan through the drives and take some checksums of various
>> files in an attempt to ascertain which drives took the most data
>> corruption damage, to try and find the date that the damage started
>> occurring (as it was unclear when exactly this began), and to try and
>> rescue some of the data off of the good pairs.
> forget it and restore a backup
Or if your data is static, use last years backup and look for
un-changed files and them compare the data inside them?
but yes, using a better backup system is a good idea. I'm using
'burp' for my home backups. And big disks are cheap. How much is
your data worth to you?
next prev parent reply other threads:[~2025-06-04 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 1:05 Need help increasing raid scan efficiency David Niklas
2025-06-03 16:46 ` Wol
2025-06-03 20:04 ` David Niklas
2025-06-03 20:04 ` David Niklas
2025-06-03 20:27 ` anthony
2025-06-04 4:22 ` Jani Partanen
2025-06-04 8:59 ` Reindl Harald
2025-06-04 8:46 ` Reindl Harald
2025-06-04 12:24 ` John Stoffel [this message]
2025-06-04 12:34 ` John Stoffel
2025-06-04 12:52 ` Reindl Harald
2025-06-04 15:45 ` David Niklas
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=26688.15101.386901.684@quad.stoffel.home \
--to=john@stoffel.org \
--cc=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