Re: raid1 recoverable after system crash?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2016-04-07 at 18:00 +0500, Roman Mamedov wrote:
> 
> You do not have a write intent bitmap at md0, so re-add will not
> work.

Ahhh.  OK.

>  Seems
> like you should --add it now,

Tried that.  It started off and got this far:

# cat /proc/mdstat 
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
md0 : active raid1 md1[2](F) sdd[0]
      1953514496 blocks [2/1] [U_]
      [================>....]  recovery = 82.0% (1602507648/1953514496) finish=42613.2min speed=137K/sec

before hitting this:

2016 Apr  7 12:01:00 linux [16583.606363] md/raid1:md0: Disk failure on md1, disabling device.
2016 Apr  7 12:01:00 linux [16583.606366] md/raid1:md0: Operation continuing on 1 devices.
2016 Apr  7 12:01:00 linux FailSpare event detected on md device /dev/md0, component device /dev/md1
2016 Apr  7 12:01:01 linux [16583.907982] BUG: unable to handle kernel paging request at 0000000099b899b8
2016 Apr  7 12:01:01 linux [16583.908009] IP: [<ffffffffa0019227>] call_bio_endio+0x37/0xb0 [raid1]
2016 Apr  7 12:01:01 linux [16583.908009] Oops: 0000 [#1] SMP
2016 Apr  7 12:01:01 linux [16583.908009] Stack:
2016 Apr  7 12:01:01 linux [16583.908009] Call Trace:
2016 Apr  7 12:01:01 linux [16583.908009] Code: 4c 89 65 e0 4c 89 6d e8 4c 89 75 f0 4c 89 7d f8 66 66 66 66 90 4c 8b 67 28 48 8b 47 20 41 bf 01 00 00 00 48 89 fb 41 8b 54 24 2c <4c> 8b 28 85 d2 75 42 48 8b 43 18 a8 01 75 07 3e 41 80 64 24 18
2016 Apr  7 12:01:01 linux [16583.908009] RIP  [<ffffffffa0019227>] call_bio_endio+0x37/0xb0 [raid1]
2016 Apr  7 12:01:01 linux [16583.908009] CR2: 0000000099b899b8

And it seems to be stuck there now.

dmesg contents at http://www.interlinx.bc.ca/~brian/raid-dmesg.txt

>  then after it rebuilds use --grow to add a
> bitmap, so that in the future you could use -re-add.

Cool.  Will do, when this finally gets fixed.

> As to why the situation occured in the first place, you should ensure
> that md1
> assembles before md0.

Yeah.  Just noticed as of this incident that the order in mdadm.conf is
wrong.  :-(

Cheers,
b.

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux