All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Sanders <plsander@gmail.com>
To: Eyal Lebedinsky <fedora@eyal.emu.id.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID 6, 6 device array - all devices lost superblock
Date: Mon, 29 Aug 2022 19:53:44 -0400	[thread overview]
Message-ID: <CAKAPSkJhf8hWGTQiCne6BnMPYoum4hJT3diz9U1FGAfq=_N-nA@mail.gmail.com> (raw)
In-Reply-To: <1d978f6c-e1cc-e928-efc5-11ff167938b1@eyal.emu.id.au>

Couple more questions.

Mdadm -create ... Do I use the /dev/sdx or /dev/mapper/sdx name for
the overlayed device?

And reset the mapping between each create attempt by doing:
remove the loop-device/overlay association
   dmsetup remove on all devices
remove the overlay files
  rm
remove the loop back devices
  losetup -d ...
rebuild the loop back devices
  mknod -m 660 ...
build the overlay files
  truncate -s 300G overlay-...
reassociate the loop-devices and the overlays
  losetup... dmsetup..

and try again.

(Yeah, I recognize that there is code to do this (I think) in the
article, but my script-fu is not up to fully understanding those
examples.)

On Mon, Aug 29, 2022 at 6:58 PM Eyal Lebedinsky <fedora@eyal.emu.id.au> wrote:
>
>
> On 30/08/2022 07.45, John Stoffel wrote:
> >>>>>> "Peter" == Peter Sanders <plsander@gmail.com> writes:
> >
> > Peter> Phil,
> > Peter> fstab from the working config -
> >
> > Peter> # <file system> <mount point>   <type>  <options>       <dump>  <pass>
> > Peter> # / was on /dev/sda1 during installation
> > Peter> UUID=50976432-b750-4809-80ac-3bbdd2773163 /               ext4
> > Peter> errors=remount-ro 0       1
> > Peter> # /home was on /dev/sda6 during installation
> > Peter> UUID=eb93a2c4-0190-41fa-a41d-7a5966c6bc47 /home           ext4
> > Peter> defaults        0       2
> > Peter> # /var was on /dev/sda5 during installation
> > Peter> UUID=d1aa6d1f-3ee9-48a8-9350-b15149f738c4 /var            ext4
> > Peter> defaults        0       2
> > Peter> /dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
> > Peter> /dev/sr1        /media/cdrom1   udf,iso9660 user,noauto     0       0
> > Peter> # raid array
> > Peter> /dev/md0    /mnt/raid6    ext4    defaults    0    2
> >
> > Peter> No LVM, one large EXT4 partition
> >
> > Peter> I have several large files ( NEF and various mpg files) I can identify
> > Peter> and have backup copies available.
> >
> > Peter> I have the overlays created. 300G for each of the six drives.
> >
> > So that's good.  Now you have to try and figure out which order they
> > were created in.  As the docs show, you setup the overlayfs on top of
> > each of the six drives.
> >
> > Keep track by noting the drive serial numbers, since Linux can move
> > them around and change drive letters on reboots.
> >
> >
> > Then using the overlays, do an:
> >
> >       mdadm --create /dev/md0 --level=raid6 -n 6 /dev/sd[bcdefg]
> >       fsck -n /dev/md0
> >
> > and see what you get.  If it doesn't look like a real filesystem, then
> > you can break it down, and then modify the order you give the drive
> > letters, like:
> >
> >        /dev/sd[cdefge]
> >
> > and rinse and repeat as it goes.  Not fun... but should hopefully fix
> > things for you.
> >
> > John
>
> An aside, I would think the way to specify a list in a nominated order is something like
>
> $ echo /dev/sd{c,d,a,b}
> /dev/sdc /dev/sdd /dev/sda /dev/sdb
>
> rather than
>
> $ echo /dev/sd[cdab]
> /dev/sda /dev/sdb /dev/sdc /dev/sdd
>
> which will be in sorting order, regardless of the order of the letter.
>
> --
> Eyal Lebedinsky (fedora@eyal.emu.id.au)

  reply	other threads:[~2022-08-29 23:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-28  2:00 RAID 6, 6 device array - all devices lost superblock Peter Sanders
2022-08-28  9:14 ` Wols Lists
2022-08-28  9:54   ` Wols Lists
2022-08-28 16:47     ` Phil Turmel
     [not found]       ` <CAKAPSkJAQYsec-4zzcePbkJ7Ee0=sd_QvHj4Stnyineq+T8BXw@mail.gmail.com>
2022-08-28 17:16         ` Wols Lists
2022-08-28 18:45         ` John Stoffel
2022-08-28 19:36           ` Phil Turmel
2022-08-28 19:49             ` John Stoffel
2022-08-28 23:24               ` Peter Sanders
2022-08-29 13:12                 ` Peter Sanders
2022-08-29 21:45                 ` John Stoffel
2022-08-29 22:29                   ` Eyal Lebedinsky
2022-08-29 23:53                     ` Peter Sanders [this message]
2022-08-30 13:27                       ` Peter Sanders
2022-08-30 18:03                         ` Wols Lists
2022-08-31 17:48                           ` Peter Sanders
2022-08-31 20:37                             ` John Stoffel
2022-09-02 14:56                               ` Peter Sanders
2022-09-02 18:52                                 ` Peter Sanders
2022-09-02 19:12                                   ` John Stoffel
2022-09-03  0:39                                     ` Peter Sanders
2022-09-03  5:51                                       ` Peter Sanders
2022-09-05 19:36                                         ` John Stoffel
2022-09-05 20:16                                           ` Peter Sanders
2022-09-05 19:25                                       ` John Stoffel
2022-08-28 15:10 ` John Stoffel
2022-08-28 17:11 ` Andy Smith
2022-08-28 17:22   ` Andy Smith
2022-08-28 17:34     ` Peter Sanders

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='CAKAPSkJhf8hWGTQiCne6BnMPYoum4hJT3diz9U1FGAfq=_N-nA@mail.gmail.com' \
    --to=plsander@gmail.com \
    --cc=fedora@eyal.emu.id.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.