From: NeilBrown <neilb@suse.de>
To: Benjamin ESTRABAUD <be@mpstor.com>
Cc: Salatiel Filho <salatiel.filho@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Raid over USB disks and eject
Date: Tue, 13 Nov 2012 07:28:34 +1100 [thread overview]
Message-ID: <20121113072834.1af12558@notabene.brown> (raw)
In-Reply-To: <50A11EC0.1060203@mpstor.com>
[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]
On Mon, 12 Nov 2012 16:07:28 +0000 Benjamin ESTRABAUD <be@mpstor.com> wrote:
> Hi!
>
> You could setup a cron job that will pause the resync by writing to sysfs:
>
> If your array if "md0":
>
> echo "idle" > /sys/block/md0/md/sync_action
"idle" is not sufficient. It will stop the recovery, but then it will
immediately start again.
You need "frozen".
NeilBrown
>
> However, this is probably not necessary as the resynced stripes will be
> marked in the bitmap, meaning that if your rebuild fails, re-assembling
> the array should restart the resync from where it stopped.
>
> Regards,
> Ben.
>
> On 12/11/12 12:44, Salatiel Filho wrote:
> > Hi guys, i have an external USB enclosure with 4 disks in RAID5 mode
> > using mdadm. I dont know exactly why but if i use this disks for
> > massive I/O for lots of hours (over 12 hours), linux usually eject
> > some or all disks (causing a faulty in the raid) and remaps them: sdb
> > -> sdf , sdc -> sdg , sdd -> sdh , sde -> sdi
> > Well , this was never exactly a problem because most of the time those
> > disks are idle (just backup), but i had a real disk failure and i will
> > replace the disk. But probably the rebuild process will take a lot
> > more than 12 hours so the chances are that some disk will be ejected
> > and i will be in a trouble situation where a raid5 rebuilding process
> > will probably be stopped by an apparently failure. So my question is:
> >
> > If i get into that situation , will i be able to disassemble and
> > reassemble the disk using the three disks i know are 'fine' and
> > restart the rebuild process from where it stopped ? I have internal
> > bitmap enabled.
> >
> > Is it possible to somehow freeze the rebuild process ? So i could
> > pause the process for a few hours after 8 hours of work for example.
> >
> > The raid will be assembled but umounted during the rebuild proccess.
> >
> > I am using kernel 3.2.30.
> >
> > Thanks !!!
> >
> >
> > []'s
> > Salatiel
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> > the body of a message tomajordomo@vger.kernel.org
> > More majordomo info athttp://vger.kernel.org/majordomo-info.html
> >
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-11-12 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 12:44 Raid over USB disks and eject Salatiel Filho
2012-11-12 16:07 ` Benjamin ESTRABAUD
2012-11-12 20:28 ` NeilBrown [this message]
2012-11-14 16:25 ` Salatiel Filho
[not found] ` <50A11B2C.7070902@mpstor.com>
2012-11-12 16:10 ` Salatiel Filho
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=20121113072834.1af12558@notabene.brown \
--to=neilb@suse.de \
--cc=be@mpstor.com \
--cc=linux-raid@vger.kernel.org \
--cc=salatiel.filho@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox