From: Carsten Aulbert <Carsten.Aulbert@aei.mpg.de>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Recovering from two almost simultaneously failed devices in RAID1
Date: Sat, 10 Aug 2013 19:39:39 +0200 [thread overview]
Message-ID: <52067ADB.8080100@aei.mpg.de> (raw)
In-Reply-To: <52066B43.1010901@aei.mpg.de>
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
*sigh*
Thanks to me being at home and only IPMI access with relatively high
latencies, I did not manage to boot into single user mode and the system
booted up normally - luckily for me, both md and ext4 tell me, the file
system is safe and ok.
# mdadm --detail /dev/md2
/dev/md2:
Version : 1.2
Creation Time : Fri Jul 27 11:58:50 2012
Raid Level : raid1
Array Size : 250050533 (238.47 GiB 256.05 GB)
Used Dev Size : 250050533 (238.47 GiB 256.05 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Sat Aug 10 19:38:01 2013
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Name : gitmaster:2 (local to host gitmaster)
UUID : 7cb262a7:54496605:238cc0bf:6fa6a3e9
Events : 61
Number Major Minor RaidDevice State
0 8 49 0 active sync /dev/sdd1
1 8 33 1 active sync /dev/sdc1
I think I got really lucky (still running checks on the git repositories
on this md).
Anyone who experienced such a problem with SSDs (or HDDs) being
disconnected like this?
Cheers
Carsten
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2044 bytes --]
next prev parent reply other threads:[~2013-08-10 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 16:29 Recovering from two almost simultaneously failed devices in RAID1 Carsten Aulbert
2013-08-10 16:33 ` Carsten Aulbert
2013-08-10 17:39 ` Carsten Aulbert [this message]
2013-08-10 17:45 ` Mathias Burén
2013-08-10 18:05 ` Carsten Aulbert
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=52067ADB.8080100@aei.mpg.de \
--to=carsten.aulbert@aei.mpg.de \
--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