public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: Christian Focke-Kiss <christian.focke-kiss@mail.fernfh.ac.at>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
	"yukuai3@huawei.com" <yukuai3@huawei.com>,
	"song@kernel.org" <song@kernel.org>
Subject: Re: Possible issue with software RAID 1 in case of disks with different speed
Date: Sun, 7 Dec 2025 15:41:22 -0500	[thread overview]
Message-ID: <26933.58994.820569.229198@quad.stoffel.home> (raw)
In-Reply-To: <ac13d188ba7e2d5b0e2a8943d720f1903003d548.camel@mail.fernfh.ac.at>

>>>>> "Christian" == Christian Focke-Kiss <christian.focke-kiss@mail.fernfh.ac.at> writes:

> I am using Debian stable for years (currently, release 13; before, 12,
> 11, 10, etc. starting with 3.0, if my long-time backups are complete).

Same here, though with different backup tools

> For some years now, I am using software RAID with two RAID 1 sets with
> three 8TB disks each, one for my production data (/home, /var/lib,
> /var/www, etc.) and the second one for a nightly backup of my
> production data (three disks each because HDDs failed quite frequently
> then, and recovery was slow).

I like this, three way mirrors are cheap insurance. 

> Initially, I used external disks connected mainly via USB 3.x, and also
> via USB 2.0, when I ran out of USB ports. Reason for USB was that I
> couldn't/wouldn't afford a server with slots for accomodating six 3.5"
> HDDs.

There's the problem, USB connections are notoriously crappy.  It would
be better to go with eSATA or some other more reliable transport.  

> After migrating the failed 3.5" HDDs to 2.5" SSDs one-by-one over
> the years, I finally migrated five disks into a rack-mount server
> and connected the sixth disk via USB 3.x (I couldn't migrate all six
> disks because one slot was still occupied by the boot disk).

> I run nightly rsync jobs ('managed' by Back In Time) to backup
> everything from /dev/md0 (boot) to /dev/md1 (production) and then to
> /dev/md2 (backup).

> Now, as long as the sixth disk was still connected via USB 3.x, the
> rsync job and a kworker job were 'blocked' after some hours of
> rsync- ing, and the console displayed some 'sync' errors, and I had
> to press Ctrl+Alt+Del to reboot the system because login didn't work
> anymore.

What did you see in the logs?  I.e. did you kick off the logs and then
maybe send the logs to another system (if possible) or to the console
which you could then switch the display to, so you might have a chance
of looking at things?  

> I flagged the USB 3.x disk 'write-mostly' and 'nofailfast' but this
> didn't resolve the issue.

I suspect your external USB enclosure is crap.  I've never found a
good one in my experience.  It's too prone to losing connectivity, or
having a crappy controller chip which just doesn't handle long term
writes well, etc. 

> Only after I added two NVMe SSDs as boot disks and migrated the
> sixth SSD into the sixth slot, everything runs fine.

It's the USB connection, not the disk or RAID.  

> Conclusion:
> I suspect software RAID 1 has issues if one disk of a three disk RAID 1
> set is significantly slower than the other two disks.

Logs?  Warnings?  

Glad to hear it's up, but in the future, just use eSATA or regular
SATA in your case.  I've got some old big cases with 8 drive bays for
3.5" disks and it works great.  I've thought about server case with
2.5" disks that could be hot-swapped, but in reality for a home
system, I don't need it up five 9s, I can handle downtime.  

But thanks for the anecdote!
John

  reply	other threads:[~2025-12-07 20:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-07 14:41 Possible issue with software RAID 1 in case of disks with different speed Christian Focke-Kiss
2025-12-07 20:41 ` John Stoffel [this message]
2025-12-07 22:00 ` Roger Heflin
2025-12-11  0:25 ` Andy Smith

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=26933.58994.820569.229198@quad.stoffel.home \
    --to=john@stoffel.org \
    --cc=christian.focke-kiss@mail.fernfh.ac.at \
    --cc=linux-raid@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=yukuai3@huawei.com \
    /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