All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reindl Harald <h.reindl@thelounge.net>
To: Bob Brand <brand@wmawater.com.au>,
	Roger Heflin <rogerheflin@gmail.com>,
	Wols Lists <antlists@youngman.org.uk>
Cc: Linux RAID <linux-raid@vger.kernel.org>,
	Phil Turmel <philip@turmel.org>, NeilBrown <neilb@suse.com>
Subject: Re: Failed adadm RAID array after aborted Grown operation
Date: Sun, 22 May 2022 13:25:40 +0200	[thread overview]
Message-ID: <d8d15df1-28b6-1569-d13e-4cf411816fa0@thelounge.net> (raw)
In-Reply-To: <054401d86d92$3c59cac0$b50d6040$@wmawater.com.au>



Am 22.05.22 um 06:13 schrieb Bob Brand:
> Is xfs_repair an option? 

unlikely in case the underlying device has all sort of damages - think 
of the RAID like a single disk and how the filesystem reacts if you 
shoot holes in it

> And, if it is, do I run it on md125 or the
> individual sd devices?

when you think two seconds it's obvious - is the filesystem on top of 
single disks or on top of the whole RAID - the filesystem don't even 
know about individual devices

> Unfortunately, restore from back up isn't an option - after all to where do
> you back up 200TB of data? 

on a second machine in a different building - the inital sync is done 
local and then no matter how large the data rsync is enough - the daily 
delta don't vary just because the whole dataset is huge

and don't get me wrong but who starts a reshape on a 200 TB storage when 
he knows that there is no backup?

> This storage was originally set up with the
> understanding that it wasn't backed up and so no valuable data was supposed
> to have been stored on it. 

well, then i won't store it at all

> Unfortunately, people being what they are,
> valuable data has been stored there and I'm the mug now trying to get it
> back - it's a system that I've inherited.


  reply	other threads:[~2022-05-22 11:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08 13:18 Failed adadm RAID array after aborted Grown operation Bob Brand
2022-05-08 15:32 ` Wols Lists
2022-05-08 22:04   ` Bob Brand
2022-05-08 22:15     ` Wol
2022-05-08 22:19       ` Bob Brand
2022-05-08 23:02         ` Bob Brand
2022-05-08 23:32           ` Bob Brand
2022-05-09  0:09             ` Bob Brand
2022-05-09  6:52               ` Wols Lists
2022-05-09 13:07                 ` Bob Brand
     [not found]                 ` <CAAMCDecTb69YY+jGzq9HVqx4xZmdVGiRa54BD55Amcz5yaZo1Q@mail.gmail.com>
2022-05-11  5:39                   ` Bob Brand
2022-05-11 12:35                     ` Reindl Harald
2022-05-11 13:22                       ` Bob Brand
2022-05-11 14:56                         ` Reindl Harald
2022-05-11 14:59                           ` Reindl Harald
2022-05-13  5:32                             ` Bob Brand
2022-05-13  8:18                               ` Reindl Harald
2022-05-20 15:13                   ` Bob Brand
2022-05-20 15:41                     ` Reindl Harald
2022-05-22  4:13                       ` Bob Brand
2022-05-22 11:25                         ` Reindl Harald [this message]
2022-05-22 13:31                         ` Wols Lists
2022-05-22 22:54                           ` Bob Brand

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=d8d15df1-28b6-1569-d13e-4cf411816fa0@thelounge.net \
    --to=h.reindl@thelounge.net \
    --cc=antlists@youngman.org.uk \
    --cc=brand@wmawater.com.au \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=philip@turmel.org \
    --cc=rogerheflin@gmail.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 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.