From: David Niklas <simd@vfemail.net>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Array will not resync.
Date: Mon, 19 Feb 2024 23:07:19 -0500 [thread overview]
Message-ID: <20240219230719.09c5a795@firefly> (raw)
In-Reply-To: <CAJj0OutmJKP6F1ZRMEoNQyYgJsM+ZUXMzLE5mOzhAAiiF34xRw@mail.gmail.com>
Ah! I needed to issue repair to the sync_action. Thanks!
mdstat looks normal.
David
On Sun, 18 Feb 2024 19:47:19 -0800
"C.J. Collier" <cjac@colliertech.org> wrote:
> Does the content of /proc/mdstat look interesting to you?
>
> On Sun, Feb 18, 2024, 17:13 Yu Kuai <yukuai1@huaweicloud.com> wrote:
>
> > Hi,
> >
> > 在 2024/02/19 0:23, simd@vfemail.net 写道:
> > > Hello,
> > >
> > > I cannot get my RAID 6 array to resync.
> > >
> > > I'm using mdadm version v4.1. I've tried kernels 5.18.X, 6.0.X, and
> > > 6.3.X on Devuan (Debian) Linux.
> > >
> > > % echo resync > /sys/devices/virtual/block/md127/md/sync_action
> > >
> > > Does nothing.
> > >
> > > % mdadm --assemble --update=resync /dev/md127
> > >
> > > Does nothing.
> >
> > Please note that resync is one-time after assemble the array the first
> > time, you can't resync again after the array is clean.
> >
> > >
> > > I should see a status change to resync with mdadm
> > > --detail /dev/md127 and hear some activity from the drives.
> > >
> > > I tried adding the verbose option, but it only lists the
> > > recognizing of the drives and adding them to the array.
> > >
> > > The array currently has some mismatches which need to be corrected.
> > > It's currently registering all devices in "active sync" status and
> > > says that it is "clean".
> >
> > What you want is "echo check > sync_action", then "cat mismatch_cnt",
> > if there are really mismatches, "echo repair > sync_action" to fix it.
> >
> > Thanks,
> > Kuai
> >
> > >
> > > I tried setting the flag, in misc mode, to readonly and then back to
> > > readwrite but that still doesn't allow the array to be resync'd.
> > >
> > > In desperation, I tried unplugging one of the drives, it holds
> > > most/all of the mismatches -- the SATA cable was going bad, and
> > > then I touch(1)ed
> > a
> > > file on the FS and unmounted the FS. Although the array recognized
> > > the failure of the drive, it did not start resync the array upon
> > > adding the drive back into the array.
> > >
> > >
> > >
> > >
> > > Any ideas how to resync the array?
> > >
> > > Thanks,
> > > David
> > >
> > > .
> > >
> >
> >
> >
prev parent reply other threads:[~2024-02-20 4:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 16:23 Array will not resync simd
2024-02-19 1:13 ` Yu Kuai
[not found] ` <CAJj0OutmJKP6F1ZRMEoNQyYgJsM+ZUXMzLE5mOzhAAiiF34xRw@mail.gmail.com>
2024-02-20 4:07 ` David Niklas [this message]
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=20240219230719.09c5a795@firefly \
--to=simd@vfemail.net \
--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.