* Re: Recovery Raid6 Degraded
From: Emanuel Domingos @ 2015-04-14 12:47 UTC (permalink / raw)
To: Mikael Abrahamsson; +Cc: linux-raid
In-Reply-To: <alpine.DEB.2.02.1504132234220.16871@uplift.swm.pp.se>
Hi, Mikael, hi guys!
Follow the errors found after building the new version of mdadm:
#mdadm --stop /dev/md/ubuntu\:md-raid6_primary
#mdadm --assemble --force /dev/md/ubuntu\:md-raid6_primary /dev/sdaa
/dev/sdac /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdz
mdadm: device /dev/md/ubuntu:md-raid6_primary exists but is not an md array.
DMESG
[661924.167503] md: md123 stopped.
[661924.167513] md: unbind<sdi>
[661924.184248] md: export_rdev(sdi)
[661924.184259] md: unbind<sdj>
[661924.184324] md: export_rdev(sdj)
[661924.184335] md: unbind<sdg>
[661924.188227] md: export_rdev(sdg)
[661924.188248] md: unbind<sdh>
[661924.192285] md: export_rdev(sdh)
[661924.192296] md: unbind<sdf>
[661924.192364] md: export_rdev(sdf)
[661924.192375] md: unbind<sdz>
[661924.264120] md: export_rdev(sdz)
[661924.264133] md: unbind<sdaa>
[661924.264456] md: export_rdev(sdaa)
[661924.264467] md: unbind<sdac>
[661924.272138] md: export_rdev(sdac)
Thanks!
2015-04-13 17:38 GMT-03:00 Mikael Abrahamsson <swmike@swm.pp.se>:
> On Mon, 13 Apr 2015, Emanuel Domingos wrote:
>
>> guys, following guidelines on wiki, before to try recreate my array
>> I'm sending this mail to listen the experts.
>
>
> Good choice!
>
>> I would like to aid as a problem in my raid arrays after a crash in
>> which I had to restart the server.
>
>
> What kernel version and mdadm version are you running?
>
> My first recommendation would be for you to compile latest mdadm from
> source:
>
> "git clone https://github.com/neilbrown/mdadm"
>
> Then compile it and use that to do the --assemble-force operation that
> failed before. This has helped others.
>
> If it still doesn't work, please provide dmesg output from when that
> operation occured.
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
--
Emanuel Domingos
Cursando Bacharelado em Ciência da Computação - IFCE Campus Maracanaú
Técnico em Conectividade - IFCE Campus Maracanaú
--
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
^ permalink raw reply
* Re: Recovery Raid6 Degraded
From: Emanuel Domingos @ 2015-04-14 12:58 UTC (permalink / raw)
To: linux-raid
In-Reply-To: <CACsoFmjWW7mqSA8OKZZEPhpFidf-exSMm771ZOp0TssSYydcrw@mail.gmail.com>
Hi, Mikael, hi guys!
Follow the errors found after building the new version of mdadm:
#mdadm --stop /dev/md/ubuntu\:md-raid6_primary
#mdadm --assemble --force /dev/md/ubuntu\:md-raid6_primary /dev/sdaa
/dev/sdac /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdz
mdadm: device /dev/md/ubuntu:md-raid6_primary exists but is not an md array.
DMESG
[661924.167503] md: md123 stopped.
[661924.167513] md: unbind<sdi>
[661924.184248] md: export_rdev(sdi)
[661924.184259] md: unbind<sdj>
[661924.184324] md: export_rdev(sdj)
[661924.184335] md: unbind<sdg>
[661924.188227] md: export_rdev(sdg)
[661924.188248] md: unbind<sdh>
[661924.192285] md: export_rdev(sdh)
[661924.192296] md: unbind<sdf>
[661924.192364] md: export_rdev(sdf)
[661924.192375] md: unbind<sdz>
[661924.264120] md: export_rdev(sdz)
[661924.264133] md: unbind<sdaa>
[661924.264456] md: export_rdev(sdaa)
[661924.264467] md: unbind<sdac>
[661924.272138] md: export_rdev(sdac)
2015-04-13 16:59 GMT-03:00 Emanuel Domingos <emanuelsdrock@gmail.com>:
> guys, following guidelines on wiki, before to try recreate my array
> I'm sending this mail to listen the experts.
>
> I would like to aid as a problem in my raid arrays after a crash in
> which I had to restart the server.
>
> After the restart, the situation was as follows:
>
> # ls -lh /dev/md/
>
> lrwxrwxrwx 1 root root 8 Apr 6 17:35 ubuntu:md-flash -> ../md125
> lrwxrwxrwx 1 root root 10 Apr 6 17:34 ubuntu:md-raid6_2 -> /dev/md127
> lrwxrwxrwx 1 root root 8 Apr 6 17:35 ubuntu:md-raid6-bacula -> ../md126
> lrwxrwxrwx 1 root root 10 Apr 6 17:34 ubuntu:md-raid6_primary -> /dev/md124
>
> # cat /proc/mdstat
>
> md124 : inactive sdh[2] sdf[0] sdg[1]
> 5860540680 blocks super 1.2
>
> md125 : active (auto-read-only) raid1 sdag[1]
> 97684688 blocks super 1.2 [2/1] [_U]
>
> md126 : active (auto-read-only) raid6 sdad[1] sdv[2] sdy[5] sdw[3] sdx[4]
> 7814051840 blocks super 1.2 level 6, 512k chunk, algorithm 2
> [6/5] [_UUUUU]
>
> md127 : inactive sdd[13] sdc[15] sde[14] sda[10] sdb[11] sdt[4] sdr[2]
> sdq[1] sdm[7] sdk[5] sdo[9] sdn[8]
> 23442162720 blocks super 1.2
>
>
> Did anyone some tip for me? My focus is to restore 'primary' raid fow now.
> for now
> My hardware is 2 pci express sata contollers conected each one on tow
> 5x1 sata multiplexer.
>
> Follow detail /dev/md124:
>
> # mdadm --detail /dev/md124
>
> Version : 1.2
> Creation Time : Thu Sep 27 11:39:20 2012
> Raid Level : raid6
> Used Dev Size : 1953512960 (1863.02 GiB 2000.40 GB)
> Raid Devices : 8
> Total Devices : 3
> Persistence : Superblock is persistent
>
> Update Time : Mon Apr 6 04:09:06 2015
> State : active, FAILED, Not Started
> Active Devices : 3
> Working Devices : 3
> Failed Devices : 0
> Spare Devices : 0
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Name : ubuntu:md-raid6_primary (local to host ubuntu)
> UUID : cee8d180:d6275a41:599064c6:8894819e
> Events : 1093684
>
> Number Major Minor RaidDevice State
> 0 8 80 0 active sync /dev/sdf
> 1 8 96 1 active sync /dev/sdg
> 2 8 112 2 active sync /dev/sdh
> 3 0 0 3 removed
> 4 0 0 4 removed
> 5 0 0 5 removed
> 6 0 0 6 removed
> 7 0 0 7 removed
>
>
> I tried to assemble with "mdadm --assemble --force
> /dev/md/ubuntu\:md-raid6_primary /dev/sdaa /dev/sdac /dev/sdf /dev/sdg
> /dev/sdh /dev/sdi /dev/sdj /dev/sdz" ('primary' raid) but my result
> was this
>
> cat /proc/mdstat after mdadm --assemble...
>
> Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5]
> [raid4] [raid10]
> md123 : inactive sdi[3](S) sdj[8](S) sdg[1](S) sdh[2](S) sdf[0](S)
> sdz[5](S) sdaa[6](S) sdac[7](S)
> 15628108480 blocks super 1.2
>
> md125 : active (auto-read-only) raid1 sdag[1]
> 97684688 blocks super 1.2 [2/1] [_U]
>
> md126 : active raid6 sdad[1] sdv[2] sdy[5] sdw[3] sdx[4]
> 7814051840 blocks super 1.2 level 6, 512k chunk, algorithm 2
> [6/5] [_UUUUU]
>
> md127 : inactive sdd[13] sdc[15] sde[14] sda[10] sdb[11] sdt[4] sdr[2]
> sdq[1] sdm[7] sdk[5] sdo[9] sdn[8]
> 23442162720 blocks super 1.2
>
> unused devices: <none>
>
>
> Detail for /dev/md123
>
> #mdadm --detail /dev/123 shows the output:
>
> mdadm: md device /dev/md123 does not appear to be active.
>
>
> The name change /dev/md124 -> /dev/md123. output ls -lh /dev/md
>
> #ls -lh /dev/md
>
> lrwxrwxrwx 1 root root 8 Apr 6 17:35 ubuntu:md-flash -> ../md125
> lrwxrwxrwx 1 root root 10 Apr 6 17:34 ubuntu:md-raid6_2 -> /dev/md127
> lrwxrwxrwx 1 root root 8 Apr 6 17:35 ubuntu:md-raid6-bacula -> ../md126
> lrwxrwxrwx 1 root root 10 Apr 6 17:34 ubuntu:md-raid6_primary -> /dev/md124
>
>
> LIST OF DISKS:
>
> ARRAY PRIMARY (md-raid6_primary)
>
> /dev/sdaa
> /dev/sdac
> /dev/sdf
> /dev/sdg
> /dev/sdh
> /dev/sdi
> /dev/sdj
> /dev/sdz
>
> ARRAY BACULA (md-raid6-bacula)
>
> /dev/sdab
> /dev/sdad
> /dev/sdv
> /dev/sdw
> /dev/sdx
> /dev/sdy
>
> ARRAY FLASH (md-flash)
>
> /dev/sdaf
> /dev/sdag
>
> ARRAY SECONDARY (md-raid6_2)
>
> /dev/sda
> /dev/sdb
> /dev/sdc
> /dev/sdd
> /dev/sde
> /dev/sdk
> /dev/sdl
> /dev/sdm
> /dev/sdn
> /dev/sdo
> /dev/sdp
> /dev/sdq
> /dev/sdr
> /dev/sds
> /dev/sdt
>
> OUTPUT dmesg:
>
> [487229.059007] end_request: I/O error, dev sdae, sector 3560087488
> [487249.705034] end_request: I/O error, dev sdae, sector 3560087488
> [572716.092783] end_request: I/O error, dev sdx, sector 1954527040
> [573492.373689] end_request: I/O error, dev sdae, sector 3560087488
> [573513.171095] end_request: I/O error, dev sdae, sector 3560087488
> [573533.807073] end_request: I/O error, dev sdae, sector 3560087488
> [573556.188797] end_request: I/O error, dev sdae, sector 3560087488
> [573576.996265] end_request: I/O error, dev sdae, sector 3560087488
>
> OUTPUT mdadm -E all_devices:
>
> /dev/sdaa:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : cee8d180:d6275a41:599064c6:8894819e
> Name : ubuntu:md-raid6_primary (local to host ubuntu)
> Creation Time : Thu Sep 27 11:39:20 2012
> Raid Level : raid6
> Raid Devices : 8
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 23442155520 (11178.09 GiB 12002.38 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : f6227bf3:2f25dbde:db6509e4:57a5dbe2
>
> Update Time : Mon Apr 6 03:53:41 2015
> Checksum : ea5c72c1 - correct
> Events : 1093681
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 6
> Array State : AAA..AAA ('A' == active, '.' == missing)
>
> /dev/sdac:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : cee8d180:d6275a41:599064c6:8894819e
> Name : ubuntu:md-raid6_primary (local to host ubuntu)
> Creation Time : Thu Sep 27 11:39:20 2012
> Raid Level : raid6
> Raid Devices : 8
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 23442155520 (11178.09 GiB 12002.38 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 912783f6:c39a8aad:7fb5018a:d4bdd201
>
> Update Time : Mon Apr 6 03:53:41 2015
> Checksum : 81035511 - correct
> Events : 1093681
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 7
> Array State : AAA..AAA ('A' == active, '.' == missing)
>
> /dev/sdf:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : cee8d180:d6275a41:599064c6:8894819e
> Name : ubuntu:md-raid6_primary (local to host ubuntu)
> Creation Time : Thu Sep 27 11:39:20 2012
> Raid Level : raid6
> Raid Devices : 8
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 23442155520 (11178.09 GiB 12002.38 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : clean
> Device UUID : f9131d59:1fa41bca:5df029d1:bd5e0158
>
> Update Time : Mon Apr 6 04:09:06 2015
> Checksum : 9d762a2f - correct
> Events : 1093684
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 0
> Array State : AAA..... ('A' == active, '.' == missing)
>
> /dev/sdg:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : cee8d180:d6275a41:599064c6:8894819e
> Name : ubuntu:md-raid6_primary (local to host ubuntu)
> Creation Time : Thu Sep 27 11:39:20 2012
> Raid Level : raid6
> Raid Devices : 8
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 23442155520 (11178.09 GiB 12002.38 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : clean
> Device UUID : 4cfae88d:49377cb6:58042dfb:82fa744e
>
> Update Time : Mon Apr 6 04:09:06 2015
> Checksum : df19536d - correct
> Events : 1093684
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 1
> Array State : AAA..... ('A' == active, '.' == missing)
>
> /dev/sdh:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : cee8d180:d6275a41:599064c6:8894819e
> Name : ubuntu:md-raid6_primary (local to host ubuntu)
> Creation Time : Thu Sep 27 11:39:20 2012
> Raid Level : raid6
> Raid Devices : 8
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 23442155520 (11178.09 GiB 12002.38 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : clean
> Device UUID : f6a4ada7:207315c0:96a2f83b:9f0199d4
>
> Update Time : Mon Apr 6 04:09:06 2015
> Checksum : c966e242 - correct
> Events : 1093684
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 2
> Array State : AAA..... ('A' == active, '.' == missing)
>
> /dev/sdi:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : cee8d180:d6275a41:599064c6:8894819e
> Name : ubuntu:md-raid6_primary (local to host ubuntu)
> Creation Time : Thu Sep 27 11:39:20 2012
> Raid Level : raid6
> Raid Devices : 8
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 23442155520 (11178.09 GiB 12002.38 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 17f6f6ba:25d71c20:7e945a21:d3432130
>
> Update Time : Mon Mar 30 20:38:33 2015
> Checksum : 7dad75f8 - correct
> Events : 1093684
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 3
> Array State : AAAA.AAA ('A' == active, '.' == missing)
>
> /dev/sdj:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : cee8d180:d6275a41:599064c6:8894819e
> Name : ubuntu:md-raid6_primary (local to host ubuntu)
> Creation Time : Thu Sep 27 11:39:20 2012
> Raid Level : raid6
> Raid Devices : 8
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 23442155520 (11178.09 GiB 12002.38 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : eb58254f:fca9077b:37214548:a828733f
>
> Update Time : Thu Mar 26 04:33:44 2015
> Checksum : a2fbf51b - correct
> Events : 1093684
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 4
> Array State : AAAAAAAA ('A' == active, '.' == missing)
>
>
> /dev/sdz:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : cee8d180:d6275a41:599064c6:8894819e
> Name : ubuntu:md-raid6_primary (local to host ubuntu)
> Creation Time : Thu Sep 27 11:39:20 2012
> Raid Level : raid6
> Raid Devices : 8
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 23442155520 (11178.09 GiB 12002.38 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 9a71d9ba:0954c58b:49d41aed:6ad7fa48
>
> Update Time : Mon Apr 6 03:53:41 2015
> Checksum : cdd590c1 - correct
> Events : 1093684
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 5
> Array State : AAA..AAA ('A' == active, '.' == missing)
>
>
> ARRAY BACULA
>
> /dev/sdab:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 001f075c:ee06ae37:c0969316:a46c843b
> Name : ubuntu:md-raid6-bacula (local to host ubuntu)
> Creation Time : Thu Sep 27 17:15:15 2012
> Raid Level : raid6
> Raid Devices : 6
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 15628103680 (7452.06 GiB 8001.59 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : fe51b5fd:941292b0:c66da01b:85e972d5
>
> Update Time : Tue Dec 30 11:46:29 2014
> Checksum : 8423da96 - correct
> Events : 439
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 0
> Array State : AAAAAA ('A' == active, '.' == missing)
>
> /dev/sdad:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 001f075c:ee06ae37:c0969316:a46c843b
> Name : ubuntu:md-raid6-bacula (local to host ubuntu)
> Creation Time : Thu Sep 27 17:15:15 2012
> Raid Level : raid6
> Raid Devices : 6
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 15628103680 (7452.06 GiB 8001.59 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 0a39d4dc:d1834661:72ee59e9:1bcd650b
>
> Update Time : Mon Apr 13 09:59:52 2015
> Checksum : 184d5e9a - correct
> Events : 2082350
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 1
> Array State : .AAAAA ('A' == active, '.' == missing)
>
> /dev/sdv:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 001f075c:ee06ae37:c0969316:a46c843b
> Name : ubuntu:md-raid6-bacula (local to host ubuntu)
> Creation Time : Thu Sep 27 17:15:15 2012
> Raid Level : raid6
> Raid Devices : 6
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 15628103680 (7452.06 GiB 8001.59 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 42fc3b73:ce28a790:321d18d3:14fd029d
>
> Update Time : Mon Apr 13 10:00:05 2015
> Checksum : 597125a8 - correct
> Events : 2082368
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 2
> Array State : .AAAAA ('A' == active, '.' == missing)
>
> /dev/sdw:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 001f075c:ee06ae37:c0969316:a46c843b
> Name : ubuntu:md-raid6-bacula (local to host ubuntu)
> Creation Time : Thu Sep 27 17:15:15 2012
> Raid Level : raid6
> Raid Devices : 6
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 15628103680 (7452.06 GiB 8001.59 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 7c34659e:5c432ccb:80185072:3146a69a
>
> Update Time : Mon Apr 13 10:00:05 2015
> Checksum : 5bfabcdc - correct
> Events : 2082368
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 3
> Array State : .AAAAA ('A' == active, '.' == missing)
>
> /dev/sdx:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 001f075c:ee06ae37:c0969316:a46c843b
> Name : ubuntu:md-raid6-bacula (local to host ubuntu)
> Creation Time : Thu Sep 27 17:15:15 2012
> Raid Level : raid6
> Raid Devices : 6
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 15628103680 (7452.06 GiB 8001.59 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 8e0d1c2b:9e5e86f4:5121676e:ef6b4951
>
> Update Time : Mon Apr 13 10:00:05 2015
> Checksum : c4c5eaff - correct
> Events : 2082368
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 4
> Array State : .AAAAA ('A' == active, '.' == missing)
>
> /dev/sdy:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 001f075c:ee06ae37:c0969316:a46c843b
> Name : ubuntu:md-raid6-bacula (local to host ubuntu)
> Creation Time : Thu Sep 27 17:15:15 2012
> Raid Level : raid6
> Raid Devices : 6
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 15628103680 (7452.06 GiB 8001.59 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 2c061cce:58eff44d:633cce36:22aebbb4
>
> Update Time : Mon Apr 13 10:00:05 2015
> Checksum : ed0dc65d - correct
> Events : 2082368
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 5
> Array State : .AAAAA ('A' == active, '.' == missing)
>
> ARRAY FLASH
>
> /dev/sdaf:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 9ae996a5:b8cef013:6163d4f2:e4fc50e9
> Name : ubuntu:md-flash (local to host ubuntu)
> Creation Time : Thu Sep 4 15:58:58 2014
> Raid Level : raid1
> Raid Devices : 2
>
> Avail Dev Size : 234439600 (111.79 GiB 120.03 GB)
> Array Size : 195369376 (93.16 GiB 100.03 GB)
> Used Dev Size : 195369376 (93.16 GiB 100.03 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 8242b575:8a255c04:6a9b17a1:c92a3364
>
> Update Time : Thu Mar 12 19:18:00 2015
> Checksum : c89e3c42 - correct
> Events : 149
>
> Device Role : Active device 0
> Array State : AA ('A' == active, '.' == missing)
>
> /dev/sdag:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 9ae996a5:b8cef013:6163d4f2:e4fc50e9
> Name : ubuntu:md-flash (local to host ubuntu)
> Creation Time : Thu Sep 4 15:58:58 2014
> Raid Level : raid1
> Raid Devices : 2
>
> Avail Dev Size : 195369520 (93.16 GiB 100.03 GB)
> Array Size : 195369376 (93.16 GiB 100.03 GB)
> Used Dev Size : 195369376 (93.16 GiB 100.03 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : clean
> Device UUID : 7aef1a7d:529d6a8e:5d8df6fe:c621fda7
>
> Update Time : Mon Apr 6 08:41:23 2015
> Checksum : f99dc861 - correct
> Events : 1394745
>
>
> Device Role : Active device 1
> Array State : .A ('A' == active, '.' == missing)
>
> ARRAY SECONDARY (2)
>
> /dev/sda:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 5b5f642d:98b070d8:1db552b3:f2cd400d
>
> Update Time : Mon Apr 6 04:09:07 2015
> Checksum : b853be69 - correct
> Events : 1687638
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 10
> Array State : .AA.AA.AAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sdae:
> MBR Magic : aa55
> Partition[0] : 3907029167 sectors at 1 (type ee)
>
> /dev/sdb:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : c6ea8392:7a154f08:514b5790:225afb6d
>
> Update Time : Mon Apr 6 04:09:07 2015
> Checksum : 8b10e35b - correct
> Events : 1687638
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 11
> Array State : .AA.AA.AAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sdc:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 7c612542:eaea873e:70998b44:510981c5
>
> Update Time : Mon Apr 6 04:09:07 2015
> Checksum : 7ca51a93 - correct
> Events : 1687638
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 12
> Array State : .AA.AA.AAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sdd:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 81c06400:83b34ee6:4ba3f678:73b6383a
>
> Update Time : Mon Apr 6 04:09:07 2015
> Checksum : 8bce0e54 - correct
> Events : 1687638
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 13
> Array State : .AA.AA.AAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sde:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : dff1662e:f4b3d490:759f1c84:0f25bd77
>
> Update Time : Mon Apr 6 04:09:07 2015
> Checksum : ad0095c2 - correct
> Events : 1687638
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 14
> Array State : .AA.AA.AAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sdk:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 4419c60e:832defe9:3608aeb5:0c9ad899
>
> Update Time : Mon Apr 6 04:09:07 2015
> Checksum : 3a27146c - correct
> Events : 1687638
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 5
> Array State : .AA.AA.AAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sdl:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 83b744ab:d39a7fa0:790c4745:1a330f22
>
> Update Time : Mon Apr 6 03:53:16 2015
> Checksum : a504b986 - correct
> Events : 1687615
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 6
> Array State : .AA.AAAAAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sdm:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 74a5554b:60bc1caf:0f606353:4cd70807
>
> Update Time : Mon Apr 6 04:09:07 2015
> Checksum : 46c9c493 - correct
> Events : 1687638
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 7
> Array State : .AA.AA.AAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sdn:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : e922ebba:63a4fd5f:3cf1ed29:6625c141
>
> Update Time : Mon Apr 6 04:09:07 2015
> Checksum : 78830953 - correct
> Events : 1687638
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 8
> Array State : .AA.AA.AAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sdo:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : b866bcbd:5b768cae:f280dfd3:a6fa4bb0
>
> Update Time : Mon Apr 6 04:09:07 2015
> Checksum : e25f8412 - correct
> Events : 1687638
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 9
> Array State : .AA.AA.AAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sdp:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : d0435b9e:e3be7bc9:066b5f4a:c1bc1879
>
> Update Time : Sat Mar 14 13:16:16 2015
> Checksum : 1d09cb6f - correct
> Events : 343654
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 0
> Array State : AAA.AAAAAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sdq:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : b3c0ebc7:608cf642:a714996a:1f6f6a43
>
> Update Time : Mon Apr 6 04:09:07 2015
> Checksum : aad0fc37 - correct
> Events : 1687638
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 1
> Array State : .AA.AA.AAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sdr:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 2a527d72:0042643b:d86fc040:43763b9c
>
> Update Time : Mon Apr 6 04:09:07 2015
> Checksum : 7cc8a5a4 - correct
> Events : 1687638
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 2
> Array State : .AA.AA.AAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sds:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : a13aed14:981145b2:0bfe76a9:e2d39512
>
> Update Time : Thu Mar 12 04:01:24 2015
> Checksum : 74f446c3 - correct
> Events : 111833
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 3
> Array State : AAAAAAAAAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sdt:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 0aac0176:0d0bfb36:9d06836e:345e031a
> Name : ubuntu:md-raid6_2 (local to host ubuntu)
> Creation Time : Thu Sep 27 10:58:00 2012
> Raid Level : raid6
> Raid Devices : 15
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 50791336960 (24219.20 GiB 26005.16 GB)
> Used Dev Size : 3907025920 (1863.02 GiB 2000.40 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : active
> Device UUID : 8c6f02f3:23411071:3fc98d04:d237ed37
>
> Update Time : Mon Apr 6 04:09:07 2015
> Checksum : 9278dd21 - correct
> Events : 1687638
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 4
> Array State : .AA.AA.AAAAAAAA ('A' == active, '.' == missing)
>
> /dev/sdu:
> MBR Magic : aa55
> Partition[0] : 3907027120 sectors at 2048 (type 83)
>
>
> OUTPUT lshw:
>
> *-pci
> description: Host bridge
> product: 2nd Generation Core Processor Family DRAM Controller
> vendor: Intel Corporation
> physical id: 100
> bus info: pci@0000:00:00.0
> version: 09
> width: 32 bits
> clock: 33MHz
> configuration: driver=agpgart-intel
> resources: irq:0
> *-pci:0
> description: PCI bridge
> product: Xeon E3-1200/2nd Generation Core Processor
> Family PCI Express Root Port
> vendor: Intel Corporation
> physical id: 1
> bus info: pci@0000:00:01.0
> version: 09
> width: 32 bits
> clock: 33MHz
> capabilities: pci pm msi pciexpress normal_decode
> bus_master cap_list
> configuration: driver=pcieport
> resources: irq:40
> *-pci:1
> description: PCI bridge
> product: Xeon E3-1200/2nd Generation Core Processor
> Family PCI Express Root Port
> vendor: Intel Corporation
> physical id: 1.1
> bus info: pci@0000:00:01.1
> version: 09
> width: 32 bits
> clock: 33MHz
> capabilities: pci pm msi pciexpress normal_decode
> bus_master cap_list
> configuration: driver=pcieport
> resources: irq:41 ioport:e000(size=4096) memory:fbb00000-fbbfffff
> *-storage
> description: RAID bus controller
> product: SiI 3132 Serial ATA Raid II Controller
> vendor: Silicon Image, Inc.
> physical id: 0
> bus info: pci@0000:02:00.0
> logical name: scsi0
> logical name: scsi1
> version: 01
> width: 64 bits
> clock: 33MHz
> capabilities: storage pm msi pciexpress bus_master
> cap_list rom emulated
> configuration: driver=sata_sil24 latency=0
> resources: irq:17 memory:fbb84000-fbb8407f
> memory:fbb80000-fbb83fff ioport:e000(size=128)
> memory:fbb00000-fbb7ffff
> *-disk:0
> description: ATA Disk
> product: SAMSUNG HD204UI
> physical id: 0
> bus info: scsi@0:0.0.0
> logical name: /dev/sda
> version: 1AQ1
> serial: S2N6J50B800969
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=20af5a10
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@0:0.0.0,1
> logical name: /dev/sda1
> capacity: 1863GiB
> capabilities: primary
> *-disk:1
> description: ATA Disk
> product: SAMSUNG HD204UI
> physical id: 1
> bus info: scsi@0:1.0.0
> logical name: /dev/sdb
> version: 1AQ1
> serial: S2N6J50B800971
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=822181a7
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@0:1.0.0,1
> logical name: /dev/sdb1
> capacity: 1863GiB
> capabilities: primary
> *-disk:2
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 2
> bus info: scsi@0:2.0.0
> logical name: /dev/sdc
> version: ML6O
> serial: ML2220F30YLVBE
> size: 1863GiB (2TB)
> configuration: ansiversion=5
> *-disk:3
> description: ATA Disk
> product: SAMSUNG HD204UI
> physical id: 3
> bus info: scsi@0:3.0.0
> logical name: /dev/sdd
> version: 1AQ1
> serial: S2N6J50B800952
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=f6e5951b
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@0:3.0.0,1
> logical name: /dev/sdd1
> capacity: 1863GiB
> capabilities: primary
> *-disk:4
> description: ATA Disk
> product: SAMSUNG HD204UI
> physical id: 4
> bus info: scsi@0:4.0.0
> logical name: /dev/sde
> version: 1AQ1
> serial: S2N6J50B800950
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=2ecdc2ce
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@0:4.0.0,1
> logical name: /dev/sde1
> capacity: 1863GiB
> capabilities: primary
> *-disk:5
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 5
> bus info: scsi@1:0.0.0
> logical name: /dev/sdf
> version: ML6O
> serial: ML2220F30V22NE
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=3783f5ab
> *-volume UNCLAIMED
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@1:0.0.0,1
> capacity: 1863GiB
> capabilities: primary
> *-disk:6
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 6
> bus info: scsi@1:1.0.0
> logical name: /dev/sdg
> version: ML6O
> serial: ML2220F32PN2ME
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=3cbd062e
> *-volume UNCLAIMED
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@1:1.0.0,1
> capacity: 1863GiB
> capabilities: primary
> *-disk:7
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 7
> bus info: scsi@1:2.0.0
> logical name: /dev/sdh
> version: ML6O
> serial: ML2220F32PNAPE
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=b6c83342
> *-volume UNCLAIMED
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@1:2.0.0,1
> capacity: 1863GiB
> capabilities: primary
> *-disk:8
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 8
> bus info: scsi@1:3.0.0
> logical name: /dev/sdi
> version: ML6O
> serial: ML2220F30WZYHE
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=6ef255a1
> *-volume UNCLAIMED
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@1:3.0.0,1
> capacity: 1863GiB
> capabilities: primary
> *-disk:9
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 9
> bus info: scsi@1:4.0.0
> logical name: /dev/sdj
> version: ML6O
> serial: ML2220F30Z38XE
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=099ce3df
> *-volume UNCLAIMED
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@1:4.0.0,1
> capacity: 1863GiB
> capabilities: primary
>
> *-pci:2
> description: PCI bridge
> product: 6 Series/C200 Series Chipset Family PCI Express
> Root Port 1
> vendor: Intel Corporation
> physical id: 1c
> bus info: pci@0000:00:1c.0
> version: b5
> width: 32 bits
> clock: 33MHz
> capabilities: pci pciexpress msi pm normal_decode
> bus_master cap_list
> configuration: driver=pcieport
> resources: irq:42 ioport:d000(size=4096) memory:fba00000-fbafffff
> *-storage
> description: RAID bus controller
> product: SiI 3132 Serial ATA Raid II Controller
> vendor: Silicon Image, Inc.
> physical id: 0
> bus info: pci@0000:03:00.0
> logical name: scsi2
> logical name: scsi3
> version: 01
> width: 64 bits
> clock: 33MHz
> capabilities: storage pm msi pciexpress bus_master
> cap_list rom emulated
> configuration: driver=sata_sil24 latency=0
> resources: irq:16 memory:fba84000-fba8407f
> memory:fba80000-fba83fff ioport:d000(size=128)
> memory:fba00000-fba7ffff
> *-disk:0
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 0
> bus info: scsi@2:0.0.0
> logical name: /dev/sdk
> version: ML6O
> serial: ML2220F30U13AE
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=c381acb8
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@2:0.0.0,1
> logical name: /dev/sdk1
> capacity: 1863GiB
> capabilities: primary
> *-disk:1
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 1
> bus info: scsi@2:1.0.0
> logical name: /dev/sdl
> version: ML6O
> serial: ML2220F30YL2NE
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=31c44e74
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@2:1.0.0,1
> logical name: /dev/sdl1
> capacity: 1863GiB
> capabilities: primary
> *-disk:2
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 2
> bus info: scsi@2:2.0.0
> logical name: /dev/sdm
> version: ML6O
> serial: ML2220F32S2JNE
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=8f8c9eeb
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@2:2.0.0,1
> logical name: /dev/sdm1
> capacity: 1863GiB
> capabilities: primary
> *-disk:3
> description: ATA Disk
> product: WDC WD20EARX-00P
> vendor: Western Digital
> physical id: 3
> bus info: scsi@2:3.0.0
> logical name: /dev/sdn
> version: 51.0
> serial: WD-WMAZA9409912
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=f2a3d65b
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@2:3.0.0,1
> logical name: /dev/sdn1
> capacity: 1863GiB
> capabilities: primary
> *-disk:4
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 4
> bus info: scsi@2:4.0.0
> logical name: /dev/sdo
> version: ML6O
> serial: ML2220F30VS6SE
> size: 1863GiB (2TB)
> configuration: ansiversion=5
> *-disk:5
> description: EXT4 volume
> product: Hitachi HDS5C302
> vendor: Linux
> physical id: 5
> bus info: scsi@3:0.0.0
> logical name: /dev/sdp
> version: 1.0
> serial: 3d95991d-d58b-4c49-b22d-620b4a74aa91
> size: 1863GiB
> capabilities: journaled extended_attributes
> large_files huge_files dir_nlink extents ext4 ext2 initialized
> configuration: ansiversion=5 created=2012-09-05
> 16:45:31 filesystem=ext4 lastmountpoint=/media/hdd modified=2012-09-05
> 17:57:47 mounted=2012-09-05 17:55:30 state=clean
> *-disk:6
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 6
> bus info: scsi@3:1.0.0
> logical name: /dev/sdq
> version: ML6O
> serial: ML2220F311S72E
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=590f599d
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@3:1.0.0,1
> logical name: /dev/sdq1
> capacity: 1863GiB
> capabilities: primary
> *-disk:7
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 7
> bus info: scsi@3:2.0.0
> logical name: /dev/sdr
> version: ML6O
> serial: ML2220F30YD74E
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=dcc1db62
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@3:2.0.0,1
> logical name: /dev/sdr1
> capacity: 1863GiB
> capabilities: primary
> *-disk:8
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 8
> bus info: scsi@3:3.0.0
> logical name: /dev/sds
> version: ML6O
> serial: ML2220F30YBPUE
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=e9c70fcd
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@3:3.0.0,1
> logical name: /dev/sds1
> capacity: 1863GiB
> capabilities: primary
> *-disk:9
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 9
> bus info: scsi@3:4.0.0
> logical name: /dev/sdt
> version: ML6O
> serial: ML2220F30R3XYE
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=8458157f
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@3:4.0.0,1
> logical name: /dev/sdt1
> capacity: 1863GiB
> capabilities: primary
> *-pci:3
> description: PCI bridge
> product: 6 Series/C200 Series Chipset Family PCI Express
> Root Port 2
> vendor: Intel Corporation
> physical id: 1c.1
> bus info: pci@0000:00:1c.1
> version: b5
> width: 32 bits
> clock: 33MHz
> capabilities: pci pciexpress msi pm normal_decode
> bus_master cap_list
> configuration: driver=pcieport
> resources: irq:43 memory:fb900000-fb9fffff
> *-usb
> description: USB controller
> product: ASM1042 SuperSpeed USB Host Controller
> vendor: ASMedia Technology Inc.
> physical id: 0
> bus info: pci@0000:04:00.0
> version: 00
> width: 64 bits
> clock: 33MHz
> capabilities: msi msix pm pciexpress xhci bus_master cap_list
> configuration: driver=xhci_hcd latency=0
> resources: irq:17 memory:fb900000-fb907fff
> *-pci:4
> description: PCI bridge
> product: 6 Series/C200 Series Chipset Family PCI Express
> Root Port 3
> vendor: Intel Corporation
> physical id: 1c.2
> bus info: pci@0000:00:1c.2
> version: b5
> width: 32 bits
> clock: 33MHz
> capabilities: pci pciexpress msi pm normal_decode
> bus_master cap_list
> configuration: driver=pcieport
> resources: irq:44 ioport:c000(size=4096) memory:fb800000-fb8fffff
> *-storage
> description: RAID bus controller
> product: SiI 3132 Serial ATA Raid II Controller
> vendor: Silicon Image, Inc.
> physical id: 0
> bus info: pci@0000:05:00.0
> logical name: scsi4
> logical name: scsi5
> version: 01
> width: 64 bits
> clock: 33MHz
> capabilities: storage pm msi pciexpress bus_master
> cap_list rom emulated
> configuration: driver=sata_sil24 latency=0
> resources: irq:18 memory:fb884000-fb88407f
> memory:fb880000-fb883fff ioport:c000(size=128)
> memory:fb800000-fb87ffff
> *-disk:0
> description: ATA Disk
> product: SAMSUNG HD204UI
> physical id: 0
> bus info: scsi@4:0.0.0
> logical name: /dev/sdu
> version: 1AQ1
> serial: S2N6J50B800957
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=0fca2557
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@4:0.0.0,1
> logical name: /dev/sdu1
> capacity: 1863GiB
> capabilities: primary
> *-disk:1
> description: ATA Disk
> product: SAMSUNG HD204UI
> physical id: 1
> bus info: scsi@4:1.0.0
> logical name: /dev/sdv
> version: 1AQ1
> serial: S2N6J50B800964
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=9d8ed5a5
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@4:1.0.0,1
> logical name: /dev/sdv1
> capacity: 1863GiB
> capabilities: primary
> *-disk:2
> description: ATA Disk
> product: SAMSUNG HD204UI
> physical id: 2
> bus info: scsi@4:2.0.0
> logical name: /dev/sdw
> version: 1AQ1
> serial: S2N6J50B800955
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=ab4b523a
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@4:2.0.0,1
> logical name: /dev/sdw1
> capacity: 1863GiB
> capabilities: primary
> *-disk:3
> description: ATA Disk
> product: SAMSUNG HD204UI
> physical id: 3
> bus info: scsi@4:3.0.0
> logical name: /dev/sdx
> version: 1AQ1
> serial: S2N6J50B800954
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=e69fb7cb
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@4:3.0.0,1
> logical name: /dev/sdx1
> capacity: 1863GiB
> capabilities: primary
> *-disk:4
> description: ATA Disk
> product: SAMSUNG HD204UI
> physical id: 4
> bus info: scsi@4:4.0.0
> logical name: /dev/sdy
> version: 1AQ1
> serial: S2N6J50B800956
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=195e4659
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@4:4.0.0,1
> logical name: /dev/sdy1
> capacity: 1863GiB
> capabilities: primary
> *-disk:5
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 5
> bus info: scsi@5:0.0.0
> logical name: /dev/sdz
> version: ML6O
> serial: ML2220F30ZRZ5E
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=222ff77a
> *-volume UNCLAIMED
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@5:0.0.0,1
> capacity: 1863GiB
> capabilities: primary
> *-disk:6
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 6
> bus info: scsi@5:1.0.0
> logical name: /dev/sdaa
> version: ML6O
> serial: ML2220F30TDYWE
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=a4f16c55
> *-volume UNCLAIMED
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@5:1.0.0,1
> capacity: 1863GiB
> capabilities: primary
> *-disk:7
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 7
> bus info: scsi@5:2.0.0
> logical name: /dev/sdab
> version: ML6O
> serial: ML2220F31162ZE
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=c1af612f
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@5:2.0.0,1
> logical name: /dev/sdab1
> capacity: 1863GiB
> capabilities: primary
> *-disk:8
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 8
> bus info: scsi@5:3.0.0
> logical name: /dev/sdac
> version: ML6O
> serial: ML2220F30XAN6E
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=a2c77b59
> *-volume UNCLAIMED
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@5:3.0.0,1
> capacity: 1863GiB
> capabilities: primary
> *-disk:9
> description: ATA Disk
> product: Hitachi HDS5C302
> vendor: Hitachi
> physical id: 9
> bus info: scsi@5:4.0.0
> logical name: /dev/sdad
> version: ML6O
> serial: ML2220F311S91E
> size: 1863GiB (2TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=d6aacde0
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@5:4.0.0,1
> logical name: /dev/sdad1
> capacity: 1863GiB
> capabilities: primary
> *-pci:5
> description: PCI bridge
> product: 6 Series/C200 Series Chipset Family PCI Express
> Root Port 4
> vendor: Intel Corporation
> physical id: 1c.3
> bus info: pci@0000:00:1c.3
> version: b5
> width: 32 bits
> clock: 33MHz
> capabilities: pci pciexpress msi pm normal_decode
> bus_master cap_list
> configuration: driver=pcieport
> resources: irq:45 ioport:b000(size=4096)
> memory:fb700000-fb7fffff ioport:cfa00000(size=1048576)
> *-storage
> description: SATA controller
> product: JMB362 SATA Controller
> vendor: JMicron Technology Corp.
> physical id: 0
> bus info: pci@0000:06:00.0
> version: 10
> width: 32 bits
> clock: 33MHz
> capabilities: storage pm pciexpress ahci_1.0
> bus_master cap_list rom
> configuration: driver=ahci latency=0
> resources: irq:19 ioport:b040(size=8)
> ioport:b030(size=4) ioport:b020(size=8) ioport:b010(size=4)
> ioport:b000(size=16) memory:fb710000-fb7101ff memory:cfa00000-cfa0ffff
> *-pci:6
> description: PCI bridge
> product: 6 Series/C200 Series Chipset Family PCI Express
> Root Port 5
> vendor: Intel Corporation
> physical id: 1c.4
> bus info: pci@0000:00:1c.4
> version: b5
> width: 32 bits
> clock: 33MHz
> capabilities: pci pciexpress msi pm normal_decode
> bus_master cap_list
> configuration: driver=pcieport
> resources: irq:46 memory:fb600000-fb6fffff
> *-usb
> description: USB controller
> product: ASM1042 SuperSpeed USB Host Controller
> vendor: ASMedia Technology Inc.
> physical id: 0
> bus info: pci@0000:07:00.0
> version: 00
> width: 64 bits
> clock: 33MHz
> capabilities: msi msix pm pciexpress xhci bus_master cap_list
> configuration: driver=xhci_hcd latency=0
> resources: irq:16 memory:fb600000-fb607fff
> *-pci:7
> description: PCI bridge
> product: 82801 PCI Bridge
> vendor: Intel Corporation
> physical id: 1c.6
> bus info: pci@0000:00:1c.6
> version: b5
> width: 32 bits
> clock: 33MHz
> capabilities: pci pciexpress msi pm subtractive_decode
> bus_master cap_list
> resources: ioport:a000(size=4096) memory:fb500000-fb5fffff
> *-pci
> description: PCI bridge
> product: ASM1083/1085 PCIe to PCI Bridge
> vendor: ASMedia Technology Inc.
> physical id: 0
> bus info: pci@0000:08:00.0
> version: 01
> width: 32 bits
> clock: 33MHz
> capabilities: pci subtractive_decode bus_master cap_list
> resources: ioport:a000(size=4096) memory:fb500000-fb5fffff
> *-firewire
> description: FireWire (IEEE 1394)
> product: VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller
> vendor: VIA Technologies, Inc.
> physical id: 2
> bus info: pci@0000:09:02.0
> version: c0
> width: 32 bits
> clock: 33MHz
> capabilities: pm ohci bus_master cap_list
> configuration: driver=firewire_ohci latency=32 maxlatency=32
> resources: irq:17 memory:fb500000-fb5007ff
> ioport:a000(size=128)
> *-pci:8
> description: PCI bridge
> product: 6 Series/C200 Series Chipset Family PCI Express
> Root Port 8
> vendor: Intel Corporation
> physical id: 1c.7
> bus info: pci@0000:00:1c.7
> version: b5
> width: 32 bits
> clock: 33MHz
> capabilities: pci pciexpress msi pm normal_decode
> bus_master cap_list
> configuration: driver=pcieport
> resources: irq:47 ioport:9000(size=4096) memory:fb400000-fb4fffff
> *-storage
> description: SATA controller
> product: 88SE9172 SATA 6Gb/s Controller
> vendor: Marvell Technology Group Ltd.
> physical id: 0
> bus info: pci@0000:0a:00.0
> logical name: scsi14
> logical name: scsi15
> version: 11
> width: 32 bits
> clock: 33MHz
> capabilities: storage pm msi pciexpress ahci_1.0
> bus_master cap_list rom emulated
> configuration: driver=ahci latency=0
> resources: irq:60 ioport:9040(size=8)
> ioport:9030(size=4) ioport:9020(size=8) ioport:9010(size=4)
> ioport:9000(size=16) memory:fb410000-fb4101ff memory:fb400000-fb40ffff
> *-disk:0
> description: ATA Disk
> product: Corsair Force 3
> physical id: 0
> bus info: scsi@14:0.0.0
> logical name: /dev/sdaf
> version: 1.3.
> serial: 11436520000012112929
> size: 111GiB (120GB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=447df0c7
> *-volume
> description: Linux filesystem partition
> physical id: 1
> bus info: scsi@14:0.0.0,1
> logical name: /dev/sdaf1
> capacity: 111GiB
> capabilities: primary
> *-disk:1
> description: ATA Disk
> product: KINGSTON SE100S3
> physical id: 1
> bus info: scsi@15:0.0.0
> logical name: /dev/sdag
> version: 515A
> serial: 50026B723A087F9E
> size: 93GiB (100GB)
> configuration: ansiversion=5
> *-usb:1
> description: USB controller
> product: 6 Series/C200 Series Chipset Family USB Enhanced
> Host Controller #1
> vendor: Intel Corporation
> physical id: 1d
> bus info: pci@0000:00:1d.0
> version: 05
> width: 32 bits
> clock: 33MHz
> capabilities: pm debug ehci bus_master cap_list
> configuration: driver=ehci_hcd latency=0
> resources: irq:23 memory:fbc26000-fbc263ff
> *-isa
> description: ISA bridge
> product: Z68 Express Chipset Family LPC Controller
> vendor: Intel Corporation
> physical id: 1f
> bus info: pci@0000:00:1f.0
> version: 05
> width: 32 bits
> clock: 33MHz
> capabilities: isa bus_master cap_list
> configuration: latency=0
> *-storage
> description: SATA controller
> product: 6 Series/C200 Series Chipset Family SATA AHCI Controller
> vendor: Intel Corporation
> physical id: 1f.2
> bus info: pci@0000:00:1f.2
> logical name: scsi10
> version: 05
> width: 32 bits
> clock: 66MHz
> capabilities: storage msi pm ahci_1.0 bus_master cap_list emulated
> configuration: driver=ahci latency=0
> resources: irq:59 ioport:f0d0(size=8) ioport:f0c0(size=4)
> ioport:f0b0(size=8) ioport:f0a0(size=4) ioport:f060(size=32)
> memory:fbc25000-fbc257ff
> *-disk
> description: ATA Disk
> product: ST2000DL003-9VT1
> vendor: Seagate
> physical id: 0.0.0
> bus info: scsi@10:0.0.0
> logical name: /dev/sdae
> version: CC32
> serial: 5YD3L8H1
> size: 1863GiB (2TB)
> capabilities: gpt-1.00 partitioned partitioned:gpt
> configuration: ansiversion=5
> guid=ee69a333-af6d-4738-be13-8f376787e0f5
> *-volume:0
> description: EFI partition
> physical id: 1
> bus info: scsi@10:0.0.0,1
> logical name: /dev/sdae1
> serial: 1ba7cdd4-ca07-4cb4-932c-52ef2464d25f
> capacity: 976KiB
> *-volume:1
> description: EXT4 volume
> vendor: Linux
> physical id: 2
> bus info: scsi@10:0.0.0,2
> logical name: /dev/sdae2
> logical name: /
> version: 1.0
> serial: 582b06ec-89d4-4f54-a537-1f72440b09f1
> size: 1855GiB
> capabilities: journaled extended_attributes
> large_files huge_files dir_nlink recover extents ext4 ext2 initialized
> configuration: created=2012-04-04 15:28:10
> filesystem=ext4 lastmountpoint=/ modified=2015-03-03 16:46:29
> mount.fstype=ext4
> mount.options=rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered
> mounted=2015-04-06 17:35:05 state=mounted
> *-volume:2
> description: Linux swap volume
> physical id: 3
> bus info: scsi@10:0.0.0,3
> logical name: /dev/sdae3
> version: 1
> serial: 10a1f4e7-ba5f-4319-9f6b-80338ef27594
> size: 8097MiB
> capacity: 8097MiB
> capabilities: nofs swap initialized
> configuration: filesystem=swap pagesize=4096
> *-serial UNCLAIMED
> description: SMBus
> product: 6 Series/C200 Series Chipset Family SMBus Controller
> vendor: Intel Corporation
> physical id: 1f.3
> bus info: pci@0000:00:1f.3
> version: 05
> width: 64 bits
> clock: 33MHz
> configuration: latency=0
> resources: memory:fbc24000-fbc240ff ioport:f040(size=32)
>
>
>
>
>
> --
> Emanuel Domingos
--
Emanuel Domingos
Cursando Bacharelado em Ciência da Computação - IFCE Campus Maracanaú
Técnico em Conectividade - IFCE Campus Maracanaú
--
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
^ permalink raw reply
* Re: Recovery Raid6 Degraded
From: Emanuel Domingos @ 2015-04-14 13:02 UTC (permalink / raw)
To: Mikael Abrahamsson; +Cc: linux-raid
In-Reply-To: <alpine.DEB.2.02.1504132234220.16871@uplift.swm.pp.se>
Hi, Mikael, hi guys!
Follow the errors found after building the new version of mdadm:
#mdadm --stop /dev/md/ubuntu\:md-raid6_primary
#mdadm --assemble --force /dev/md/ubuntu\:md-raid6_primary /dev/sdaa
/dev/sdac /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdz
mdadm: device /dev/md/ubuntu:md-raid6_primary exists but is not an md array.
DMESG
[661924.167503] md: md123 stopped.
[661924.167513] md: unbind<sdi>
[661924.184248] md: export_rdev(sdi)
[661924.184259] md: unbind<sdj>
[661924.184324] md: export_rdev(sdj)
[661924.184335] md: unbind<sdg>
[661924.188227] md: export_rdev(sdg)
[661924.188248] md: unbind<sdh>
[661924.192285] md: export_rdev(sdh)
[661924.192296] md: unbind<sdf>
[661924.192364] md: export_rdev(sdf)
[661924.192375] md: unbind<sdz>
[661924.264120] md: export_rdev(sdz)
[661924.264133] md: unbind<sdaa>
[661924.264456] md: export_rdev(sdaa)
[661924.264467] md: unbind<sdac>
[661924.272138] md: export_rdev(sdac)
2015-04-13 17:38 GMT-03:00 Mikael Abrahamsson <swmike@swm.pp.se>:
> On Mon, 13 Apr 2015, Emanuel Domingos wrote:
>
>> guys, following guidelines on wiki, before to try recreate my array
>> I'm sending this mail to listen the experts.
>
>
> Good choice!
>
>> I would like to aid as a problem in my raid arrays after a crash in
>> which I had to restart the server.
>
>
> What kernel version and mdadm version are you running?
>
> My first recommendation would be for you to compile latest mdadm from
> source:
>
> "git clone https://github.com/neilbrown/mdadm"
>
> Then compile it and use that to do the --assemble-force operation that
> failed before. This has helped others.
>
> If it still doesn't work, please provide dmesg output from when that
> operation occured.
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
--
Emanuel Domingos
Cursando Bacharelado em Ciência da Computação - IFCE Campus Maracanaú
Técnico em Conectividade - IFCE Campus Maracanaú
--
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
^ permalink raw reply
* Re: Recovery Raid6 Degraded
From: Mikael Abrahamsson @ 2015-04-14 14:19 UTC (permalink / raw)
To: Emanuel Domingos; +Cc: linux-raid
In-Reply-To: <CACsoFmiCXw1dgpqtz33rA5ejMhYsndi68L63OdpRoU_XyCfFFg@mail.gmail.com>
On Tue, 14 Apr 2015, Emanuel Domingos wrote:
> Hi, Mikael, hi guys!
>
>
> Follow the errors found after building the new version of mdadm:
>
> #mdadm --stop /dev/md/ubuntu\:md-raid6_primary
>
> #mdadm --assemble --force /dev/md/ubuntu\:md-raid6_primary /dev/sdaa /dev/sdac
> /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdz
>
> mdadm: device /dev/md/ubuntu:md-raid6_primary exists but is not an md array.
Please call it /dev/md124 and not the above ubuntu: name. I have no idea
what it is you're trying to do with that name. Also use --verbose when
trying to do the assembly and see if you get any further information.
--
Mikael Abrahamsson email: swmike@swm.pp.se
^ permalink raw reply
* [PATCH 1/6] md-cluster: correct the num for comparison
From: Goldwyn Rodrigues @ 2015-04-14 15:42 UTC (permalink / raw)
To: neilb; +Cc: GQJiang, linux-raid
Author: Guoqing Jiang <gqjiang@suse.com>
Since the node num of md-cluster is from zero, and
cinfo->slot_number represents the slot num of dlm,
no need to check for equality.
Signed-off-by: Guoqing Jiang <gqjiang@suse.com>
Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
---
drivers/md/md-cluster.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/md/md-cluster.c b/drivers/md/md-cluster.c
index 96679b2..6bdc45e 100644
--- a/drivers/md/md-cluster.c
+++ b/drivers/md/md-cluster.c
@@ -612,7 +612,7 @@ static int join(struct mddev *mddev, int nodes)
if (ret)
goto err;
wait_for_completion(&cinfo->completion);
- if (nodes <= cinfo->slot_number) {
+ if (nodes < cinfo->slot_number) {
pr_err("md-cluster: Slot allotted(%d) greater than available slots(%d)", cinfo->slot_number - 1,
nodes);
ret = -ERANGE;
--
2.1.4
^ permalink raw reply related
* [PATCH 2/6] md: Export and rename kick_rdev_from_array
From: Goldwyn Rodrigues @ 2015-04-14 15:43 UTC (permalink / raw)
To: neilb; +Cc: GQJiang, linux-raid
This export is required for clustering module in order to
co-ordinate remove/readd a rdev from all nodes.
Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
---
drivers/md/md.c | 17 +++++++++--------
drivers/md/md.h | 1 +
2 files changed, 10 insertions(+), 8 deletions(-)
diff --git a/drivers/md/md.c b/drivers/md/md.c
index d566ade..2949c4a 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -2172,11 +2172,12 @@ static void export_rdev(struct md_rdev *rdev)
kobject_put(&rdev->kobj);
}
-static void kick_rdev_from_array(struct md_rdev *rdev)
+void md_kick_rdev_from_array(struct md_rdev *rdev)
{
unbind_rdev_from_array(rdev);
export_rdev(rdev);
}
+EXPORT_SYMBOL_GPL(md_kick_rdev_from_array);
static void export_array(struct mddev *mddev)
{
@@ -2185,7 +2186,7 @@ static void export_array(struct mddev *mddev)
while (!list_empty(&mddev->disks)) {
rdev = list_first_entry(&mddev->disks, struct md_rdev,
same_set);
- kick_rdev_from_array(rdev);
+ md_kick_rdev_from_array(rdev);
}
mddev->raid_disks = 0;
mddev->major_version = 0;
@@ -2480,7 +2481,7 @@ state_store(struct md_rdev *rdev, const char *buf, size_t len)
struct mddev *mddev = rdev->mddev;
if (mddev_is_clustered(mddev))
md_cluster_ops->metadata_update_start(mddev);
- kick_rdev_from_array(rdev);
+ md_kick_rdev_from_array(rdev);
if (mddev->pers)
md_update_sb(mddev, 1);
md_new_event(mddev);
@@ -3138,7 +3139,7 @@ static void analyze_sbs(struct mddev *mddev)
"md: fatal superblock inconsistency in %s"
" -- removing from array\n",
bdevname(rdev->bdev,b));
- kick_rdev_from_array(rdev);
+ md_kick_rdev_from_array(rdev);
}
super_types[mddev->major_version].
@@ -3153,7 +3154,7 @@ static void analyze_sbs(struct mddev *mddev)
"md: %s: %s: only %d devices permitted\n",
mdname(mddev), bdevname(rdev->bdev, b),
mddev->max_disks);
- kick_rdev_from_array(rdev);
+ md_kick_rdev_from_array(rdev);
continue;
}
if (rdev != freshest) {
@@ -3162,7 +3163,7 @@ static void analyze_sbs(struct mddev *mddev)
printk(KERN_WARNING "md: kicking non-fresh %s"
" from array!\n",
bdevname(rdev->bdev,b));
- kick_rdev_from_array(rdev);
+ md_kick_rdev_from_array(rdev);
continue;
}
/* No device should have a Candidate flag
@@ -3171,7 +3172,7 @@ static void analyze_sbs(struct mddev *mddev)
if (test_bit(Candidate, &rdev->flags)) {
pr_info("md: kicking Cluster Candidate %s from array!\n",
bdevname(rdev->bdev, b));
- kick_rdev_from_array(rdev);
+ md_kick_rdev_from_array(rdev);
}
}
if (mddev->level == LEVEL_MULTIPATH) {
@@ -5973,7 +5974,7 @@ static int hot_remove_disk(struct mddev *mddev, dev_t dev)
if (rdev->raid_disk >= 0)
goto busy;
- kick_rdev_from_array(rdev);
+ md_kick_rdev_from_array(rdev);
md_update_sb(mddev, 1);
md_new_event(mddev);
diff --git a/drivers/md/md.h b/drivers/md/md.h
index 6dc0ce0..d98c0d7 100644
--- a/drivers/md/md.h
+++ b/drivers/md/md.h
@@ -671,6 +671,7 @@ extern struct bio *bio_alloc_mddev(gfp_t gfp_mask, int nr_iovecs,
extern void md_unplug(struct blk_plug_cb *cb, bool from_schedule);
extern void md_reload_sb(struct mddev *mddev);
extern void md_update_sb(struct mddev *mddev, int force);
+extern void md_kick_rdev_from_array(struct md_rdev * rdev);
static inline int mddev_check_plugged(struct mddev *mddev)
{
return !!blk_check_plugged(md_unplug, mddev,
--
2.1.4
^ permalink raw reply related
* [PATCH 3/6] md: Export and rename find_rdev_nr_rcu
From: Goldwyn Rodrigues @ 2015-04-14 15:43 UTC (permalink / raw)
To: neilb; +Cc: GQJiang, linux-raid
This is required by the clustering module (patches to follow) to
find the device to remove or re-add.
Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
---
drivers/md/md.c | 9 +++++----
drivers/md/md.h | 1 +
2 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/md/md.c b/drivers/md/md.c
index 2949c4a..9d253c2 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -646,7 +646,7 @@ void mddev_unlock(struct mddev *mddev)
}
EXPORT_SYMBOL_GPL(mddev_unlock);
-static struct md_rdev *find_rdev_nr_rcu(struct mddev *mddev, int nr)
+struct md_rdev *md_find_rdev_nr_rcu(struct mddev *mddev, int nr)
{
struct md_rdev *rdev;
@@ -656,6 +656,7 @@ static struct md_rdev *find_rdev_nr_rcu(struct mddev *mddev, int nr)
return NULL;
}
+EXPORT_SYMBOL_GPL(md_find_rdev_nr_rcu);
static struct md_rdev *find_rdev(struct mddev *mddev, dev_t dev)
{
@@ -2053,11 +2054,11 @@ static int bind_rdev_to_array(struct md_rdev *rdev, struct mddev *mddev)
int choice = 0;
if (mddev->pers)
choice = mddev->raid_disks;
- while (find_rdev_nr_rcu(mddev, choice))
+ while (md_find_rdev_nr_rcu(mddev, choice))
choice++;
rdev->desc_nr = choice;
} else {
- if (find_rdev_nr_rcu(mddev, rdev->desc_nr)) {
+ if (md_find_rdev_nr_rcu(mddev, rdev->desc_nr)) {
rcu_read_unlock();
return -EBUSY;
}
@@ -5728,7 +5729,7 @@ static int get_disk_info(struct mddev *mddev, void __user * arg)
return -EFAULT;
rcu_read_lock();
- rdev = find_rdev_nr_rcu(mddev, info.number);
+ rdev = md_find_rdev_nr_rcu(mddev, info.number);
if (rdev) {
info.major = MAJOR(rdev->bdev->bd_dev);
info.minor = MINOR(rdev->bdev->bd_dev);
diff --git a/drivers/md/md.h b/drivers/md/md.h
index d98c0d7..ecdce36 100644
--- a/drivers/md/md.h
+++ b/drivers/md/md.h
@@ -672,6 +672,7 @@ extern void md_unplug(struct blk_plug_cb *cb, bool from_schedule);
extern void md_reload_sb(struct mddev *mddev);
extern void md_update_sb(struct mddev *mddev, int force);
extern void md_kick_rdev_from_array(struct md_rdev * rdev);
+struct md_rdev *md_find_rdev_nr_rcu(struct mddev *mddev, int nr);
static inline int mddev_check_plugged(struct mddev *mddev)
{
return !!blk_check_plugged(md_unplug, mddev,
--
2.1.4
^ permalink raw reply related
* [PATCH 4/6] md-cluster: remove capabilities
From: Goldwyn Rodrigues @ 2015-04-14 15:44 UTC (permalink / raw)
To: neilb; +Cc: GQJiang, linux-raid
This adds "remove" capabilities for the clustered environment.
When a user initiates removal of a device from the array, a
REMOVE message with disk number in the array is sent to all
the nodes which kick the respective device in their own array.
This facilitates the removal of failed devices.
Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
---
drivers/md/md-cluster.c | 30 ++++++++++++++++++++++++++++++
drivers/md/md-cluster.h | 1 +
drivers/md/md.c | 7 ++++++-
3 files changed, 37 insertions(+), 1 deletion(-)
diff --git a/drivers/md/md-cluster.c b/drivers/md/md-cluster.c
index 6bdc45e..82f1b7b 100644
--- a/drivers/md/md-cluster.c
+++ b/drivers/md/md-cluster.c
@@ -72,6 +72,7 @@ enum msg_type {
METADATA_UPDATED = 0,
RESYNCING,
NEWDISK,
+ REMOVE,
};
struct cluster_msg {
@@ -401,6 +402,16 @@ static void process_metadata_update(struct mddev *mddev, struct cluster_msg *msg
dlm_lock_sync(cinfo->no_new_dev_lockres, DLM_LOCK_CR);
}
+static void process_remove_disk(struct mddev *mddev, struct cluster_msg *msg)
+{
+ struct md_rdev *rdev = md_find_rdev_nr_rcu(mddev, msg->raid_slot);
+
+ if (rdev)
+ md_kick_rdev_from_array(rdev);
+ else
+ pr_warn("%s: %d Could not find disk(%d) to REMOVE\n", __func__, __LINE__, msg->raid_slot);
+}
+
static void process_recvd_msg(struct mddev *mddev, struct cluster_msg *msg)
{
switch (msg->type) {
@@ -419,6 +430,15 @@ static void process_recvd_msg(struct mddev *mddev, struct cluster_msg *msg)
pr_info("%s: %d Received message: NEWDISK from %d\n",
__func__, __LINE__, msg->slot);
process_add_new_disk(mddev, msg);
+ break;
+ case REMOVE:
+ pr_info("%s: %d Received REMOVE from %d\n",
+ __func__, __LINE__, msg->slot);
+ process_remove_disk(mddev, msg);
+ break;
+ default:
+ pr_warn("%s:%d Received unknown message from %d\n",
+ __func__, __LINE__, msg->slot);
};
}
@@ -854,6 +874,15 @@ static int new_disk_ack(struct mddev *mddev, bool ack)
return 0;
}
+static int remove_disk(struct mddev *mddev, struct md_rdev *rdev)
+{
+ struct cluster_msg cmsg;
+ struct md_cluster_info *cinfo = mddev->cluster_info;
+ cmsg.type = REMOVE;
+ cmsg.raid_slot = rdev->desc_nr;
+ return __sendmsg(cinfo, &cmsg);
+}
+
static struct md_cluster_operations cluster_ops = {
.join = join,
.leave = leave,
@@ -868,6 +897,7 @@ static struct md_cluster_operations cluster_ops = {
.add_new_disk_start = add_new_disk_start,
.add_new_disk_finish = add_new_disk_finish,
.new_disk_ack = new_disk_ack,
+ .remove_disk = remove_disk,
};
static int __init cluster_init(void)
diff --git a/drivers/md/md-cluster.h b/drivers/md/md-cluster.h
index 7417133..71e5143 100644
--- a/drivers/md/md-cluster.h
+++ b/drivers/md/md-cluster.h
@@ -22,6 +22,7 @@ struct md_cluster_operations {
int (*add_new_disk_start)(struct mddev *mddev, struct md_rdev *rdev);
int (*add_new_disk_finish)(struct mddev *mddev);
int (*new_disk_ack)(struct mddev *mddev, bool ack);
+ int (*remove_disk)(struct mddev *mddev, struct md_rdev *rdev);
};
#endif /* _MD_CLUSTER_H */
diff --git a/drivers/md/md.c b/drivers/md/md.c
index 9d253c2..9127d11 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -2481,8 +2481,10 @@ state_store(struct md_rdev *rdev, const char *buf, size_t len)
else {
struct mddev *mddev = rdev->mddev;
if (mddev_is_clustered(mddev))
- md_cluster_ops->metadata_update_start(mddev);
+ md_cluster_ops->remove_disk(mddev, rdev);
md_kick_rdev_from_array(rdev);
+ if (mddev_is_clustered(mddev))
+ md_cluster_ops->metadata_update_start(mddev);
if (mddev->pers)
md_update_sb(mddev, 1);
md_new_event(mddev);
@@ -5975,6 +5977,9 @@ static int hot_remove_disk(struct mddev *mddev, dev_t dev)
if (rdev->raid_disk >= 0)
goto busy;
+ if (mddev_is_clustered(mddev))
+ md_cluster_ops->remove_disk(mddev, rdev);
+
md_kick_rdev_from_array(rdev);
md_update_sb(mddev, 1);
md_new_event(mddev);
--
2.1.4
^ permalink raw reply related
* [PATCH 5/6] md: re-add a failed disk
From: Goldwyn Rodrigues @ 2015-04-14 15:45 UTC (permalink / raw)
To: neilb; +Cc: GQJiang, linux-raid
This adds the capability of re-adding a failed disk by
writing "re-add" to /sys/block/mdXX/md/dev-YYY/state.
This facilitates adding disks which have encountered a temporary
error such as a network disconnection/hiccup in an iSCSI device,
or a SAN cable disconnection which has been restored. In such
a situation, you do not need to remove and re-add the device.
Writing re-add to the failed device's state would add it again
to the array and perform the recovery of only the blocks which
were written after the device failed.
This works for generic md, and is not related to clustering. However,
this patch is to ease re-add operations listed above in clustering
environments.
Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
---
drivers/md/md.c | 56 +++++++++++++++++++++++++++++++++++---------------------
1 file changed, 35 insertions(+), 21 deletions(-)
diff --git a/drivers/md/md.c b/drivers/md/md.c
index 9127d11..ba01605 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -2379,6 +2379,36 @@ repeat:
}
EXPORT_SYMBOL(md_update_sb);
+static int add_bound_rdev(struct md_rdev *rdev)
+{
+ struct mddev *mddev = rdev->mddev;
+ int err = 0;
+
+ if (!mddev->pers->hot_remove_disk) {
+ /* If there is hot_add_disk but no hot_remove_disk
+ * then added disks for geometry changes,
+ * and should be added immediately.
+ */
+ super_types[mddev->major_version].
+ validate_super(mddev, rdev);
+ err = mddev->pers->hot_add_disk(mddev, rdev);
+ if (err) {
+ unbind_rdev_from_array(rdev);
+ export_rdev(rdev);
+ return err;
+ }
+ }
+ sysfs_notify_dirent_safe(rdev->sysfs_state);
+
+ set_bit(MD_CHANGE_DEVS, &mddev->flags);
+ if (mddev->degraded)
+ set_bit(MD_RECOVERY_RECOVER, &mddev->recovery);
+ set_bit(MD_RECOVERY_NEEDED, &mddev->recovery);
+ md_new_event(mddev);
+ md_wakeup_thread(mddev->thread);
+ return 0;
+}
+
/* words written to sysfs files may, or may not, be \n terminated.
* We want to accept with case. For this we use cmd_match.
*/
@@ -2568,7 +2598,10 @@ state_store(struct md_rdev *rdev, const char *buf, size_t len)
clear_bit(Replacement, &rdev->flags);
err = 0;
}
- }
+ } else if (cmd_match(buf, "re-add") && (test_bit(Faulty, &rdev->flags) || (rdev->raid_disk == -1))) {
+ clear_bit(Faulty, &rdev->flags);
+ err = add_bound_rdev(rdev);
+ }
if (!err)
sysfs_notify_dirent_safe(rdev->sysfs_state);
return err ? err : len;
@@ -5882,29 +5915,10 @@ static int add_new_disk(struct mddev *mddev, mdu_disk_info_t *info)
rdev->raid_disk = -1;
err = bind_rdev_to_array(rdev, mddev);
- if (!err && !mddev->pers->hot_remove_disk) {
- /* If there is hot_add_disk but no hot_remove_disk
- * then added disks for geometry changes,
- * and should be added immediately.
- */
- super_types[mddev->major_version].
- validate_super(mddev, rdev);
- err = mddev->pers->hot_add_disk(mddev, rdev);
- if (err)
- unbind_rdev_from_array(rdev);
- }
if (err)
export_rdev(rdev);
else
- sysfs_notify_dirent_safe(rdev->sysfs_state);
-
- set_bit(MD_CHANGE_DEVS, &mddev->flags);
- if (mddev->degraded)
- set_bit(MD_RECOVERY_RECOVER, &mddev->recovery);
- set_bit(MD_RECOVERY_NEEDED, &mddev->recovery);
- if (!err)
- md_new_event(mddev);
- md_wakeup_thread(mddev->thread);
+ err = add_bound_rdev(rdev);
if (mddev_is_clustered(mddev) &&
(info->state & (1 << MD_DISK_CLUSTER_ADD)))
md_cluster_ops->add_new_disk_finish(mddev);
--
2.1.4
^ permalink raw reply related
* [PATCH 6/6] md-cluster: re-add capabilities
From: Goldwyn Rodrigues @ 2015-04-14 15:45 UTC (permalink / raw)
To: neilb; +Cc: GQJiang, linux-raid
When "re-add" is writted to /sys/block/mdXX/md/dev-YYY/state,
the clustered md:
1. Sends RE_ADD message with the desc_nr. Nodes receiving the message
clear the Faulty bit in their respective rdev->flags.
2. The node initiating re-add, gathers the bitmaps of all nodes
and copies them into the local bitmap. It does not clear the bitmap
from which it is copying.
3. Initiating node schedules a md recovery to sync the devices.
Signed-off-by: Guoqing Jiang <gqjiang@suse.com>
Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
---
drivers/md/bitmap.c | 20 +++++++++++---------
drivers/md/bitmap.h | 2 +-
drivers/md/md-cluster.c | 48 +++++++++++++++++++++++++++++++++++++++++++++++-
drivers/md/md-cluster.h | 1 +
drivers/md/md.c | 12 ++++++++++++
5 files changed, 72 insertions(+), 11 deletions(-)
diff --git a/drivers/md/bitmap.c b/drivers/md/bitmap.c
index 5ff67c3..956cfb9 100644
--- a/drivers/md/bitmap.c
+++ b/drivers/md/bitmap.c
@@ -1852,7 +1852,7 @@ EXPORT_SYMBOL_GPL(bitmap_load);
* to our bitmap
*/
int bitmap_copy_from_slot(struct mddev *mddev, int slot,
- sector_t *low, sector_t *high)
+ sector_t *low, sector_t *high, bool clear_bits)
{
int rv = 0, i, j;
sector_t block, lo = 0, hi = 0;
@@ -1879,14 +1879,16 @@ int bitmap_copy_from_slot(struct mddev *mddev, int slot,
}
}
- bitmap_update_sb(bitmap);
- /* Setting this for the ev_page should be enough.
- * And we do not require both write_all and PAGE_DIRT either
- */
- for (i = 0; i < bitmap->storage.file_pages; i++)
- set_page_attr(bitmap, i, BITMAP_PAGE_DIRTY);
- bitmap_write_all(bitmap);
- bitmap_unplug(bitmap);
+ if (clear_bits) {
+ bitmap_update_sb(bitmap);
+ /* Setting this for the ev_page should be enough.
+ * And we do not require both write_all and PAGE_DIRT either
+ */
+ for (i = 0; i < bitmap->storage.file_pages; i++)
+ set_page_attr(bitmap, i, BITMAP_PAGE_DIRTY);
+ bitmap_write_all(bitmap);
+ bitmap_unplug(bitmap);
+ }
*low = lo;
*high = hi;
err:
diff --git a/drivers/md/bitmap.h b/drivers/md/bitmap.h
index 4aabc74..f1f4dd0 100644
--- a/drivers/md/bitmap.h
+++ b/drivers/md/bitmap.h
@@ -263,7 +263,7 @@ void bitmap_daemon_work(struct mddev *mddev);
int bitmap_resize(struct bitmap *bitmap, sector_t blocks,
int chunksize, int init);
int bitmap_copy_from_slot(struct mddev *mddev, int slot,
- sector_t *lo, sector_t *hi);
+ sector_t *lo, sector_t *hi, bool clear_bits);
#endif
#endif
diff --git a/drivers/md/md-cluster.c b/drivers/md/md-cluster.c
index 82f1b7b..ad2b5b7 100644
--- a/drivers/md/md-cluster.c
+++ b/drivers/md/md-cluster.c
@@ -73,6 +73,7 @@ enum msg_type {
RESYNCING,
NEWDISK,
REMOVE,
+ RE_ADD,
};
struct cluster_msg {
@@ -253,7 +254,7 @@ void recover_bitmaps(struct md_thread *thread)
str, ret);
goto clear_bit;
}
- ret = bitmap_copy_from_slot(mddev, slot, &lo, &hi);
+ ret = bitmap_copy_from_slot(mddev, slot, &lo, &hi, true);
if (ret) {
pr_err("md-cluster: Could not copy data from bitmap %d\n", slot);
goto dlm_unlock;
@@ -412,6 +413,16 @@ static void process_remove_disk(struct mddev *mddev, struct cluster_msg *msg)
pr_warn("%s: %d Could not find disk(%d) to REMOVE\n", __func__, __LINE__, msg->raid_slot);
}
+static void process_readd_disk(struct mddev *mddev, struct cluster_msg *msg)
+{
+ struct md_rdev *rdev = md_find_rdev_nr_rcu(mddev, msg->raid_slot);
+
+ if (rdev && test_bit(Faulty, &rdev->flags))
+ clear_bit(Faulty, &rdev->flags);
+ else
+ pr_warn("%s: %d Could not find disk(%d) which is faulty", __func__, __LINE__, msg->raid_slot);
+}
+
static void process_recvd_msg(struct mddev *mddev, struct cluster_msg *msg)
{
switch (msg->type) {
@@ -436,6 +447,11 @@ static void process_recvd_msg(struct mddev *mddev, struct cluster_msg *msg)
__func__, __LINE__, msg->slot);
process_remove_disk(mddev, msg);
break;
+ case RE_ADD:
+ pr_info("%s: %d Received RE_ADD from %d\n",
+ __func__, __LINE__, msg->slot);
+ process_readd_disk(mddev, msg);
+ break;
default:
pr_warn("%s:%d Received unknown message from %d\n",
__func__, __LINE__, msg->slot);
@@ -883,6 +899,35 @@ static int remove_disk(struct mddev *mddev, struct md_rdev *rdev)
return __sendmsg(cinfo, &cmsg);
}
+static int gather_bitmaps(struct md_rdev *rdev)
+{
+ int sn, err;
+ sector_t lo, hi;
+ struct cluster_msg cmsg;
+ struct mddev *mddev = rdev->mddev;
+ struct md_cluster_info *cinfo = mddev->cluster_info;
+
+ cmsg.type = RE_ADD;
+ cmsg.raid_slot = rdev->desc_nr;
+ err = sendmsg(cinfo, &cmsg);
+ if (err)
+ goto out;
+
+ for (sn = 0; sn < mddev->bitmap_info.nodes; sn++) {
+ if (sn == (cinfo->slot_number - 1))
+ continue;
+ err = bitmap_copy_from_slot(mddev, sn, &lo, &hi, false);
+ if (err) {
+ pr_warn("md-cluster: Could not gather bitmaps from slot %d", sn);
+ goto out;
+ }
+ if ((hi > 0) && (lo < mddev->recovery_cp))
+ mddev->recovery_cp = lo;
+ }
+out:
+ return err;
+}
+
static struct md_cluster_operations cluster_ops = {
.join = join,
.leave = leave,
@@ -898,6 +943,7 @@ static struct md_cluster_operations cluster_ops = {
.add_new_disk_finish = add_new_disk_finish,
.new_disk_ack = new_disk_ack,
.remove_disk = remove_disk,
+ .gather_bitmaps = gather_bitmaps,
};
static int __init cluster_init(void)
diff --git a/drivers/md/md-cluster.h b/drivers/md/md-cluster.h
index 71e5143..6817ee0 100644
--- a/drivers/md/md-cluster.h
+++ b/drivers/md/md-cluster.h
@@ -23,6 +23,7 @@ struct md_cluster_operations {
int (*add_new_disk_finish)(struct mddev *mddev);
int (*new_disk_ack)(struct mddev *mddev, bool ack);
int (*remove_disk)(struct mddev *mddev, struct md_rdev *rdev);
+ int (*gather_bitmaps)(struct md_rdev *rdev);
};
#endif /* _MD_CLUSTER_H */
diff --git a/drivers/md/md.c b/drivers/md/md.c
index ba01605..8c37bbf 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -2599,11 +2599,23 @@ state_store(struct md_rdev *rdev, const char *buf, size_t len)
err = 0;
}
} else if (cmd_match(buf, "re-add") && (test_bit(Faulty, &rdev->flags) || (rdev->raid_disk == -1))) {
+ /* clear_bit is performed _after_ all the devices
+ * have their local Faulty bit cleared. If any writes
+ * happen in the meantime in the local node, they
+ * will land in the local bitmap, which will be synced
+ * by this node eventually
+ */
+ if (mddev_is_clustered(rdev->mddev)) {
+ err = md_cluster_ops->gather_bitmaps(rdev);
+ if (err)
+ goto out;
+ }
clear_bit(Faulty, &rdev->flags);
err = add_bound_rdev(rdev);
}
if (!err)
sysfs_notify_dirent_safe(rdev->sysfs_state);
+out:
return err ? err : len;
}
static struct rdev_sysfs_entry rdev_state =
--
2.1.4
^ permalink raw reply related
* BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
From: Azat Khuzhin @ 2015-04-14 17:15 UTC (permalink / raw)
To: Kernel.org-Linux-RAID, neilb
$ git describe
v4.0-2620-gb79013b
During setting up partitions with mdadm, mdadm hung, after attaching to mdadm with strace I got next:
# pgrep mdadm | xargs strace -fp
Process 27389 attached - interrupt to quit
unlink("/dev/.tmp.md.27389:9:127") = 0
mknod("/tmp/.tmp.md.27389:9:127", S_IFBLK|0600, makedev(9, 127)) = 0
open("/tmp/.tmp.md.27389:9:127", O_RDWR|O_EXCL|O_DIRECT) <-- *hung*
After, I looked into dmesg, and found this:
[ 9627.630018] ------------[ cut here ]------------
[ 9627.630029] WARNING: CPU: 18 PID: 3330 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x5a/0x70()
[ 9627.630032] sysfs: cannot create duplicate filename '/devices/virtual/bdi/9:127'
[ 9627.630033] Modules linked in: xt_tcpudp iptable_filter ip_tables x_tables nfsd nfs lockd grace sunrpc ipmi_devintf netconsole configfs loop hid_generic usbhid hid x86_pkg_temp_thermal coretemp ghash_clmulni_intel aesni_intel ioatdma ehci_pci aes_x86_64 iTCO_wdt iTCO_ve
[ 9627.630074] CPU: 18 PID: 3330 Comm: mdadm Not tainted 4.0.0bl-azat-v6+ #1
[ 9627.630076] Hardware name: Supermicro X9DRD-7LN4F(-JBOD)/X9DRD-EF/X9DRD-7LN4F, BIOS 3.0a 12/05/2013
[ 9627.630077] 0000000000000000 ffffffff814e3fcc ffffffff813e590f ffff885f9bcd3808
[ 9627.630079] ffffffff8104575c ffff885f96acb000 ffff885fa4b3e3c0 ffff885fa2fec780
[ 9627.630081] ffff885fa4bc4000 0000000000000000 ffffffff810457d5 ffffffff814e5d78
[ 9627.630083] Call Trace:
[ 9627.630091] [<ffffffff813e590f>] ? dump_stack+0x40/0x50
[ 9627.630096] [<ffffffff8104575c>] ? warn_slowpath_common+0x7c/0xb0
[ 9627.630098] [<ffffffff810457d5>] ? warn_slowpath_fmt+0x45/0x50
[ 9627.630100] [<ffffffff81185092>] ? kernfs_path+0x42/0x50
[ 9627.630102] [<ffffffff811883da>] ? sysfs_warn_dup+0x5a/0x70
[ 9627.630104] [<ffffffff8118846e>] ? sysfs_create_dir_ns+0x7e/0x90
[ 9627.630108] [<ffffffff811d94ab>] ? kobject_add_internal+0x9b/0x2f0
[ 9627.630109] [<ffffffff811d9af6>] ? kobject_add+0x66/0xb0
[ 9627.630114] [<ffffffff812bb2e3>] ? device_add+0x263/0x620
[ 9627.630116] [<ffffffff812bb8a8>] ? device_create_groups_vargs+0xe8/0x100
[ 9627.630118] [<ffffffff812bb8d3>] ? device_create_vargs+0x13/0x20
[ 9627.630124] [<ffffffff810ed128>] ? bdi_register+0x68/0x150
[ 9627.630129] [<ffffffff811c535d>] ? add_disk+0x14d/0x4a0
[ 9627.630132] [<ffffffff811c585f>] ? alloc_disk_node+0xaf/0x100
[ 9627.630137] [<ffffffffa0252269>] ? md_alloc+0x1e9/0x350 [md_mod]
[ 9627.630141] [<ffffffffa02523db>] ? md_probe+0xb/0x20 [md_mod]
[ 9627.630143] [<ffffffff812c0654>] ? kobj_lookup+0x104/0x170
[ 9627.630147] [<ffffffffa02523d0>] ? md_alloc+0x350/0x350 [md_mod]
[ 9627.630149] [<ffffffff811c4da8>] ? get_gendisk+0x28/0xf0
[ 9627.630153] [<ffffffff8115fb74>] ? __blkdev_get+0x114/0x3c0
[ 9627.630156] [<ffffffff8115e590>] ? bdev_direct_access+0xa0/0xa0
[ 9627.630158] [<ffffffff8115e5a0>] ? bdev_test+0x10/0x10
[ 9627.630160] [<ffffffff8115fe58>] ? blkdev_get+0x38/0x310
[ 9627.630162] [<ffffffff81160170>] ? blkdev_get_by_dev+0x40/0x40
[ 9627.630167] [<ffffffff8112b3d3>] ? do_dentry_open.isra.16+0x153/0x320
[ 9627.630170] [<ffffffff811380f3>] ? do_last.isra.51+0x323/0xd50
[ 9627.630172] [<ffffffff8111f5b3>] ? kmem_cache_alloc+0x123/0x130
[ 9627.630174] [<ffffffff8113a97f>] ? path_openat+0x7f/0x610
[ 9627.630177] [<ffffffff810f7480>] ? tlb_flush_mmu_free+0x30/0x50
[ 9627.630180] [<ffffffff810fe800>] ? unmap_region+0xb0/0xf0
[ 9627.630182] [<ffffffff8113bb3b>] ? do_filp_open+0x2b/0x90
[ 9627.630187] [<ffffffff811472ec>] ? __alloc_fd+0x7c/0x120
[ 9627.630189] [<ffffffff8112c531>] ? do_sys_open+0x121/0x210
[ 9627.630193] [<ffffffff813ea097>] ? system_call_fastpath+0x12/0x6a
[ 9627.630195] ---[ end trace b7a3e9c6f05c2666 ]---
[ 9627.630196] ------------[ cut here ]------------
[ 9627.630198] WARNING: CPU: 18 PID: 3330 at lib/kobject.c:240 kobject_add_internal+0x274/0x2f0()
[ 9627.630200] kobject_add_internal failed for 9:127 with -EEXIST, don't try to register things with the same name in the same directory.
[ 9627.630201] Modules linked in: xt_tcpudp iptable_filter ip_tables x_tables nfsd nfs lockd grace sunrpc ipmi_devintf netconsole configfs loop hid_generic usbhid hid x86_pkg_temp_thermal coretemp ghash_clmulni_intel aesni_intel ioatdma ehci_pci aes_x86_64 iTCO_wdt iTCO_ve
[ 9627.630223] CPU: 18 PID: 3330 Comm: mdadm Tainted: G W 4.0.0bl-azat-v6+ #1
[ 9627.630224] Hardware name: Supermicro X9DRD-7LN4F(-JBOD)/X9DRD-EF/X9DRD-7LN4F, BIOS 3.0a 12/05/2013
[ 9627.630225] 0000000000000000 ffffffff814f2c88 ffffffff813e590f ffff885f9bcd3858
[ 9627.630227] ffffffff8104575c ffff885fa4bc4010 00000000ffffffef ffff885fa473f420
[ 9627.630229] ffff885fa4bc4000 0000000000000000 ffffffff810457d5 ffffffff814f2e48
[ 9627.630230] Call Trace:
[ 9627.630233] [<ffffffff813e590f>] ? dump_stack+0x40/0x50
[ 9627.630235] [<ffffffff8104575c>] ? warn_slowpath_common+0x7c/0xb0
[ 9627.630236] [<ffffffff810457d5>] ? warn_slowpath_fmt+0x45/0x50
[ 9627.630238] [<ffffffff8118846e>] ? sysfs_create_dir_ns+0x7e/0x90
[ 9627.630240] [<ffffffff811d9684>] ? kobject_add_internal+0x274/0x2f0
[ 9627.630242] [<ffffffff811d9af6>] ? kobject_add+0x66/0xb0
[ 9627.630244] [<ffffffff812bb2e3>] ? device_add+0x263/0x620
[ 9627.630245] [<ffffffff812bb8a8>] ? device_create_groups_vargs+0xe8/0x100
[ 9627.630247] [<ffffffff812bb8d3>] ? device_create_vargs+0x13/0x20
[ 9627.630250] [<ffffffff810ed128>] ? bdi_register+0x68/0x150
[ 9627.630252] [<ffffffff811c535d>] ? add_disk+0x14d/0x4a0
[ 9627.630255] [<ffffffff811c585f>] ? alloc_disk_node+0xaf/0x100
[ 9627.630258] [<ffffffffa0252269>] ? md_alloc+0x1e9/0x350 [md_mod]
[ 9627.630261] [<ffffffffa02523db>] ? md_probe+0xb/0x20 [md_mod]
[ 9627.630262] [<ffffffff812c0654>] ? kobj_lookup+0x104/0x170
[ 9627.630266] [<ffffffffa02523d0>] ? md_alloc+0x350/0x350 [md_mod]
[ 9627.630268] [<ffffffff811c4da8>] ? get_gendisk+0x28/0xf0
[ 9627.630270] [<ffffffff8115fb74>] ? __blkdev_get+0x114/0x3c0
[ 9627.630272] [<ffffffff8115e590>] ? bdev_direct_access+0xa0/0xa0
[ 9627.630274] [<ffffffff8115e5a0>] ? bdev_test+0x10/0x10
[ 9627.630276] [<ffffffff8115fe58>] ? blkdev_get+0x38/0x310
[ 9627.630278] [<ffffffff81160170>] ? blkdev_get_by_dev+0x40/0x40
[ 9627.630280] [<ffffffff8112b3d3>] ? do_dentry_open.isra.16+0x153/0x320
[ 9627.630282] [<ffffffff811380f3>] ? do_last.isra.51+0x323/0xd50
[ 9627.630283] [<ffffffff8111f5b3>] ? kmem_cache_alloc+0x123/0x130
[ 9627.630285] [<ffffffff8113a97f>] ? path_openat+0x7f/0x610
[ 9627.630287] [<ffffffff810f7480>] ? tlb_flush_mmu_free+0x30/0x50
[ 9627.630289] [<ffffffff810fe800>] ? unmap_region+0xb0/0xf0
[ 9627.630291] [<ffffffff8113bb3b>] ? do_filp_open+0x2b/0x90
[ 9627.630293] [<ffffffff811472ec>] ? __alloc_fd+0x7c/0x120
[ 9627.630295] [<ffffffff8112c531>] ? do_sys_open+0x121/0x210
[ 9627.630297] [<ffffffff813ea097>] ? system_call_fastpath+0x12/0x6a
[ 9627.630298] ---[ end trace b7a3e9c6f05c2667 ]---
[ 9627.630395] BUG: unable to handle kernel NULL pointer dereference at 0000000000000040
[ 9627.630430] IP: [<ffffffff8118869a>] sysfs_do_create_link_sd.isra.2+0x2a/0xb0
[ 9627.630524] PGD 5fa2d03067 PUD 5f9d679067 PMD 0
[ 9627.630550] Oops: 0000 [#1] SMP
[ 9627.630624] Modules linked in: xt_tcpudp iptable_filter ip_tables x_tables nfsd nfs lockd grace sunrpc ipmi_devintf netconsole configfs loop hid_generic usbhid hid x86_pkg_temp_thermal coretemp ghash_clmulni_intel aesni_intel ioatdma ehci_pci aes_x86_64 iTCO_wdt iTCO_ve
[ 9627.631073] CPU: 18 PID: 3330 Comm: mdadm Tainted: G W 4.0.0bl-azat-v6+ #1
[ 9627.631090] Hardware name: Supermicro X9DRD-7LN4F(-JBOD)/X9DRD-EF/X9DRD-7LN4F, BIOS 3.0a 12/05/2013
[ 9627.631109] task: ffff885fa4659f00 ti: ffff885f9bcd0000 task.ti: ffff885f9bcd0000
[ 9627.631124] RIP: 0010:[<ffffffff8118869a>] [<ffffffff8118869a>] sysfs_do_create_link_sd.isra.2+0x2a/0xb0
[ 9627.631162] RSP: 0018:ffff885f9bcd3a78 EFLAGS: 00010246
[ 9627.631189] RAX: 000000000000e6e6 RBX: 0000000000000040 RCX: 00000000000000e6
[ 9627.631219] RDX: ffffffff814e19d0 RSI: 0000000000000040 RDI: ffffffff81740d88
[ 9627.631249] RBP: ffffffff814e19d0 R08: 0000000000017d60 R09: ffff88607fcd7d60
[ 9627.631278] R10: ffff882fbf802400 R11: ffffea017e830e00 R12: 0000000000000001
[ 9627.631308] R13: ffff885fa5a61ca8 R14: ffff885fa4bc3c70 R15: ffff885fa4bc3c00
[ 9627.631338] FS: 00007f439e991700(0000) GS:ffff88607fcc0000(0000) knlGS:0000000000000000
[ 9627.631383] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 9627.631411] CR2: 0000000000000040 CR3: 0000005f9fe22000 CR4: 00000000001407e0
[ 9627.631440] Stack:
[ 9627.631460] ffff885fa4bc3c00 ffff885f9bf41428 ffff885fa4bc3c0c ffff885fa4bc3c80
[ 9627.631515] ffff885fa4bc3c70 ffffffff811c53f3 ffff885fa4bc3c00 ffffffff00000018
[ 9627.631569] 0090007f9bcd3b08 ffff885fa4bc3c00 0000000000000000 0000000000000001
[ 9627.631680] Call Trace:
[ 9627.631703] [<ffffffff811c53f3>] ? add_disk+0x1e3/0x4a0
[ 9627.631733] [<ffffffffa0252269>] ? md_alloc+0x1e9/0x350 [md_mod]
[ 9627.631763] [<ffffffffa02523db>] ? md_probe+0xb/0x20 [md_mod]
[ 9627.631791] [<ffffffff812c0654>] ? kobj_lookup+0x104/0x170
[ 9627.631820] [<ffffffffa02523d0>] ? md_alloc+0x350/0x350 [md_mod]
[ 9627.631849] [<ffffffff811c4da8>] ? get_gendisk+0x28/0xf0
[ 9627.631877] [<ffffffff8115fb74>] ? __blkdev_get+0x114/0x3c0
[ 9627.631905] [<ffffffff8115e590>] ? bdev_direct_access+0xa0/0xa0
[ 9627.631933] [<ffffffff8115e5a0>] ? bdev_test+0x10/0x10
[ 9627.631961] [<ffffffff8115fe58>] ? blkdev_get+0x38/0x310
[ 9627.631988] [<ffffffff81160170>] ? blkdev_get_by_dev+0x40/0x40
[ 9627.632017] [<ffffffff8112b3d3>] ? do_dentry_open.isra.16+0x153/0x320
[ 9627.632046] [<ffffffff811380f3>] ? do_last.isra.51+0x323/0xd50
[ 9627.632075] [<ffffffff8111f5b3>] ? kmem_cache_alloc+0x123/0x130
[ 9627.632103] [<ffffffff8113a97f>] ? path_openat+0x7f/0x610
[ 9627.632131] [<ffffffff810f7480>] ? tlb_flush_mmu_free+0x30/0x50
[ 9627.632159] [<ffffffff810fe800>] ? unmap_region+0xb0/0xf0
[ 9627.632186] [<ffffffff8113bb3b>] ? do_filp_open+0x2b/0x90
[ 9627.632215] [<ffffffff811472ec>] ? __alloc_fd+0x7c/0x120
[ 9627.632242] [<ffffffff8112c531>] ? do_sys_open+0x121/0x210
[ 9627.632270] [<ffffffff813ea097>] ? system_call_fastpath+0x12/0x6a
[ 9627.632298] Code: 00 48 85 d2 74 73 48 85 ff 74 6e 41 56 41 55 49 89 fd 41 54 55 48 c7 c7 88 0d 74 81 53 48 89 f3 41 89 cc 48 89 d5 e8 76 15 26 00 <48> 8b 1b 48 85 db 74 08 48 89 df e8 f6 c9 ff ff 80 05 d7 86 5b
[ 9627.632557] RIP [<ffffffff8118869a>] sysfs_do_create_link_sd.isra.2+0x2a/0xb0
[ 9627.632604] RSP <ffff885f9bcd3a78>
[ 9627.632627] CR2: 0000000000000040
[ 9627.633014] ---[ end trace b7a3e9c6f05c2668 ]---
Any assumptions?
^ permalink raw reply
* Re: Recovery Raid6 Degraded
From: Emanuel Domingos @ 2015-04-14 18:06 UTC (permalink / raw)
To: Mikael Abrahamsson; +Cc: linux-raid
In-Reply-To: <alpine.DEB.2.02.1504141617220.16871@uplift.swm.pp.se>
Thanks! worked perfectly
Follow results
#mdadm --stop /dev/md/ubuntu\:md-raid6_primary
#mdadm --assemble --force /dev/md/ubuntu\:md-raid6_primary /dev/sdaa
/dev/sdac /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdz
cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5]
[raid4] [raid10]
md124 : active raid6 sdf[0] sdz[5] sdj[8] sdi[3] sdh[2] sdg[1]
11721077760 blocks super 1.2 level 6, 512k chunk, algorithm 2
[8/6] [UUUUUU__]
md125 : active (auto-read-only) raid1 sdag[1]
97684688 blocks super 1.2 [2/1] [_U]
md126 : active raid6 sdad[1] sdv[2] sdy[5] sdw[3] sdx[4]
7814051840 blocks super 1.2 level 6, 512k chunk, algorithm 2
[6/5] [_UUUUU]
md127 : inactive sdd[13] sdc[15] sde[14] sda[10] sdb[11] sdt[4] sdr[2]
sdq[1] sdm[7] sdk[5] sdo[9] sdn[8]
23442162720 blocks super 1.2
unused devices: <none>
Adding two disks that were removed [8/6]
mdadm --manage /dev/md124 --add /dev/sdaa
mdadm --manage /dev/md124 --add /dev/sdac
cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5]
[raid4] [raid10]
md124 : active raid6 sdac[10] sdaa[9] sdf[0] sdz[5] sdj[8] sdi[3] sdh[2] sdg[1]
11721077760 blocks super 1.2 level 6, 512k chunk, algorithm 2
[8/6] [UUUUUU__]
[>....................] recovery = 0.4% (8112408/1953512960)
finish=6234.6min speed=5200K/sec
md125 : active (auto-read-only) raid1 sdag[1]
97684688 blocks super 1.2 [2/1] [_U]
md126 : active raid6 sdad[1] sdv[2] sdy[5] sdw[3] sdx[4]
7814051840 blocks super 1.2 level 6, 512k chunk, algorithm 2
[6/5] [_UUUUU]
md127 : inactive sdd[13] sdc[15] sde[14] sda[10] sdb[11] sdt[4] sdr[2]
sdq[1] sdm[7] sdk[5] sdo[9] sdn[8]
23442162720 blocks super 1.2
unused devices: <none>
mdadm --detail /dev/md124
/dev/md124:
Version : 1.2
Creation Time : Thu Sep 27 11:39:20 2012
Raid Level : raid6
Array Size : 11721077760 (11178.09 GiB 12002.38 GB)
Used Dev Size : 1953512960 (1863.02 GiB 2000.40 GB)
Raid Devices : 8
Total Devices : 8
Persistence : Superblock is persistent
Update Time : Tue Apr 14 14:37:56 2015
State : clean, degraded, recovering
Active Devices : 6
Working Devices : 8
Failed Devices : 0
Spare Devices : 2
Layout : left-symmetric
Chunk Size : 512K
Rebuild Status : 0% complete
Name : ubuntu:md-raid6_primary (local to host ubuntu)
UUID : cee8d180:d6275a41:599064c6:8894819e
Events : 1093711
Number Major Minor RaidDevice State
0 8 80 0 active sync /dev/sdf
1 8 96 1 active sync /dev/sdg
2 8 112 2 active sync /dev/sdh
3 8 128 3 active sync /dev/sdi
8 8 144 4 active sync /dev/sdj
5 65 144 5 active sync /dev/sdz
9 65 160 6 spare rebuilding /dev/sdaa
10 65 192 7 spare rebuilding /dev/sdac
Just wait for the complete rebuild! Great work. Thanks
2015-04-14 11:19 GMT-03:00 Mikael Abrahamsson <swmike@swm.pp.se>:
> On Tue, 14 Apr 2015, Emanuel Domingos wrote:
>
>> Hi, Mikael, hi guys!
>>
>>
>> Follow the errors found after building the new version of mdadm:
>>
>> #mdadm --stop /dev/md/ubuntu\:md-raid6_primary
>>
>> #mdadm --assemble --force /dev/md/ubuntu\:md-raid6_primary /dev/sdaa
>> /dev/sdac
>> /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdz
>>
>> mdadm: device /dev/md/ubuntu:md-raid6_primary exists but is not an md
>> array.
>
>
> Please call it /dev/md124 and not the above ubuntu: name. I have no idea
> what it is you're trying to do with that name. Also use --verbose when
> trying to do the assembly and see if you get any further information.
>
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
--
Emanuel Domingos
Cursando Bacharelado em Ciência da Computação - IFCE Campus Maracanaú
Técnico em Conectividade - IFCE Campus Maracanaú
--
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
^ permalink raw reply
* Re: Recovery Raid6 Degraded
From: John Stoffel @ 2015-04-14 20:27 UTC (permalink / raw)
To: Emanuel Domingos; +Cc: Mikael Abrahamsson, linux-raid
In-Reply-To: <CACsoFmiCoZGRoUWpxg_PLw6hyhW1mAB0TZFO94MZ6Kix-DxMOA@mail.gmail.com>
Make sure you add in a bitmap to your array, to make rebuilds quicker
after a system crash.
mdadm --grow /dev/md126 --bitmap internal
^ permalink raw reply
* Re: [PATCH 2/4] md-cluster: remove capabilities
From: gary @ 2015-04-15 2:24 UTC (permalink / raw)
To: Goldwyn Rodrigues, Guoqing Jiang; +Cc: neilb, linux-raid
In-Reply-To: <552CF96A.7000306@suse.de>
Hi Goldwyn,
>>> diff --git a/drivers/md/md.c b/drivers/md/md.c
>>> index bc11551..0c65e51 100644
>>> --- a/drivers/md/md.c
>>> +++ b/drivers/md/md.c
>>> @@ -2291,11 +2291,12 @@ static void export_rdev(struct md_rdev * rdev)
>>> kobject_put(&rdev->kobj);
>>> }
>>>
>>> -static void kick_rdev_from_array(struct md_rdev * rdev)
>>> +void md_kick_rdev_from_array(struct md_rdev * rdev)
>>> {
>>> unbind_rdev_from_array(rdev);
>>> export_rdev(rdev);
>>> }
>>> +EXPORT_SYMBOL_GPL(md_kick_rdev_from_array);
>>>
>>> static void export_array(struct mddev *mddev)
>>> {
>>> @@ -2306,7 +2307,7 @@ static void export_array(struct mddev *mddev)
>>> MD_BUG();
>>> continue;
>>> }
>>> - kick_rdev_from_array(rdev);
>>> + md_kick_rdev_from_array(rdev);
>>> }
>>> if (!list_empty(&mddev->disks))
>>> MD_BUG();
>>> @@ -2750,9 +2751,11 @@ state_store(struct md_rdev *rdev, const char
>>> *buf, size_t len)
>>> err = -EBUSY;
>>> else {
>>> struct mddev *mddev = rdev->mddev;
>>> - if (mddev_is_clustered(mddev))
>>> + if (mddev_is_clustered(mddev)) {
>>> md_cluster_ops->metadata_update_start(mddev);
>>> - kick_rdev_from_array(rdev);
>>> + md_cluster_ops->remove_disk(mddev, rdev);
>>> + }
>>> + md_kick_rdev_from_array(rdev);
>>>
>> For md-cluster, seems it is possible that md_kick_rdev_from_array could
>> be called twice,
>> is this what you want? Thanks.
>
>
> No, it would be called only once. There are two types of nodes in this
> case: one is sender and other received. The sender calls
> md_kick_rdev_from_array() in the regular flow of
> state_store/hot_remove_disk() while the receiver calls
> md_kick_rdev_from_array() in the process_remove_disk().
>
Thanks for explanation, both sender node and receiver node need to kick
the disk from array. I misunderstood it, :(.
Regards,
Guoqing
^ permalink raw reply
* Re: BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
From: Guoqing Jiang @ 2015-04-15 2:44 UTC (permalink / raw)
To: Azat Khuzhin; +Cc: Kernel.org-Linux-RAID, neilb
In-Reply-To: <20150414171537.GH25394@azat>
Azat Khuzhin wrote:
> $ git describe
> v4.0-2620-gb79013b
>
> During setting up partitions with mdadm, mdadm hung, after attaching to mdadm with strace I got next:
>
> # pgrep mdadm | xargs strace -fp
> Process 27389 attached - interrupt to quit
> unlink("/dev/.tmp.md.27389:9:127") = 0
> mknod("/tmp/.tmp.md.27389:9:127", S_IFBLK|0600, makedev(9, 127)) = 0
> open("/tmp/.tmp.md.27389:9:127", O_RDWR|O_EXCL|O_DIRECT) <-- *hung*
>
> After, I looked into dmesg, and found this:
> [ 9627.630018] ------------[ cut here ]------------
> [ 9627.630029] WARNING: CPU: 18 PID: 3330 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x5a/0x70()
> [ 9627.630032] sysfs: cannot create duplicate filename '/devices/virtual/bdi/9:127'
>
sysfs complains about duplicate filename, maybe you tried to create the
array with same node.
> [ 9627.630033] Modules linked in: xt_tcpudp iptable_filter ip_tables x_tables nfsd nfs lockd grace sunrpc ipmi_devintf netconsole configfs loop hid_generic usbhid hid x86_pkg_temp_thermal coretemp ghash_clmulni_intel aesni_intel ioatdma ehci_pci aes_x86_64 iTCO_wdt iTCO_ve
> [ 9627.630074] CPU: 18 PID: 3330 Comm: mdadm Not tainted 4.0.0bl-azat-v6+ #1
> [ 9627.630076] Hardware name: Supermicro X9DRD-7LN4F(-JBOD)/X9DRD-EF/X9DRD-7LN4F, BIOS 3.0a 12/05/2013
> [ 9627.630077] 0000000000000000 ffffffff814e3fcc ffffffff813e590f ffff885f9bcd3808
> [ 9627.630079] ffffffff8104575c ffff885f96acb000 ffff885fa4b3e3c0 ffff885fa2fec780
> [ 9627.630081] ffff885fa4bc4000 0000000000000000 ffffffff810457d5 ffffffff814e5d78
> [ 9627.630083] Call Trace:
> [ 9627.630091] [<ffffffff813e590f>] ? dump_stack+0x40/0x50
> [ 9627.630096] [<ffffffff8104575c>] ? warn_slowpath_common+0x7c/0xb0
> [ 9627.630098] [<ffffffff810457d5>] ? warn_slowpath_fmt+0x45/0x50
> [ 9627.630100] [<ffffffff81185092>] ? kernfs_path+0x42/0x50
> [ 9627.630102] [<ffffffff811883da>] ? sysfs_warn_dup+0x5a/0x70
> [ 9627.630104] [<ffffffff8118846e>] ? sysfs_create_dir_ns+0x7e/0x90
> [ 9627.630108] [<ffffffff811d94ab>] ? kobject_add_internal+0x9b/0x2f0
> [ 9627.630109] [<ffffffff811d9af6>] ? kobject_add+0x66/0xb0
> [ 9627.630114] [<ffffffff812bb2e3>] ? device_add+0x263/0x620
> [ 9627.630116] [<ffffffff812bb8a8>] ? device_create_groups_vargs+0xe8/0x100
> [ 9627.630118] [<ffffffff812bb8d3>] ? device_create_vargs+0x13/0x20
> [ 9627.630124] [<ffffffff810ed128>] ? bdi_register+0x68/0x150
> [ 9627.630129] [<ffffffff811c535d>] ? add_disk+0x14d/0x4a0
> [ 9627.630132] [<ffffffff811c585f>] ? alloc_disk_node+0xaf/0x100
> [ 9627.630137] [<ffffffffa0252269>] ? md_alloc+0x1e9/0x350 [md_mod]
> [ 9627.630141] [<ffffffffa02523db>] ? md_probe+0xb/0x20 [md_mod]
> [ 9627.630143] [<ffffffff812c0654>] ? kobj_lookup+0x104/0x170
> [ 9627.630147] [<ffffffffa02523d0>] ? md_alloc+0x350/0x350 [md_mod]
> [ 9627.630149] [<ffffffff811c4da8>] ? get_gendisk+0x28/0xf0
> [ 9627.630153] [<ffffffff8115fb74>] ? __blkdev_get+0x114/0x3c0
> [ 9627.630156] [<ffffffff8115e590>] ? bdev_direct_access+0xa0/0xa0
> [ 9627.630158] [<ffffffff8115e5a0>] ? bdev_test+0x10/0x10
> [ 9627.630160] [<ffffffff8115fe58>] ? blkdev_get+0x38/0x310
> [ 9627.630162] [<ffffffff81160170>] ? blkdev_get_by_dev+0x40/0x40
> [ 9627.630167] [<ffffffff8112b3d3>] ? do_dentry_open.isra.16+0x153/0x320
> [ 9627.630170] [<ffffffff811380f3>] ? do_last.isra.51+0x323/0xd50
> [ 9627.630172] [<ffffffff8111f5b3>] ? kmem_cache_alloc+0x123/0x130
> [ 9627.630174] [<ffffffff8113a97f>] ? path_openat+0x7f/0x610
> [ 9627.630177] [<ffffffff810f7480>] ? tlb_flush_mmu_free+0x30/0x50
> [ 9627.630180] [<ffffffff810fe800>] ? unmap_region+0xb0/0xf0
> [ 9627.630182] [<ffffffff8113bb3b>] ? do_filp_open+0x2b/0x90
> [ 9627.630187] [<ffffffff811472ec>] ? __alloc_fd+0x7c/0x120
> [ 9627.630189] [<ffffffff8112c531>] ? do_sys_open+0x121/0x210
> [ 9627.630193] [<ffffffff813ea097>] ? system_call_fastpath+0x12/0x6a
> [ 9627.630195] ---[ end trace b7a3e9c6f05c2666 ]---
> [ 9627.630196] ------------[ cut here ]------------
> [ 9627.630198] WARNING: CPU: 18 PID: 3330 at lib/kobject.c:240 kobject_add_internal+0x274/0x2f0()
> [ 9627.630200] kobject_add_internal failed for 9:127 with -EEXIST, don't try to register things with the same name in the same directory.
>
Ditto, seems the same issue.
Thanks,
Guoqing
^ permalink raw reply
* Re: BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
From: Azat Khuzhin @ 2015-04-15 8:47 UTC (permalink / raw)
To: Guoqing Jiang; +Cc: Kernel.org-Linux-RAID, neilb
In-Reply-To: <552DD097.9010504@suse.com>
On Wed, Apr 15, 2015 at 10:44:39AM +0800, Guoqing Jiang wrote:
> Azat Khuzhin wrote:
> > $ git describe
> > v4.0-2620-gb79013b
> >
> > During setting up partitions with mdadm, mdadm hung, after attaching to mdadm with strace I got next:
> >
> > # pgrep mdadm | xargs strace -fp
> > Process 27389 attached - interrupt to quit
> > unlink("/dev/.tmp.md.27389:9:127") = 0
> > mknod("/tmp/.tmp.md.27389:9:127", S_IFBLK|0600, makedev(9, 127)) = 0
> > open("/tmp/.tmp.md.27389:9:127", O_RDWR|O_EXCL|O_DIRECT) <-- *hung*
> >
> > After, I looked into dmesg, and found this:
> > [ 9627.630018] ------------[ cut here ]------------
> > [ 9627.630029] WARNING: CPU: 18 PID: 3330 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x5a/0x70()
> > [ 9627.630032] sysfs: cannot create duplicate filename '/devices/virtual/bdi/9:127'
> >
> sysfs complains about duplicate filename, maybe you tried to create the
> array with same node.
Yes, my steps was close to this:
$ mdadm --create /dev/md/foo --raid-devices=2 /dev/sda /dev/sdb
$ mdadm --stop --scan
$ mdadm --create /dev/md/foo --raid-devices=2 /dev/sda /dev/sdb
But it is not always reproduces.
Anyway the most important is not WARNING but BUG (also after that BUG
you can't umount all file systems normally -- i.e. on reboot).
^ permalink raw reply
* SV: mdadm raid 5 one disk overwritten file system failed
From: John Andre Taule @ 2015-04-15 11:47 UTC (permalink / raw)
To: linux-raid
In-Reply-To: <alpine.DEB.2.02.1502191521450.4007@uplift.swm.pp.se>
The guy that did this to us got 3 months jail.
His argument was that we should have failed the system manually (removed the
disk that he targeted with "dd"), and the raid should have magically fixed
itself. Anyone think this would have worked?
It was 5 hours of heavy write and deletes to the file system (ext4) and all
that time the dd command where running.
Later I also found this exact "test" of raid in mdadm documentation marking
it as not something you should do (will fail data integriy, eg corrupt
filesystem, period).
/regards
-----Opprinnelig melding-----
Fra: Mikael Abrahamsson [mailto:swmike@swm.pp.se]
Sendt: 19. februar 2015 15:24
Til: John Andre Taule
Kopi: linux-raid@vger.kernel.org
Emne: Re: mdadm raid 5 one disk overwritten file system failed
On Thu, 19 Feb 2015, John Andre Taule wrote:
> I'm a bit surprised that overwriting anything on the physical disk
> should corrupt the file system on the raid. I would think that would
> be similar to a disk crashing or failing in other ways.
Errr, in raid5 you have data blocks and parity blocks. WHen you overwrite
one of the component drives with zeroes, you're effectively doing the same
as writing 0:es to a non-raid drive every 3 $stripesize. You're zero:ing a
lot of the filesystem information.
> What you say that Linux might not have seen the disk as failing is
> interesting. This could explain why the file system got corrupted.
Correct. There is no mechanism that periodically checks the contents of the
superblock and fails the drive if it's not there anymore. So the drive is
never failed.
--
Mikael Abrahamsson email: swmike@swm.pp.se
^ permalink raw reply
* Re: mdadm raid 5 one disk overwritten file system failed
From: Mikael Abrahamsson @ 2015-04-15 12:38 UTC (permalink / raw)
To: John Andre Taule; +Cc: linux-raid
In-Reply-To: <00b901d07771$f56c0010$e0440030$@johnandre.net>
On Wed, 15 Apr 2015, John Andre Taule wrote:
> The guy that did this to us got 3 months jail.
>
> His argument was that we should have failed the system manually (removed the
> disk that he targeted with "dd"), and the raid should have magically fixed
> itself. Anyone think this would have worked?
> It was 5 hours of heavy write and deletes to the file system (ext4) and all
> that time the dd command where running.
Not a chance, after 5 hours dd basically had overwritten 1/3 of the data
spread out across a large portion of the volume. We're talking massive
file and filesystem corruption.
I don't know enough about zfs, but I am under the impression that zfs
perhaps could have detected the bad information (because checksum would no
longer match on those blocks) if you would have had native zfs to create
the raid5. I don't have personal experience with zfs though, someone else
might be able to answer that part.
It's really hard to protect against this kind of intentional sabotage.
Even if you would have run zfs instead, he could have just dd:ed to the
actual raid volume instead.
^ permalink raw reply
* Re: mdadm raid 5 one disk overwritten file system failed
From: Wols Lists @ 2015-04-15 18:27 UTC (permalink / raw)
To: Mikael Abrahamsson, John Andre Taule; +Cc: linux-raid
In-Reply-To: <alpine.DEB.2.02.1504151432250.16871@uplift.swm.pp.se>
On 15/04/15 13:38, Mikael Abrahamsson wrote:
> On Wed, 15 Apr 2015, John Andre Taule wrote:
>
>> The guy that did this to us got 3 months jail.
>>
>> His argument was that we should have failed the system manually
>> (removed the
>> disk that he targeted with "dd"), and the raid should have magically
>> fixed
>> itself. Anyone think this would have worked?
>> It was 5 hours of heavy write and deletes to the file system (ext4)
>> and all
>> that time the dd command where running.
>
> Not a chance, after 5 hours dd basically had overwritten 1/3 of the data
> spread out across a large portion of the volume. We're talking massive
> file and filesystem corruption.
Wouldn't failing the drive and then adding it "as new" (triggering a
rebuild) recover any files that hadn't been modified while the dd was
running?
Of course, that still means any directories that had been modified would
likely have also been corrupted, in all probability landing the files in
them into "lost+found" and necessitating a massive recataloging of all
the files in there.
The data would have been recovered, but the directory structure ... not
a nice recovery job.
Cheers,
Wol
^ permalink raw reply
* Re: RAID 5 "magicaly" become a RAID0
From: Thomas MARCHESSEAU @ 2015-04-16 8:53 UTC (permalink / raw)
To: Phil Turmel, linux-raid; +Cc: Roger Heflin
In-Reply-To: <552D08C0.1010106@turmel.org>
Hi Team ,
>
>Very good to hear this.
It crashed once , but after a reboot and re-assemble , i¹ve backuped
_everything_
-> Thank you very much for you support !
>
>Yes, just --add a spare device to the array, then --grow --level=6 to
>start a live reshape.
I tryed , but it failed with many buffer I/O error , ( mostly on the last
4 drives , ( not sure , but seems hosted on the same chipset)
And now , i have tons of :
Buffer I/O error on device sdf , logical block 12
Š logical block 11 Š and so on
Same on SDH
>
--
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
^ permalink raw reply
* Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
From: Alex Elsayed @ 2015-04-16 9:23 UTC (permalink / raw)
To: dm-devel; +Cc: linux-raid, linux-kernel, linux-pm
In-Reply-To: <20150409140842.GA9779@redhat.com>
Mike Snitzer wrote:
> On Thu, Apr 09 2015 at 9:28am -0400,
> Pali Rohár <pali.rohar@gmail.com> wrote:
>
>> On Thursday 09 April 2015 09:12:08 Mike Snitzer wrote:
>> > On Mon, Apr 06 2015 at 9:29am -0400,
>> > Pali Rohár <pali.rohar@gmail.com> wrote:
>> >
>> > > On Monday 06 April 2015 15:00:46 Mike Snitzer wrote:
>> > > > On Sun, Apr 05 2015 at 1:20pm -0400,
>> > > >
>> > > > Pali Rohár <pali.rohar@gmail.com> wrote:
>> > > > > This patch series increase security of suspend and hibernate
>> > > > > actions. It allows user to safely wipe crypto keys before
>> > > > > suspend and hibernate actions starts without race
>> > > > > conditions on userspace process with heavy I/O.
>> > > > >
>> > > > > To automatically wipe cryto key for <device> before
>> > > > > hibernate action call: $ dmsetup message <device> 0 key
>> > > > > wipe_on_hibernation 1
>> > > > >
>> > > > > To automatically wipe cryto key for <device> before suspend
>> > > > > action call: $ dmsetup message <device> 0 key
>> > > > > wipe_on_suspend 1
>> > > > >
>> > > > > (Value 0 after wipe_* string reverts original behaviour - to
>> > > > > not wipe key)
>> > > >
>> > > > Can you elaborate on the attack vector your changes are meant
>> > > > to protect against? The user already authorized access, why
>> > > > is it inherently dangerous to _not_ wipe the associated key
>> > > > across these events?
>> > >
>> > > Hi,
>> > >
>> > > yes, I will try to explain current problems with cryptsetup
>> > > luksSuspend command and hibernation.
>> > >
>> > > First, sometimes it is needed to put machine into other hands.
>> > > You can still watch other person what is doing with machine, but
>> > > once if you let machine unlocked (e.g opened luks disk), she/he
>> > > can access encrypted data.
>> > >
>> > > If you turn off machine, it could be safe, because luks disk
>> > > devices are locked. But if you enter machine into suspend or
>> > > hibernate state luks devices are still open. And my patches try
>> > > to achieve similar security as when machine is off (= no crypto
>> > > keys in RAM or on swap).
>> > >
>> > > When doing hibernate on unencrypted swap it is to prevent leaking
>> > > crypto keys to hibernate image (which is stored in swap).
>> > >
>> > > When doing suspend action it is again to prevent leaking crypto
>> > > keys. E.g when you suspend laptop and put it off (somebody can
>> > > remove RAMs and do some cold boot attack).
>> > >
>> > > The most common situation is:
>> > > You have mounted partition from dm-crypt device (e.g. /home/),
>> > > some userspace processes access it (e.g opened firefox which
>> > > still reads/writes to cache ~/.firefox/) and you want to drop
>> > > crypto keys from kernel for some time.
>> > >
>> > > For that operation there is command cryptsetup luksSuspend, which
>> > > suspend dm device and then tell kernel to wipe crypto keys. All
>> > > I/O operations are then stopped and userspace processes which
>> > > want to do some those I/O operations are stopped too (until you
>> > > call cryptsetup luksResume and enter correct key).
>> > >
>> > > Now if you want to suspend/hiberate your machine (when some of dm
>> > > devices are suspeneded and some processes are stopped due to
>> > > pending I/O) it is not possible. Kernel freeze_processes function
>> > > will fail because userspace processes are still stopped inside
>> > > some I/O syscall (read/write, etc,...).
>> > >
>> > > My patches fixes this problem and do those operations (suspend dm
>> > > device, wipe crypto keys, enter suspend/hiberate) in correct
>> > > order and without race condition.
>> > >
>> > > dm device is suspended *after* userspace processes are freezed
>> > > and after that are crypto keys wiped. And then computer/laptop
>> > > enters into suspend/hibernate state.
>> >
>> > Wouldn't it be better to fix freeze_processes() to be tolerant of
>> > processes that are hung as a side-effect of their backing storage being
>> > suspended? A hibernate shouldn't fail simply because a user chose to
>> > suspend a DM device.
>> >
>> > Then this entire problem goes away and the key can be wiped from
>> > userspace (like you said above).
>>
>> Still there will be race condition. Before hibernation (and device
>> poweroff) we should have synced disks and filesystems to prevent data
>> lose (or other damage) as more as we can. And if there will be some
>> application which using lot of I/O (e.g normal firefox) then there
>> always will be race condtion.
>
> The DM suspend will take care of flushing any pending I/O. So I don't
> see where the supposed race is...
>
> Anything else that is trapped in userspace memory will be there when the
> machine resumes.
>
>> So proper way is to wipe luks crypto keys *after* userspace processes
>> are freezed.
>
> I know you believe that I'm just not accepting that at face value.
Um, pardon me if I'm being naive, but what about the case of hibernation
where the swapdev and the root device are both LVs on the same dm_crypt
device?
The kernel is writing to swap _after_ userspace processes are all frozen;
that seems to me like an ordering dependency entirely incompatible with
userspace dropping the key...
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
^ permalink raw reply
* [PATCH] dm crypt: fix error return code in crypt_ctr()
From: weiyj_lk @ 2015-04-16 12:21 UTC (permalink / raw)
To: Alasdair Kergon, Mike Snitzer, Neil Brown
Cc: Wei Yongjun, dm-devel, linux-raid
From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
Fix to return a negative error code from the error handling
case instead of 0, as done elsewhere in this function.
Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
---
drivers/md/dm-crypt.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c
index 713a962..8154f58 100644
--- a/drivers/md/dm-crypt.c
+++ b/drivers/md/dm-crypt.c
@@ -1816,6 +1816,7 @@ static int crypt_ctr(struct dm_target *ti, unsigned int argc, char **argv)
if (ret)
goto bad;
+ ret = -EINVAL;
while (opt_params--) {
opt_string = dm_shift_arg(&as);
if (!opt_string) {
^ permalink raw reply related
* Re: RAID 5 "magicaly" become a RAID0
From: Phil Turmel @ 2015-04-16 12:25 UTC (permalink / raw)
To: Thomas MARCHESSEAU, linux-raid; +Cc: Roger Heflin
In-Reply-To: <D1554172.8F19F%marchesseau@gmail.com>
Good morning Thomas,
On 04/16/2015 04:53 AM, Thomas MARCHESSEAU wrote:
> Hi Team ,
>
>>
>> Very good to hear this.
> It crashed once , but after a reboot and re-assemble , i¹ve backuped
> _everything_
>
> -> Thank you very much for you support !
You're welcome.
>> Yes, just --add a spare device to the array, then --grow --level=6 to
>> start a live reshape.
>
> I tryed , but it failed with many buffer I/O error , ( mostly on the last
> 4 drives , ( not sure , but seems hosted on the same chipset)
> And now , i have tons of :
> Buffer I/O error on device sdf , logical block 12
> Š logical block 11 Š and so on
>
> Same on SDH
You mentioned a possibly loose sata cable causing the initial problem.
I'm not so sure. I think you should check your power supply.
The smartctl reports you supplied eliminate the most common problem,
timeout mismatch, as you have nice raid-rated drives. The next most
common problem I've seen is insufficient power, which is most apparent
when writing.
Add up all of the power consumption ratings of your hardware to make
sure a new power supply is suitable. And if you have/get a multiple
rail supply, make sure you spread the load across the independent circuits.
Phil
--
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
^ permalink raw reply
* [PATCH] Manage: prevent re-adding a raid1 device that was assembled on its own
From: nhdailey @ 2015-04-16 20:03 UTC (permalink / raw)
To: linux-raid; +Cc: Nate Dailey
From: Nate Dailey <nate.dailey@stratus.com>
When re-adding a device to a RAID1, check if it appears to have been assembled
on its own and prevent the re-add if it has (unless --force is given). This
prevents overwriting unique data on the device to be added, and prevents
incomplete resync if a bitmap is in use.
To determine this, get the raid_disk numbers for devices already in the array,
and check those against the superblock of the device-to-be-added. If any active
disk shows as faulty/removed, then the device being added was likely assembled
on its own.
Signed-off-by: Nate Dailey <nate.dailey@stratus.com>
---
Manage.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 52 insertions(+), 3 deletions(-)
diff --git a/Manage.c b/Manage.c
index d3cfb55..f1df608 100644
--- a/Manage.c
+++ b/Manage.c
@@ -593,17 +593,45 @@ static void add_set(struct mddev_dev *dv, int fd, char set_char)
}
}
+int assembled_separately(int fd, struct supertype *tst, char *devmap)
+{
+ mdu_disk_info_t disc;
+ int j;
+
+ /* This device may have been assembled on its own if the superblock
+ * indicates that some device in the running array is faulty/removed.
+ */
+ for (j = 0; j < tst->max_devs; j++) {
+ disc.number = j;
+ if (ioctl(fd, GET_DISK_INFO, &disc))
+ continue;
+ if (disc.major == 0 && disc.minor == 0)
+ continue;
+ if (disc.state & (1<<MD_DISK_FAULTY | 1<<MD_DISK_REMOVED))
+ continue;
+ if (disc.raid_disk < 0)
+ continue;
+ if (devmap[disc.raid_disk] == 0)
+ return 1;
+ }
+
+ return 0;
+}
+
int attempt_re_add(int fd, int tfd, struct mddev_dev *dv,
struct supertype *dev_st, struct supertype *tst,
unsigned long rdev,
- char *update, char *devname, int verbose,
+ char *update, char *devname, int force, int verbose,
mdu_array_info_t *array)
{
struct mdinfo mdi;
int duuid[4];
int ouuid[4];
+ char *devmap = NULL;
- dev_st->ss->getinfo_super(dev_st, &mdi, NULL);
+ devmap = calloc(array->raid_disks, 1);
+ mdi.array.raid_disks = array->raid_disks;
+ dev_st->ss->getinfo_super(dev_st, &mdi, devmap);
dev_st->ss->uuid_from_super(dev_st, ouuid);
if (tst->sb)
tst->ss->uuid_from_super(tst, duuid);
@@ -630,6 +658,22 @@ int attempt_re_add(int fd, int tfd, struct mddev_dev *dv,
|| disc.major != 0 || disc.minor != 0
)
goto skip_re_add;
+
+ if (array->level == 1 &&
+ assembled_separately(fd, tst, devmap)) {
+ if (!force) {
+ pr_err("not adding %s as it reports a device in the active array as failed.\n"
+ " Add --force if you really want to add this device.\n",
+ dv->devname);
+ free(devmap);
+ return 1;
+ }
+ pr_err("%s reports a device in the active array as failed.\n"
+ " Adding anyway as --force was given.\n",
+ dv->devname);
+ goto skip_re_add;
+ }
+
disc.major = major(rdev);
disc.minor = minor(rdev);
disc.number = mdi.disk.number;
@@ -645,6 +689,7 @@ int attempt_re_add(int fd, int tfd, struct mddev_dev *dv,
tfd = dev_open(dv->devname, O_RDWR);
if (tfd < 0) {
pr_err("failed to open %s for superblock update during re-add\n", dv->devname);
+ free(devmap);
return -1;
}
@@ -665,6 +710,7 @@ int attempt_re_add(int fd, int tfd, struct mddev_dev *dv,
close(tfd);
if (rv != 0) {
pr_err("failed to update superblock during re-add\n");
+ free(devmap);
return -1;
}
}
@@ -673,17 +719,20 @@ int attempt_re_add(int fd, int tfd, struct mddev_dev *dv,
if (ioctl(fd, ADD_NEW_DISK, &disc) == 0) {
if (verbose >= 0)
pr_err("re-added %s\n", dv->devname);
+ free(devmap);
return 1;
}
if (errno == ENOMEM || errno == EROFS) {
pr_err("add new device failed for %s: %s\n",
dv->devname, strerror(errno));
+ free(devmap);
if (dv->disposition == 'M')
return 0;
return -1;
}
}
skip_re_add:
+ free(devmap);
return 0;
}
@@ -805,7 +854,7 @@ int Manage_add(int fd, int tfd, struct mddev_dev *dv,
dev_st, tst,
rdev,
update, devname,
- verbose,
+ force, verbose,
array);
dev_st->ss->free_super(dev_st);
if (rv)
--
1.8.3.1
^ permalink raw reply related
* mdadm hang when one subdev error(raid1)
From: 席智勇 @ 2015-04-17 7:23 UTC (permalink / raw)
To: linux-raid
hi all:
I create some raid1-device by mdadm, when one subdev error, all mdadm related operation just hang there, process state was D.
The backgroud is a physical disk was error, so a subdev which is part of the error disk created by device mapper must be errorred, then i did the command 'mdadm --fail' to fail the subdev from the md device, I found it not responsable, just hang there、I tryed 'mdadm --remove', even 'mdadm -D', all hang there. Later, I found not just mdadm operation hang on the problem md device, all mdadm operation on the machine connot be excute.
I wana find out what's the problem is, is it a bug of raid when disk error occur， or a problem of my system, because when i found the mdadm hang, the errored disk(/dev/sdp)just missing from my system, I said the disk was error judging from the error log in raid card log.
Can anyone give me a help？
thanks.
uname -a :Linux **-***-***-** 3.10.45-****-amd64 #1 SMP Tue Jul 1 01:52:20 UTC 2014 x86_64 GNU/Linux
mdadm --version:mdadm - v3.2.5 - 18th May 2012
kern.log:
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561205] kvm D ffff88407f313f40 0 11581 1 0x00000000
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561209] ffff88356e846080 0000000000000082 0000000000000092 ffff881fe2d6a080
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561215] 0000000000013f40 ffff882849dfdfd8 ffff882849dfdfd8 ffff88356e846080
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561219] ffffffff8139958c ffff881cac478000 ffff882849dfdcb0 ffff881cac478290
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561224] Call Trace:
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561233] [<ffffffff8139958c>] ? _raw_spin_unlock_irqrestore+0xc/0xd
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561266] [<ffffffffa02efff0>] ? md_write_start+0x131/0x147 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561271] [<ffffffff81059c2f>] ? abort_exclusive_wait+0x79/0x79
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561275] [<ffffffffa05c2762>] ? make_request+0x37/0xa63 [raid1]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561284] [<ffffffffa02f4b7e>] ? md_make_request+0xee/0x1df [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561295] [<ffffffffa0006902>] ? dm_request+0x150/0x163 [dm_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561300] [<ffffffff811b3efc>] ? generic_make_request+0x96/0xd5
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561304] [<ffffffff811b4c79>] ? submit_bio+0x10a/0x13b
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561307] [<ffffffff811b6b0a>] ? blkdev_issue_flush+0x86/0xc4
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561311] [<ffffffff8113b298>] ? blkdev_fsync+0x2b/0x37
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561315] [<ffffffff81134a43>] ? do_fsync+0x2b/0x50
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561318] [<ffffffff81134c4f>] ? SyS_fdatasync+0xb/0xf
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561356] [<ffffffff8139ea69>] ? system_call_fastpath+0x16/0x1b
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.561367] INFO: task md52_raid1:39767 blocked for more than 120 seconds.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.563976] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.566971] md52_raid1 D ffff88407f233f40 0 39767 2 0x00000000
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.566975] ffff883e60fa9810 0000000000000046 ffff883e60fa9810 ffff881fe2d620c0
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.566981] 0000000000013f40 ffff883d61523fd8 ffff883d61523fd8 ffff883e60fa9810
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.566985] ffffffff8139958c ffff883d61523c60 ffff881cac478000 ffff881cac478290
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.566990] Call Trace:
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.566995] [<ffffffff8139958c>] ? _raw_spin_unlock_irqrestore+0xc/0xd
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567007] [<ffffffffa02f4d65>] ? md_super_wait+0x69/0x7f [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567011] [<ffffffff81059c2f>] ? abort_exclusive_wait+0x79/0x79
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567019] [<ffffffffa02f5131>] ? md_update_sb+0x3b6/0x4b8 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567023] [<ffffffff813995cb>] ? _raw_spin_lock_irqsave+0x14/0x35
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567030] [<ffffffffa02f59ee>] ? md_check_recovery+0x1c6/0x3d1 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567034] [<ffffffffa05c31cc>] ? raid1d+0x3e/0xb22 [raid1]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567038] [<ffffffff813988db>] ? __schedule+0x4e7/0x53d
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567042] [<ffffffff813978a3>] ? schedule_timeout+0x2c/0x123
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567045] [<ffffffff813995cb>] ? _raw_spin_lock_irqsave+0x14/0x35
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567048] [<ffffffff813995cb>] ? _raw_spin_lock_irqsave+0x14/0x35
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567088] [<ffffffffa02f02ed>] ? md_thread+0x114/0x132 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567092] [<ffffffff81059c2f>] ? abort_exclusive_wait+0x79/0x79
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567100] [<ffffffffa02f01d9>] ? signal_pending+0x10/0x10 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567107] [<ffffffffa02f01d9>] ? signal_pending+0x10/0x10 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567110] [<ffffffff81059295>] ? kthread+0x81/0x89
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567113] [<ffffffff81059214>] ? __kthread_parkme+0x5d/0x5d
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567117] [<ffffffff8139e9bc>] ? ret_from_fork+0x7c/0xb0
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567120] [<ffffffff81059214>] ? __kthread_parkme+0x5d/0x5d
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.567125] INFO: task kvm:19762 blocked for more than 120 seconds.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.570192] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573492] kvm D ffff88407f273f40 0 19762 1 0x00000000
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573496] ffff883fc90f97d0 0000000000000082 0000000000011200 ffff881fe2d64040
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573502] 0000000000013f40 ffff882aad01dfd8 ffff882aad01dfd8 ffff883fc90f97d0
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573507] ffffffff8139958c ffff881fb5475800 ffff882aad01dcb0 ffff881fb5475a90
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573512] Call Trace:
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573517] [<ffffffff8139958c>] ? _raw_spin_unlock_irqrestore+0xc/0xd
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573529] [<ffffffffa02efff0>] ? md_write_start+0x131/0x147 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573545] [<ffffffff81059c2f>] ? abort_exclusive_wait+0x79/0x79
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573549] [<ffffffffa05c2762>] ? make_request+0x37/0xa63 [raid1]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573557] [<ffffffffa000679f>] ? __split_and_process_bio+0x40d/0x420 [dm_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573561] [<ffffffff81100cbd>] ? ____cache_alloc+0x25d/0x293
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573569] [<ffffffffa02f4b7e>] ? md_make_request+0xee/0x1df [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573576] [<ffffffffa0006902>] ? dm_request+0x150/0x163 [dm_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573580] [<ffffffff811b3efc>] ? generic_make_request+0x96/0xd5
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573583] [<ffffffff811b4c79>] ? submit_bio+0x10a/0x13b
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573586] [<ffffffff811b6b0a>] ? blkdev_issue_flush+0x86/0xc4
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573590] [<ffffffff8113b298>] ? blkdev_fsync+0x2b/0x37
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573593] [<ffffffff81134a43>] ? do_fsync+0x2b/0x50
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573596] [<ffffffff81134c4f>] ? SyS_fdatasync+0xb/0xf
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573600] [<ffffffff8139ea69>] ? system_call_fastpath+0x16/0x1b
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.573603] INFO: task kvm:9147 blocked for more than 120 seconds.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.576936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580590] kvm D ffff88407f3f3f40 0 9147 1 0x00000000
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580594] ffff883fd9bfd080 0000000000000082 0000000000000096 ffff881fe2db5040
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580631] 0000000000013f40 ffff882da06a1fd8 ffff882da06a1fd8 ffff883fd9bfd080
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580635] ffffffff8139958c ffff881fb5475800 ffff882da06a1820 ffff881fb5475a90
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580648] Call Trace:
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580653] [<ffffffff8139958c>] ? _raw_spin_unlock_irqrestore+0xc/0xd
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580666] [<ffffffffa02efff0>] ? md_write_start+0x131/0x147 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580670] [<ffffffff81059c2f>] ? abort_exclusive_wait+0x79/0x79
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580674] [<ffffffffa05c2762>] ? make_request+0x37/0xa63 [raid1]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580678] [<ffffffff81399449>] ? _raw_read_lock_irqsave+0x21/0x2a
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580685] [<ffffffffa000679f>] ? __split_and_process_bio+0x40d/0x420 [dm_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580689] [<ffffffff81102005>] ? kmem_cache_alloc+0xe1/0x154
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580697] [<ffffffffa02f4b7e>] ? md_make_request+0xee/0x1df [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580704] [<ffffffffa0006902>] ? dm_request+0x150/0x163 [dm_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580708] [<ffffffff811b3efc>] ? generic_make_request+0x96/0xd5
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580712] [<ffffffff811b4c79>] ? submit_bio+0x10a/0x13b
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580716] [<ffffffff8113ce89>] ? dio_bio_submit+0x68/0x88
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580719] [<ffffffff8113dc35>] ? do_blockdev_direct_IO+0x957/0xae8
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580723] [<ffffffff8113aef1>] ? I_BDEV+0x8/0x8
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580752] [<ffffffff810c800a>] ? generic_file_direct_write+0xe3/0x14a
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580755] [<ffffffff810c818c>] ? __generic_file_aio_write+0x11b/0x1ff
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580759] [<ffffffff8113b617>] ? blkdev_aio_write+0x44/0x93
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580763] [<ffffffff811120b3>] ? do_sync_write+0x55/0x7c
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580767] [<ffffffff81112ab0>] ? vfs_write+0x9d/0x103
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580770] [<ffffffff81112eb9>] ? SyS_pwrite64+0x61/0x87
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580773] [<ffffffff8139ea69>] ? system_call_fastpath+0x16/0x1b
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.580778] INFO: task md42_raid1:36156 blocked for more than 120 seconds.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.584560] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588685] md42_raid1 D ffff88207fa33f40 0 36156 2 0x00000000
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588690] ffff881d0b324080 0000000000000046 ffff881d0b324080 ffff881fe2d62810
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588695] 0000000000013f40 ffff881fe1157fd8 ffff881fe1157fd8 ffff881d0b324080
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588699] ffffffff8139958c ffff881fe1157c60 ffff881fb5475800 ffff881fb5475a90
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588703] Call Trace:
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588710] [<ffffffff8139958c>] ? _raw_spin_unlock_irqrestore+0xc/0xd
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588734] [<ffffffffa02f4d65>] ? md_super_wait+0x69/0x7f [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588738] [<ffffffff81059c2f>] ? abort_exclusive_wait+0x79/0x79
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588745] [<ffffffffa02f5131>] ? md_update_sb+0x3b6/0x4b8 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588750] [<ffffffff8100c02f>] ? load_TLS+0x7/0xa
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588758] [<ffffffffa02f59ee>] ? md_check_recovery+0x1c6/0x3d1 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588761] [<ffffffffa05c31cc>] ? raid1d+0x3e/0xb22 [raid1]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588766] [<ffffffff81049389>] ? lock_timer_base.isra.35+0x23/0x48
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588769] [<ffffffff810490d4>] ? detach_if_pending+0x18/0x6c
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588772] [<ffffffff8139958c>] ? _raw_spin_unlock_irqrestore+0xc/0xd
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588775] [<ffffffff810494ae>] ? try_to_del_timer_sync+0x4e/0x59
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588778] [<ffffffff810494e0>] ? del_timer_sync+0x27/0x44
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588781] [<ffffffff8139796c>] ? schedule_timeout+0xf5/0x123
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588784] [<ffffffff813995cb>] ? _raw_spin_lock_irqsave+0x14/0x35
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588787] [<ffffffff813995cb>] ? _raw_spin_lock_irqsave+0x14/0x35
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588794] [<ffffffffa02f02ed>] ? md_thread+0x114/0x132 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588797] [<ffffffff81059c2f>] ? abort_exclusive_wait+0x79/0x79
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588804] [<ffffffffa02f01d9>] ? signal_pending+0x10/0x10 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588810] [<ffffffffa02f01d9>] ? signal_pending+0x10/0x10 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588813] [<ffffffff81059295>] ? kthread+0x81/0x89
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588816] [<ffffffff81059214>] ? __kthread_parkme+0x5d/0x5d
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588819] [<ffffffff8139e9bc>] ? ret_from_fork+0x7c/0xb0
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588822] [<ffffffff81059214>] ? __kthread_parkme+0x5d/0x5d
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.588834] INFO: task kvm:14262 blocked for more than 120 seconds.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.592943] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597362] kvm D ffff88207fbb3f40 0 14262 1 0x00000000
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597365] ffff88361cc91080 0000000000000082 0000000000000092 ffff881fe2db3810
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597371] 0000000000013f40 ffff882849fd9fd8 ffff882849fd9fd8 ffff88361cc91080
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597374] ffffffff8139958c ffff883fe1297000 ffff882849fd9cb0 ffff883fe1297290
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597378] Call Trace:
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597383] [<ffffffff8139958c>] ? _raw_spin_unlock_irqrestore+0xc/0xd
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597400] [<ffffffffa02efff0>] ? md_write_start+0x131/0x147 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597403] [<ffffffff81059c2f>] ? abort_exclusive_wait+0x79/0x79
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597407] [<ffffffffa05c2762>] ? make_request+0x37/0xa63 [raid1]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597415] [<ffffffffa02f4b7e>] ? md_make_request+0xee/0x1df [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597422] [<ffffffffa0006902>] ? dm_request+0x150/0x163 [dm_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597426] [<ffffffff811b3efc>] ? generic_make_request+0x96/0xd5
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597430] [<ffffffff811b4c79>] ? submit_bio+0x10a/0x13b
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597433] [<ffffffff811b6b0a>] ? blkdev_issue_flush+0x86/0xc4
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597438] [<ffffffff8113b298>] ? blkdev_fsync+0x2b/0x37
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597442] [<ffffffff81134a43>] ? do_fsync+0x2b/0x50
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597445] [<ffffffff81134c4f>] ? SyS_fdatasync+0xb/0xf
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597449] [<ffffffff8139ea69>] ? system_call_fastpath+0x16/0x1b
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.597452] INFO: task kvm:14266 blocked for more than 120 seconds.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.602000] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606850] kvm D ffff88207fa53f40 0 14266 1 0x00000000
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606854] ffff883e6f7a3810 0000000000000082 0000000000000096 ffff881fe2d63850
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606860] 0000000000013f40 ffff883c8fc49fd8 ffff883c8fc49fd8 ffff883e6f7a3810
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606865] ffffffff8139958c ffff881b5fa52800 ffff883c8fc49700 ffff881b5fa52a90
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606870] Call Trace:
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606877] [<ffffffff8139958c>] ? _raw_spin_unlock_irqrestore+0xc/0xd
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606897] [<ffffffffa02efff0>] ? md_write_start+0x131/0x147 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606901] [<ffffffff81059c2f>] ? abort_exclusive_wait+0x79/0x79
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606906] [<ffffffffa05c2762>] ? make_request+0x37/0xa63 [raid1]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606909] [<ffffffff81399449>] ? _raw_read_lock_irqsave+0x21/0x2a
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606917] [<ffffffffa000679f>] ? __split_and_process_bio+0x40d/0x420 [dm_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606925] [<ffffffffa02f4b7e>] ? md_make_request+0xee/0x1df [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606932] [<ffffffffa0006902>] ? dm_request+0x150/0x163 [dm_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606936] [<ffffffff811b3efc>] ? generic_make_request+0x96/0xd5
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606940] [<ffffffff811b4c79>] ? submit_bio+0x10a/0x13b
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606944] [<ffffffff8113ce89>] ? dio_bio_submit+0x68/0x88
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606947] [<ffffffff8113d115>] ? dio_send_cur_page+0x7d/0xa8
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606951] [<ffffffff8113d1e8>] ? submit_page_section+0xa8/0x112
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606954] [<ffffffff8113da99>] ? do_blockdev_direct_IO+0x7bb/0xae8
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606958] [<ffffffff8113aef1>] ? I_BDEV+0x8/0x8
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606961] [<ffffffff8113b0e8>] ? blkdev_direct_IO+0x4e/0x53
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606964] [<ffffffff8113aef1>] ? I_BDEV+0x8/0x8
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606969] [<ffffffff810c800a>] ? generic_file_direct_write+0xe3/0x14a
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606972] [<ffffffff810c818c>] ? __generic_file_aio_write+0x11b/0x1ff
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606976] [<ffffffff8113b617>] ? blkdev_aio_write+0x44/0x93
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606980] [<ffffffff81112038>] ? do_sync_readv_writev+0x50/0x76
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606983] [<ffffffff8113b5d3>] ? bd_may_claim+0x2c/0x2c
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606987] [<ffffffff811130a6>] ? do_readv_writev+0xbf/0x135
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606990] [<ffffffff8113b5d3>] ? bd_may_claim+0x2c/0x2c
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606993] [<ffffffff8111205e>] ? do_sync_readv_writev+0x76/0x76
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.606997] [<ffffffff81126eee>] ? fget_light+0x6b/0x7c
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.607000] [<ffffffff81111fbb>] ? fdget+0xe/0x17
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.607004] [<ffffffff811133fe>] ? SyS_pwritev+0x65/0xb0
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.607007] [<ffffffff8139ea69>] ? system_call_fastpath+0x16/0x1b
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.607010] INFO: task kvm:14306 blocked for more than 120 seconds.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.612040] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617441] kvm D ffff88207fa53f40 0 14306 1 0x00000000
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617445] ffff880eedbaa080 0000000000000082 0000000000011200 ffff881fe2d63850
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617451] 0000000000013f40 ffff881d8e5edfd8 ffff881d8e5edfd8 ffff880eedbaa080
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617451] 0000000000013f40 ffff881d8e5edfd8 ffff881d8e5edfd8 ffff880eedbaa080
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617456] ffffffff8139958c ffff881b5fa52800 ffff881d8e5ed820 ffff881b5fa52a90
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617460] Call Trace:
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617467] [<ffffffff8139958c>] ? _raw_spin_unlock_irqrestore+0xc/0xd
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617486] [<ffffffffa02efff0>] ? md_write_start+0x131/0x147 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617490] [<ffffffff81059c2f>] ? abort_exclusive_wait+0x79/0x79
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617509] [<ffffffffa05c2762>] ? make_request+0x37/0xa63 [raid1]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617513] [<ffffffff81399449>] ? _raw_read_lock_irqsave+0x21/0x2a
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617531] [<ffffffffa000679f>] ? __split_and_process_bio+0x40d/0x420 [dm_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617536] [<ffffffff81102005>] ? kmem_cache_alloc+0xe1/0x154
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617552] [<ffffffffa02f4b7e>] ? md_make_request+0xee/0x1df [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617559] [<ffffffffa0006902>] ? dm_request+0x150/0x163 [dm_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617563] [<ffffffff811b3efc>] ? generic_make_request+0x96/0xd5
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617573] [<ffffffff811b4c79>] ? submit_bio+0x10a/0x13b
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617577] [<ffffffff8113ce89>] ? dio_bio_submit+0x68/0x88
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617580] [<ffffffff8113dc35>] ? do_blockdev_direct_IO+0x957/0xae8
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617584] [<ffffffff8113aef1>] ? I_BDEV+0x8/0x8
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617587] [<ffffffff8113b0e8>] ? blkdev_direct_IO+0x4e/0x53
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617590] [<ffffffff8113aef1>] ? I_BDEV+0x8/0x8
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617594] [<ffffffff810c800a>] ? generic_file_direct_write+0xe3/0x14a
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617597] [<ffffffff810c818c>] ? __generic_file_aio_write+0x11b/0x1ff
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617601] [<ffffffff8113b617>] ? blkdev_aio_write+0x44/0x93
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617604] [<ffffffff811120b3>] ? do_sync_write+0x55/0x7c
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617608] [<ffffffff81112ab0>] ? vfs_write+0x9d/0x103
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617611] [<ffffffff81112eb9>] ? SyS_pwrite64+0x61/0x87
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617614] [<ffffffff8139ea69>] ? system_call_fastpath+0x16/0x1b
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.617629] INFO: task md71_raid1:14478 blocked for more than 120 seconds.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.622944] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628476] md71_raid1 D ffff88207fad3f40 0 14478 2 0x00000000
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628480] ffff883ed1a09040 0000000000000046 ffff883ed1a09040 ffff881fe2d68850
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628486] 0000000000013f40 ffff883fbd0b7fd8 ffff883fbd0b7fd8 ffff883ed1a09040
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628490] ffffffff8139958c ffff883fbd0b7c60 ffff881b5fa52800 ffff881b5fa52a90
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628498] Call Trace:
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628504] [<ffffffff8139958c>] ? _raw_spin_unlock_irqrestore+0xc/0xd
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628522] [<ffffffffa02f4d65>] ? md_super_wait+0x69/0x7f [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628526] [<ffffffff81059c2f>] ? abort_exclusive_wait+0x79/0x79
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628534] [<ffffffffa02f5131>] ? md_update_sb+0x3b6/0x4b8 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628542] [<ffffffffa02f59ee>] ? md_check_recovery+0x1c6/0x3d1 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628546] [<ffffffffa05c31cc>] ? raid1d+0x3e/0xb22 [raid1]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628550] [<ffffffff813988db>] ? __schedule+0x4e7/0x53d
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628553] [<ffffffff813978a3>] ? schedule_timeout+0x2c/0x123
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628557] [<ffffffff813995cb>] ? _raw_spin_lock_irqsave+0x14/0x35
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628560] [<ffffffff813995cb>] ? _raw_spin_lock_irqsave+0x14/0x35
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628568] [<ffffffffa02f02ed>] ? md_thread+0x114/0x132 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628571] [<ffffffff81059c2f>] ? abort_exclusive_wait+0x79/0x79
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628578] [<ffffffffa02f01d9>] ? signal_pending+0x10/0x10 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628585] [<ffffffffa02f01d9>] ? signal_pending+0x10/0x10 [md_mod]
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628588] [<ffffffff81059295>] ? kthread+0x81/0x89
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628591] [<ffffffff81059214>] ? __kthread_parkme+0x5d/0x5d
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628594] [<ffffffff8139e9bc>] ? ret_from_fork+0x7c/0xb0
Apr 12 19:33:47 10-120-202-67 kernel: [10636897.628597] [<ffffffff81059214>] ? __kthread_parkme+0x5d/0x5d
-------------
Zhiyong Xi
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox