public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fun with mdadm (Software RAID)
Date: Sun, 22 Dec 2024 12:08:34 +0000	[thread overview]
Message-ID: <4ac4f9df-6b93-4ffd-b0c3-a2764e624500@youngman.org.uk> (raw)
In-Reply-To: <Z2XRa26ogrtBVFjk@MAC.fritz.box>

On 20/12/2024 20:19, Alan Mackenzie wrote:
> I've just tried it, with metadata 1.2, and it doesn't work.  I got error
> messages at boot up to the effect that the component partitions were
> lacking valid version 0.0 super blocks.
> 
> People without initramfs appear not to be in the sights of the
> maintainers of this software.  They could so easily have made the
> assembly of metadata 1.2 components on the kernel command line work.
> 🙁
No they couldn't. Not if they wanted (at the time) a kernel small enough 
to boot successfully ...

Making the disk write write identically to two disks (your basic 0.9 
mirror) is pretty simple, and also extremely error prone. Making mdraid 
robust with all the other features of an enterprise "protect your data" 
system is a lot more work.

mdraid has probably just protected my data - dunno what triggered it, 
but I lost a disk and it just got rebuilt in the background without me 
doing a thing ...
> 
> By the way, do you know an easy way for copying an entire filesystem,
> such as the root system, but without copying other systems mounted in
> it?  I tried for some while with rsync and various combinations of
> find's and xargs's, and in the end booted up into the rescue disc to do
> it.  I shouldn't have to do that.

Provided it's read-only (so yes if it's the root I might well use a 
rescue disk) I'd use dd. That's assuming a fairly small root that's 
fairly full, it's rather wasteful if it's not ...

Cheers,
Wol


  parent reply	other threads:[~2024-12-22 12:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 10:47 [gentoo-user] Fun with mdadm (Software RAID) Alan Mackenzie
2024-12-20 14:50 ` karl
2024-12-20 15:28   ` Alan Mackenzie
2024-12-20 17:44     ` karl
2024-12-20 20:19       ` Alan Mackenzie
2024-12-20 20:38         ` Hoël Bézier
2024-12-20 20:53           ` Alan Mackenzie
2024-12-20 22:02         ` karl
2024-12-30  4:08           ` Frank Steinmetzger
2024-12-20 22:02         ` karl
2024-12-21 12:43           ` Alan Mackenzie
2024-12-21 16:36             ` Alan Mackenzie
2024-12-21 16:45               ` karl
2024-12-21 16:58                 ` Alan Mackenzie
2024-12-22 13:08                   ` Alan Mackenzie
2024-12-22 12:16             ` Wols Lists
2024-12-22 12:08         ` Wols Lists [this message]
2024-12-22 12:02       ` Wols Lists
2024-12-22 13:43         ` Alan Mackenzie
2024-12-22 15:29           ` Peter Humphrey
2024-12-22 16:53             ` Wols Lists
2024-12-22 20:05               ` Alan Mackenzie
2024-12-25 21:16                 ` Steven Lembark

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=4ac4f9df-6b93-4ffd-b0c3-a2764e624500@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=gentoo-user@lists.gentoo.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