From: Richard <richard@radoeka.nl>
To: linux-raid@vger.kernel.org
Subject: Re: RAID-1 not accessible after disk replacement
Date: Fri, 24 May 2024 17:23:49 +0200 [thread overview]
Message-ID: <4705980.vXUDI8C0e8@selene> (raw)
In-Reply-To: <87y180qyyk.fsf@vps.thesusis.net>
Philip, Kuai,
Op donderdag 23 mei 2024 18:23:31 CEST schreef Phillip Susi:
> Richard <richard@radoeka.nl> writes:
> > I grew (--grow) the RAID to an smaller size as it was complaining about
> > the
> > size (no logging of that).
> > After the this action the RAID was functioning and fully accessible.
>
> I think you mean you used -z to reduce the size of the array. It
> appears that you are trying to replace the failed drive with one that is
> half the size, then shrunk the array, which truncated your filesystem,
> which is why you can no longer access it. You can't shrink the disk out
> from under the filesystem.
>
> Grow the array back to the full size of the larger disk and most likely
> you should be able to mount the filesystem again. You will need to get
> a replacement disk that is the same size as the original that failed if
> you want to replace it, or if you can shrink the filesystem to fit on
> the new disk, you have to do that FIRST, then shrink the raid array.
I followed your advice, and made the array size the same as it used to be.
I'm now able to see the data on the partition (RAID) again.
Very nice.
Thanks a lot for your support.
--
Richard
next prev parent reply other threads:[~2024-05-24 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 11:47 RAID-1 not accessible after disk replacement Richard
2024-05-23 12:20 ` Yu Kuai
2024-05-23 12:47 ` Richard
2024-05-23 16:23 ` Phillip Susi
2024-05-24 15:23 ` Richard [this message]
2024-05-24 15:55 ` Richard
2024-05-25 19:27 ` Roger Heflin
2024-05-28 19:04 ` Phillip Susi
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=4705980.vXUDI8C0e8@selene \
--to=richard@radoeka.nl \
--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;
as well as URLs for NNTP newsgroup(s).