From: CaT <cat@zip.com.au>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid5 stuck in degraded, inactive and dirty mode
Date: Wed, 9 Jan 2008 19:16:34 +1100 [thread overview]
Message-ID: <20080109081634.GS3940@zip.com.au> (raw)
In-Reply-To: <18308.28489.479077.86397@notabene.brown>
On Wed, Jan 09, 2008 at 05:52:57PM +1100, Neil Brown wrote:
> On Wednesday January 9, cat@zip.com.au wrote:
> >
> > I'd provide data dumps of --examine and friends but I'm in a situation
> > where transferring the data would be a right pain. I'll do it if need
> > be, though.
> >
> > So, what can I do?
>
> Well, providing the output of "--examine" would help a lot.
Here's the output of the 3 remaining drives, the array and mdstat.
/proc/mdstat:
Personalities : [raid1] [raid6] [raid5] [raid4]
...
md3 : inactive sdf1[0] sde1[2] sdd1[1]
1465151808 blocks
...
unused devices: <none>
/dev/md3:
Version : 00.90.03
Creation Time : Thu Aug 30 15:50:01 2007
Raid Level : raid5
Device Size : 488383936 (465.76 GiB 500.11 GB)
Raid Devices : 4
Total Devices : 3
Preferred Minor : 3
Persistence : Superblock is persistent
Update Time : Thu Jan 3 08:51:00 2008
State : active, degraded
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
UUID : f60a1be0:5a10f35f:164afef4:10240419
Events : 0.45649
Number Major Minor RaidDevice State
0 8 81 0 active sync /dev/sdf1
1 8 49 1 active sync /dev/sdd1
2 8 65 2 active sync /dev/sde1
3 0 0 - removed
/dev/sdd1:
Magic : a92b4efc
Version : 00.90.03
UUID : f60a1be0:5a10f35f:164afef4:10240419
Creation Time : Thu Aug 30 15:50:01 2007
Raid Level : raid5
Raid Devices : 4
Total Devices : 4
Preferred Minor : 3
Update Time : Thu Jan 3 08:51:00 2008
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : cb259d08 - correct
Events : 0.45649
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 1 8 49 1 active sync /dev/sdd1
0 0 8 81 0 active sync /dev/sdf1
1 1 8 49 1 active sync /dev/sdd1
2 2 8 65 2 active sync /dev/sde1
3 3 8 33 3 active sync /dev/sdc1
/dev/sde1:
Magic : a92b4efc
Version : 00.90.03
UUID : f60a1be0:5a10f35f:164afef4:10240419
Creation Time : Thu Aug 30 15:50:01 2007
Raid Level : raid5
Raid Devices : 4
Total Devices : 4
Preferred Minor : 3
Update Time : Thu Jan 3 08:51:00 2008
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : cb259d1a - correct
Events : 0.45649
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 2 8 65 2 active sync /dev/sde1
0 0 8 81 0 active sync /dev/sdf1
1 1 8 49 1 active sync /dev/sdd1
2 2 8 65 2 active sync /dev/sde1
3 3 8 33 3 active sync /dev/sdc1
/dev/sdf1:
Magic : a92b4efc
Version : 00.90.03
UUID : f60a1be0:5a10f35f:164afef4:10240419
Creation Time : Thu Aug 30 15:50:01 2007
Raid Level : raid5
Raid Devices : 4
Total Devices : 4
Preferred Minor : 3
Update Time : Thu Jan 3 08:51:00 2008
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : cb259d26 - correct
Events : 0.45649
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 0 8 81 0 active sync /dev/sdf1
0 0 8 81 0 active sync /dev/sdf1
1 1 8 49 1 active sync /dev/sdd1
2 2 8 65 2 active sync /dev/sde1
3 3 8 33 3 active sync /dev/sdc1
> But I suspect that "--assemble --force" would do the right thing.
> Without more details, it is hard to say for sure.
I suspect so aswell but throwing caution into the wind erks me wrt this
raid array. :)
--
"To the extent that we overreact, we proffer the terrorists the
greatest tribute."
- High Court Judge Michael Kirby
next prev parent reply other threads:[~2008-01-09 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 5:55 raid5 stuck in degraded, inactive and dirty mode CaT
2008-01-09 6:52 ` Neil Brown
2008-01-09 8:16 ` CaT [this message]
2008-01-10 10:29 ` CaT
2008-01-10 20:21 ` Neil Brown
2008-01-10 22:23 ` CaT
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=20080109081634.GS3940@zip.com.au \
--to=cat@zip.com.au \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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.