€•*Œsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œtranslations”Œ LanguagesNode”“”)”}”(hhh]”(hŒpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ"/translations/zh_CN/admin-guide/md”Œmodname”NŒ classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ"/translations/zh_TW/admin-guide/md”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ"/translations/it_IT/admin-guide/md”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ"/translations/ja_JP/admin-guide/md”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ"/translations/ko_KR/admin-guide/md”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ"/translations/pt_BR/admin-guide/md”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ"/translations/sp_SP/admin-guide/md”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒRAID arrays”h]”hŒRAID arrays”…””}”(hh¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhh·h²hh³Œ,,,,dev0,dev1,...,devn”h]”hŒTmd=,,,,dev0,dev1,...,devn”…””}”hjHsbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1jFh³hÊh´KhhËh²hubhý)”}”(hŒ-for raid arrays with persistent superblocks::”h]”hŒ,for raid arrays with persistent superblocks:”…””}”(hjXh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´KhhËh²hubjG)”}”(hŒ%md=,dev0,dev1,...,devn”h]”hŒ%md=,dev0,dev1,...,devn”…””}”hjfsbah}”(h]”h ]”h"]”h$]”h&]”jVjWuh1jFh³hÊh´KhhËh²hubhý)”}”(hŒ'or, to assemble a partitionable array::”h]”hŒ&or, to assemble a partitionable array:”…””}”(hjth²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´KhhËh²hubjG)”}”(hŒ&md=d,dev0,dev1,...,devn”h]”hŒ&md=d,dev0,dev1,...,devn”…””}”hj‚sbah}”(h]”h ]”h"]”h$]”h&]”jVjWuh1jFh³hÊh´KhhËh²hubh¶)”}”(hhh]”(h»)”}”(hŒ``md device no.``”h]”hŒliteral”“”)”}”(hj•h]”hŒ md device no.”…””}”(hj™h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj“ubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjh²hh³hÊh´Kubhý)”}”(hŒThe number of the md device”h]”hŒThe number of the md device”…””}”(hj¬h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Khjh²hubhŒtable”“”)”}”(hhh]”hŒtgroup”“”)”}”(hhh]”(hŒcolspec”“”)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1jÄhjÁubjÅ)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”K uh1jÄhjÁubhŒthead”“”)”}”(hhh]”hŒrow”“”)”}”(hhh]”(hŒentry”“”)”}”(hhh]”hý)”}”(hŒ``md device no.``”h]”j˜)”}”(hjëh]”hŒ md device no.”…””}”(hjíh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjéubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K hjæubah}”(h]”h ]”h"]”h$]”h&]”uh1jähjáubjå)”}”(hhh]”hý)”}”(hŒdevice”h]”hŒdevice”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jähjáubeh}”(h]”h ]”h"]”h$]”h&]”uh1jßhjÜubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhjÁubhŒtbody”“”)”}”(hhh]”(jà)”}”(hhh]”(jå)”}”(hhh]”hý)”}”(hŒ0”h]”hŒ0”…””}”(hj4h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K"hj1ubah}”(h]”h ]”h"]”h$]”h&]”uh1jähj.ubjå)”}”(hhh]”hý)”}”(hŒmd0”h]”hŒmd0”…””}”(hjKh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K"hjHubah}”(h]”h ]”h"]”h$]”h&]”uh1jähj.ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jßhj+ubjà)”}”(hhh]”(jå)”}”(hhh]”hý)”}”(hŒ1”h]”hŒ1”…””}”(hjkh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K#hjhubah}”(h]”h ]”h"]”h$]”h&]”uh1jähjeubjå)”}”(hhh]”hý)”}”(hŒmd1”h]”hŒmd1”…””}”(hj‚h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K#hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jähjeubeh}”(h]”h ]”h"]”h$]”h&]”uh1jßhj+ubjà)”}”(hhh]”(jå)”}”(hhh]”hý)”}”(hŒ2”h]”hŒ2”…””}”(hj¢h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K$hjŸubah}”(h]”h ]”h"]”h$]”h&]”uh1jähjœubjå)”}”(hhh]”hý)”}”(hŒmd2”h]”hŒmd2”…””}”(hj¹h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K$hj¶ubah}”(h]”h ]”h"]”h$]”h&]”uh1jähjœubeh}”(h]”h ]”h"]”h$]”h&]”uh1jßhj+ubjà)”}”(hhh]”(jå)”}”(hhh]”hý)”}”(hŒ3”h]”hŒ3”…””}”(hjÙh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K%hjÖubah}”(h]”h ]”h"]”h$]”h&]”uh1jähjÓubjå)”}”(hhh]”hý)”}”(hŒmd3”h]”hŒmd3”…””}”(hjðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K%hjíubah}”(h]”h ]”h"]”h$]”h&]”uh1jähjÓubeh}”(h]”h ]”h"]”h$]”h&]”uh1jßhj+ubjà)”}”(hhh]”(jå)”}”(hhh]”hý)”}”(hŒ4”h]”hŒ4”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K&hj ubah}”(h]”h ]”h"]”h$]”h&]”uh1jähj ubjå)”}”(hhh]”hý)”}”(hŒmd4”h]”hŒmd4”…””}”(hj'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K&hj$ubah}”(h]”h ]”h"]”h$]”h&]”uh1jähj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jßhj+ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j)hjÁubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1j¿hj¼ubah}”(h]”h ]”h"]”h$]”h&]”uh1jºhjh²hh³hÊh´Nubeh}”(h]”Œmd-device-no”ah ]”h"]”Œ md device no.”ah$]”h&]”uh1hµhhËh²hh³hÊh´Kubh¶)”}”(hhh]”(h»)”}”(hŒ``raid level``”h]”j˜)”}”(hjah]”hŒ raid level”…””}”(hjch²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj_ubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj\h²hh³hÊh´K*ubhý)”}”(hŒlevel of the RAID array”h]”hŒlevel of the RAID array”…””}”(hjvh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K,hj\h²hubj»)”}”(hhh]”jÀ)”}”(hhh]”(jÅ)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1jÄhj‡ubjÅ)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”K uh1jÄhj‡ubjÛ)”}”(hhh]”jà)”}”(hhh]”(jå)”}”(hhh]”hý)”}”(hŒ``raid level``”h]”j˜)”}”(hj©h]”hŒ raid level”…””}”(hj«h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj§ubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K/hj¤ubah}”(h]”h ]”h"]”h$]”h&]”uh1jähj¡ubjå)”}”(hhh]”hý)”}”(hŒlevel”h]”hŒlevel”…””}”(hjÇh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K/hjÄubah}”(h]”h ]”h"]”h$]”h&]”uh1jähj¡ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jßhjžubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhj‡ubj*)”}”(hhh]”(jà)”}”(hhh]”(jå)”}”(hhh]”hý)”}”(hŒ-1”h]”hŒ-1”…””}”(hjðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K1hjíubah}”(h]”h ]”h"]”h$]”h&]”uh1jähjêubjå)”}”(hhh]”hý)”}”(hŒlinear mode”h]”hŒlinear mode”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K1hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jähjêubeh}”(h]”h ]”h"]”h$]”h&]”uh1jßhjçubjà)”}”(hhh]”(jå)”}”(hhh]”hý)”}”(hj6h]”hŒ0”…””}”(hj'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K2hj$ubah}”(h]”h ]”h"]”h$]”h&]”uh1jähj!ubjå)”}”(hhh]”hý)”}”(hŒstriped mode”h]”hŒstriped mode”…””}”(hj=h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K2hj:ubah}”(h]”h ]”h"]”h$]”h&]”uh1jähj!ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jßhjçubeh}”(h]”h ]”h"]”h$]”h&]”uh1j)hj‡ubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1j¿hj„ubah}”(h]”h ]”h"]”h$]”h&]”uh1jºhj\h²hh³hÊh´Nubhý)”}”(hŒ;other modes are only supported with persistent super blocks”h]”hŒ;other modes are only supported with persistent super blocks”…””}”(hjjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K5hj\h²hubeh}”(h]”Œ raid-level”ah ]”h"]”Œ raid level”ah$]”h&]”uh1hµhhËh²hh³hÊh´K*ubh¶)”}”(hhh]”(h»)”}”(hŒ``chunk size factor``”h]”j˜)”}”(hj…h]”hŒchunk size factor”…””}”(hj‡h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjƒubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj€h²hh³hÊh´K8ubhý)”}”(hŒ(raid-0 and raid-1 only)”h]”hŒ(raid-0 and raid-1 only)”…””}”(hjšh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K:hj€h²hubhý)”}”(hŒSet the chunk size as 4k << n.”h]”hŒSet the chunk size as 4k << n.”…””}”(hj¨h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K) looks like this::”h]”(hŒ'A possible loadlin line (Harald Hoyer <”…””}”(hjmh²hh³Nh´Nubj)”}”(hŒHarryH@Royal.Net”h]”hŒHarryH@Royal.Net”…””}”(hjuh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:HarryH@Royal.Net”uh1jhjmubhŒ>) looks like this:”…””}”(hjmh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´KHhjîh²hubjG)”}”(hŒLe:\loadlin\loadlin e:\zimage root=/dev/md0 md=0,0,4,0,/dev/hdb2,/dev/hdc3 ro”h]”hŒLe:\loadlin\loadlin e:\zimage root=/dev/md0 md=0,0,4,0,/dev/hdb2,/dev/hdc3 ro”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”jVjWuh1jFh³hÊh´KJhjîh²hubeh}”(h]”Œdev0-to-devn”ah ]”h"]”Œdev0 to devn”ah$]”h&]”uh1hµhhËh²hh³hÊh´KDubeh}”(h]”Œ!boot-time-assembly-of-raid-arrays”ah ]”h"]”Œ!boot time assembly of raid arrays”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kubh¶)”}”(hhh]”(h»)”}”(hŒ&Boot time autodetection of RAID arrays”h]”hŒ&Boot time autodetection of RAID arrays”…””}”(hj°h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjh²hh³hÊh´KNubhý)”}”(hX@When md is compiled into the kernel (not as module), partitions of type 0xfd are scanned and automatically assembled into RAID arrays. This autodetection may be suppressed with the kernel parameter ``raid=noautodetect``. As of kernel 2.6.9, only drives with a type 0 superblock can be autodetected and run at boot time.”h]”(hŒÆWhen md is compiled into the kernel (not as module), partitions of type 0xfd are scanned and automatically assembled into RAID arrays. This autodetection may be suppressed with the kernel parameter ”…””}”(hj¾h²hh³Nh´Nubj˜)”}”(hŒ``raid=noautodetect``”h]”hŒraid=noautodetect”…””}”(hjÆh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj¾ubhŒe. As of kernel 2.6.9, only drives with a type 0 superblock can be autodetected and run at boot time.”…””}”(hj¾h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´KPhjh²hubhý)”}”(hŒ‚The kernel parameter ``raid=partitionable`` (or ``raid=part``) means that all auto-detected arrays are assembled as partitionable.”h]”(hŒThe kernel parameter ”…””}”(hjÞh²hh³Nh´Nubj˜)”}”(hŒ``raid=partitionable``”h]”hŒraid=partitionable”…””}”(hjæh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjÞubhŒ (or ”…””}”(hjÞh²hh³Nh´Nubj˜)”}”(hŒ ``raid=part``”h]”hŒ raid=part”…””}”(hjøh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjÞubhŒE) means that all auto-detected arrays are assembled as partitionable.”…””}”(hjÞh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´KVhjh²hubeh}”(h]”Œ&boot-time-autodetection-of-raid-arrays”ah ]”h"]”Œ&boot time autodetection of raid arrays”ah$]”h&]”uh1hµhh·h²hh³hÊh´KNubh¶)”}”(hhh]”(h»)”}”(hŒ+Boot time assembly of degraded/dirty arrays”h]”hŒ+Boot time assembly of degraded/dirty arrays”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjh²hh³hÊh´KZubhý)”}”(hX:If a raid5 or raid6 array is both dirty and degraded, it could have undetectable data corruption. This is because the fact that it is ``dirty`` means that the parity cannot be trusted, and the fact that it is degraded means that some datablocks are missing and cannot reliably be reconstructed (due to no parity).”h]”(hŒ‡If a raid5 or raid6 array is both dirty and degraded, it could have undetectable data corruption. This is because the fact that it is ”…””}”(hj)h²hh³Nh´Nubj˜)”}”(hŒ ``dirty``”h]”hŒdirty”…””}”(hj1h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj)ubhŒª means that the parity cannot be trusted, and the fact that it is degraded means that some datablocks are missing and cannot reliably be reconstructed (due to no parity).”…””}”(hj)h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K\hjh²hubhý)”}”(hŒÄFor this reason, md will normally refuse to start such an array. This requires the sysadmin to take action to explicitly start the array despite possible corruption. This is normally done with::”h]”hŒÃFor this reason, md will normally refuse to start such an array. This requires the sysadmin to take action to explicitly start the array despite possible corruption. This is normally done with:”…””}”(hjIh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Kbhjh²hubjG)”}”(hŒmdadm --assemble --force ....”h]”hŒmdadm --assemble --force ....”…””}”hjWsbah}”(h]”h ]”h"]”h$]”h&]”jVjWuh1jFh³hÊh´Kfhjh²hubhý)”}”(hXThis option is not really available if the array has the root filesystem on it. In order to support this booting from such an array, md supports a module parameter ``start_dirty_degraded`` which, when set to 1, bypassed the checks and will allows dirty degraded arrays to be started.”h]”(hŒ¥This option is not really available if the array has the root filesystem on it. In order to support this booting from such an array, md supports a module parameter ”…””}”(hjeh²hh³Nh´Nubj˜)”}”(hŒ``start_dirty_degraded``”h]”hŒstart_dirty_degraded”…””}”(hjmh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjeubhŒ_ which, when set to 1, bypassed the checks and will allows dirty degraded arrays to be started.”…””}”(hjeh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Khhjh²hubhý)”}”(hŒISo, to boot with a root filesystem of a dirty degraded raid 5 or 6, use::”h]”hŒHSo, to boot with a root filesystem of a dirty degraded raid 5 or 6, use:”…””}”(hj…h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Knhjh²hubjG)”}”(hŒmd-mod.start_dirty_degraded=1”h]”hŒmd-mod.start_dirty_degraded=1”…””}”hj“sbah}”(h]”h ]”h"]”h$]”h&]”jVjWuh1jFh³hÊh´Kphjh²hubeh}”(h]”Œ+boot-time-assembly-of-degraded-dirty-arrays”ah ]”h"]”Œ+boot time assembly of degraded/dirty arrays”ah$]”h&]”uh1hµhh·h²hh³hÊh´KZubh¶)”}”(hhh]”(h»)”}”(hŒSuperblock formats”h]”hŒSuperblock formats”…””}”(hj¬h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj©h²hh³hÊh´Ktubhý)”}”(hŒ»The md driver can support a variety of different superblock formats. Currently, it supports superblock formats ``0.90.0`` and the ``md-1`` format introduced in the 2.5 development series.”h]”(hŒoThe md driver can support a variety of different superblock formats. Currently, it supports superblock formats ”…””}”(hjºh²hh³Nh´Nubj˜)”}”(hŒ ``0.90.0``”h]”hŒ0.90.0”…””}”(hjÂh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjºubhŒ and the ”…””}”(hjºh²hh³Nh´Nubj˜)”}”(hŒ``md-1``”h]”hŒmd-1”…””}”(hjÔh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjºubhŒ1 format introduced in the 2.5 development series.”…””}”(hjºh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Kvhj©h²hubhý)”}”(hŒAThe kernel will autodetect which format superblock is being used.”h]”hŒAThe kernel will autodetect which format superblock is being used.”…””}”(hjìh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Kzhj©h²hubhý)”}”(hŒsSuperblock format ``0`` is treated differently to others for legacy reasons - it is the original superblock format.”h]”(hŒSuperblock format ”…””}”(hjúh²hh³Nh´Nubj˜)”}”(hŒ``0``”h]”hŒ0”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjúubhŒ\ is treated differently to others for legacy reasons - it is the original superblock format.”…””}”(hjúh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K|hj©h²hubeh}”(h]”Œsuperblock-formats”ah ]”h"]”Œsuperblock formats”ah$]”h&]”uh1hµhh·h²hh³hÊh´Ktubh¶)”}”(hhh]”(h»)”}”(hŒ0General Rules - apply for all superblock formats”h]”hŒ0General Rules - apply for all superblock formats”…””}”(hj%h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj"h²hh³hÊh´Kubhý)”}”(hŒJAn array is ``created`` by writing appropriate superblocks to all devices.”h]”(hŒAn array is ”…””}”(hj3h²hh³Nh´Nubj˜)”}”(hŒ``created``”h]”hŒcreated”…””}”(hj;h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj3ubhŒ3 by writing appropriate superblocks to all devices.”…””}”(hj3h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Kƒhj"h²hubhý)”}”(hŒ”It is ``assembled`` by associating each of these devices with an particular md virtual device. Once it is completely assembled, it can be accessed.”h]”(hŒIt is ”…””}”(hjSh²hh³Nh´Nubj˜)”}”(hŒ ``assembled``”h]”hŒ assembled”…””}”(hj[h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjSubhŒ by associating each of these devices with an particular md virtual device. Once it is completely assembled, it can be accessed.”…””}”(hjSh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K†hj"h²hubhý)”}”(hXAn array should be created by a user-space tool. This will write superblocks to all devices. It will usually mark the array as ``unclean``, or with some devices missing so that the kernel md driver can create appropriate redundancy (copying in raid 1, parity calculation in raid 4/5).”h]”(hŒAn array should be created by a user-space tool. This will write superblocks to all devices. It will usually mark the array as ”…””}”(hjsh²hh³Nh´Nubj˜)”}”(hŒ``unclean``”h]”hŒunclean”…””}”(hj{h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjsubhŒ’, or with some devices missing so that the kernel md driver can create appropriate redundancy (copying in raid 1, parity calculation in raid 4/5).”…””}”(hjsh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´KŠhj"h²hubhý)”}”(hX`When an array is assembled, it is first initialized with the SET_ARRAY_INFO ioctl. This contains, in particular, a major and minor version number. The major version number selects which superblock format is to be used. The minor number might be used to tune handling of the format, such as suggesting where on each device to look for the superblock.”h]”hX`When an array is assembled, it is first initialized with the SET_ARRAY_INFO ioctl. This contains, in particular, a major and minor version number. The major version number selects which superblock format is to be used. The minor number might be used to tune handling of the format, such as suggesting where on each device to look for the superblock.”…””}”(hj“h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Khj"h²hubhý)”}”(hŒŽThen each device is added using the ADD_NEW_DISK ioctl. This provides, in particular, a major and minor number identifying the device to add.”h]”hŒŽThen each device is added using the ADD_NEW_DISK ioctl. This provides, in particular, a major and minor number identifying the device to add.”…””}”(hj¡h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K—hj"h²hubhý)”}”(hŒ.The array is started with the RUN_ARRAY ioctl.”h]”hŒ.The array is started with the RUN_ARRAY ioctl.”…””}”(hj¯h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K›hj"h²hubhý)”}”(hŒOnce started, new devices can be added. They should have an appropriate superblock written to them, and then be passed in with ADD_NEW_DISK.”h]”hŒOnce started, new devices can be added. They should have an appropriate superblock written to them, and then be passed in with ADD_NEW_DISK.”…””}”(hj½h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Khj"h²hubhý)”}”(hŒcDevices that have failed or are not yet active can be detached from an array using HOT_REMOVE_DISK.”h]”hŒcDevices that have failed or are not yet active can be detached from an array using HOT_REMOVE_DISK.”…””}”(hjËh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K¡hj"h²hubeh}”(h]”Œ.general-rules-apply-for-all-superblock-formats”ah ]”h"]”Œ0general rules - apply for all superblock formats”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kubh¶)”}”(hhh]”(h»)”}”(hŒhSpecific Rules that apply to format-0 super block arrays, and arrays with no superblock (non-persistent)”h]”hŒhSpecific Rules that apply to format-0 super block arrays, and arrays with no superblock (non-persistent)”…””}”(hjäh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjáh²hh³hÊh´K¦ubhý)”}”(hŒ£An array can be ``created`` by describing the array (level, chunksize etc) in a SET_ARRAY_INFO ioctl. This must have ``major_version==0`` and ``raid_disks != 0``.”h]”(hŒAn array can be ”…””}”(hjòh²hh³Nh´Nubj˜)”}”(hŒ``created``”h]”hŒcreated”…””}”(hjúh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjòubhŒ[ by describing the array (level, chunksize etc) in a SET_ARRAY_INFO ioctl. This must have ”…””}”(hjòh²hh³Nh´Nubj˜)”}”(hŒ``major_version==0``”h]”hŒmajor_version==0”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjòubhŒ and ”…””}”(hjòh²hh³Nh´Nubj˜)”}”(hŒ``raid_disks != 0``”h]”hŒraid_disks != 0”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjòubhŒ.”…””}”(hjòh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K¨hjáh²hubhý)”}”(hŒ Then uninitialized devices can be added with ADD_NEW_DISK. The structure passed to ADD_NEW_DISK must specify the state of the device and its role in the array.”h]”hŒ Then uninitialized devices can be added with ADD_NEW_DISK. The structure passed to ADD_NEW_DISK must specify the state of the device and its role in the array.”…””}”(hj6h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K¬hjáh²hubhý)”}”(hŒQOnce started with RUN_ARRAY, uninitialized spares can be added with HOT_ADD_DISK.”h]”hŒQOnce started with RUN_ARRAY, uninitialized spares can be added with HOT_ADD_DISK.”…””}”(hjDh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K°hjáh²hubeh}”(h]”Œespecific-rules-that-apply-to-format-0-super-block-arrays-and-arrays-with-no-superblock-non-persistent”ah ]”h"]”Œhspecific rules that apply to format-0 super block arrays, and arrays with no superblock (non-persistent)”ah$]”h&]”uh1hµhh·h²hh³hÊh´K¦ubh¶)”}”(hhh]”(h»)”}”(hŒMD devices in sysfs”h]”hŒMD devices in sysfs”…””}”(hj]h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjZh²hh³hÊh´Kµubhý)”}”(hŒFmd devices appear in sysfs (``/sys``) as regular block devices, e.g.::”h]”(hŒmd devices appear in sysfs (”…””}”(hjkh²hh³Nh´Nubj˜)”}”(hŒ``/sys``”h]”hŒ/sys”…””}”(hjsh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjkubhŒ!) as regular block devices, e.g.:”…””}”(hjkh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K·hjZh²hubjG)”}”(hŒ/sys/block/md0”h]”hŒ/sys/block/md0”…””}”hj‹sbah}”(h]”h ]”h"]”h$]”h&]”jVjWuh1jFh³hÊh´KºhjZh²hubhý)”}”(hŒ}Each ``md`` device will contain a subdirectory called ``md`` which contains further md-specific information about the device.”h]”(hŒEach ”…””}”(hj™h²hh³Nh´Nubj˜)”}”(hŒ``md``”h]”hŒmd”…””}”(hj¡h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj™ubhŒ+ device will contain a subdirectory called ”…””}”(hj™h²hh³Nh´Nubj˜)”}”(hŒ``md``”h]”hŒmd”…””}”(hj³h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj™ubhŒA which contains further md-specific information about the device.”…””}”(hj™h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K¼hjZh²hubhý)”}”(hŒAll md devices contain:”h]”hŒAll md devices contain:”…””}”(hjËh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K¿hjZh²hubhŒblock_quote”“”)”}”(hX½ level a text file indicating the ``raid level``. e.g. raid0, raid1, raid5, linear, multipath, faulty. If no raid level has been set yet (array is still being assembled), the value will reflect whatever has been written to it, which may be a name like the above, or may be a number such as ``0``, ``5``, etc. raid_disks a text file with a simple number indicating the number of devices in a fully functional array. If this is not yet known, the file will be empty. If an array is being resized this will contain the new number of devices. Some raid levels allow this value to be set while the array is active. This will reconfigure the array. Otherwise it can only be set while assembling an array. A change to this attribute will not be permitted if it would reduce the size of the array. To reduce the number of drives in an e.g. raid5, the array size must first be reduced by setting the ``array_size`` attribute. chunk_size This is the size in bytes for ``chunks`` and is only relevant to raid levels that involve striping (0,4,5,6,10). The address space of the array is conceptually divided into chunks and consecutive chunks are striped onto neighbouring devices. The size should be at least PAGE_SIZE (4k) and should be a power of 2. This can only be set while assembling an array layout The ``layout`` for the array for the particular level. This is simply a number that is interpreted differently by different levels. It can be written while assembling an array. array_size This can be used to artificially constrain the available space in the array to be less than is actually available on the combined devices. Writing a number (in Kilobytes) which is less than the available size will set the size. Any reconfiguration of the array (e.g. adding devices) will not cause the size to change. Writing the word ``default`` will cause the effective size of the array to be whatever size is actually available based on ``level``, ``chunk_size`` and ``component_size``. This can be used to reduce the size of the array before reducing the number of devices in a raid4/5/6, or to support external metadata formats which mandate such clipping. logical_block_size Configure the array's logical block size in bytes. This attribute is only supported for 1.x meta. Write the value before starting array. The final array LBS uses the maximum between this configuration and LBS of all combined devices. Note that LBS cannot exceed PAGE_SIZE before RAID supports folio. WARNING: Arrays created on new kernel cannot be assembled at old kernel due to padding check, Set module parameter 'check_new_feature' to false to bypass, but data loss may occur. reshape_position This is either ``none`` or a sector number within the devices of the array where ``reshape`` is up to. If this is set, the three attributes mentioned above (raid_disks, chunk_size, layout) can potentially have 2 values, an old and a new value. If these values differ, reading the attribute returns:: new (old) and writing will effect the ``new`` value, leaving the ``old`` unchanged. component_size For arrays with data redundancy (i.e. not raid0, linear, faulty, multipath), all components must be the same size - or at least there must a size that they all provide space for. This is a key part or the geometry of the array. It is measured in sectors and can be read from here. Writing to this value may resize the array if the personality supports it (raid1, raid5, raid6), and if the component drives are large enough. metadata_version This indicates the format that is being used to record metadata about the array. It can be 0.90 (traditional format), 1.0, 1.1, 1.2 (newer format in varying locations) or ``none`` indicating that the kernel isn't managing metadata at all. Alternately it can be ``external:`` followed by a string which is set by user-space. This indicates that metadata is managed by a user-space program. Any device failure or other event that requires a metadata update will cause array activity to be suspended until the event is acknowledged. resync_start The point at which resync should start. If no resync is needed, this will be a very large number (or ``none`` since 2.6.30-rc1). At array creation it will default to 0, though starting the array as ``clean`` will set it much larger. new_dev This file can be written but not read. The value written should be a block device number as major:minor. e.g. 8:0 This will cause that device to be attached to the array, if it is available. It will then appear at md/dev-XXX (depending on the name of the device) and further configuration is then possible. safe_mode_delay When an md array has seen no write requests for a certain period of time, it will be marked as ``clean``. When another write request arrives, the array is marked as ``dirty`` before the write commences. This is known as ``safe_mode``. The ``certain period`` is controlled by this file which stores the period as a number of seconds. The default is 200msec (0.200). Writing a value of 0 disables safemode. array_state This file contains a single word which describes the current state of the array. In many cases, the state can be set by writing the word for the desired state, however some states cannot be explicitly set, and some transitions are not allowed. Select/poll works on this file. All changes except between Active_idle and active (which can be frequent and are not very interesting) are notified. active->active_idle is reported if the metadata is externally managed. clear No devices, no size, no level Writing is equivalent to STOP_ARRAY ioctl inactive May have some settings, but array is not active all IO results in error When written, doesn't tear down array, but just stops it suspended (not supported yet) All IO requests will block. The array can be reconfigured. Writing this, if accepted, will block until array is quiescent readonly no resync can happen. no superblocks get written. Write requests fail read-auto like readonly, but behaves like ``clean`` on a write request. clean no pending writes, but otherwise active. When written to inactive array, starts without resync If a write request arrives then if metadata is known, mark ``dirty`` and switch to ``active``. if not known, block and switch to write-pending If written to an active array that has pending writes, then fails. active fully active: IO and resync can be happening. When written to inactive array, starts with resync write-pending clean, but writes are blocked waiting for ``active`` to be written. active-idle like active, but no writes have been seen for a while (safe_mode_delay). consistency_policy This indicates how the array maintains consistency in case of unexpected shutdown. It can be: none Array has no redundancy information, e.g. raid0, linear. resync Full resync is performed and all redundancy is regenerated when the array is started after unclean shutdown. bitmap Resync assisted by a write-intent bitmap. journal For raid4/5/6, journal device is used to log transactions and replay after unclean shutdown. ppl For raid5 only, Partial Parity Log is used to close the write hole and eliminate resync. The accepted values when writing to this file are ``ppl`` and ``resync``, used to enable and disable PPL. uuid This indicates the UUID of the array in the following format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx bitmap_type [RW] When read, this file will display the current and available bitmap for this array. The currently active bitmap will be enclosed in [] brackets. Writing an bitmap name or ID to this file will switch control of this array to that new bitmap. Note that writing a new bitmap for created array is forbidden. none No bitmap bitmap The default internal bitmap llbitmap The lockless internal bitmap ”h]”hÝ)”}”(hhh]”(hâ)”}”(hX4level a text file indicating the ``raid level``. e.g. raid0, raid1, raid5, linear, multipath, faulty. If no raid level has been set yet (array is still being assembled), the value will reflect whatever has been written to it, which may be a name like the above, or may be a number such as ``0``, ``5``, etc. ”h]”(hè)”}”(hŒlevel”h]”hŒlevel”…””}”(hjæh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´KÇhjâubhø)”}”(hhh]”hý)”}”(hX-a text file indicating the ``raid level``. e.g. raid0, raid1, raid5, linear, multipath, faulty. If no raid level has been set yet (array is still being assembled), the value will reflect whatever has been written to it, which may be a name like the above, or may be a number such as ``0``, ``5``, etc.”h]”(hŒa text file indicating the ”…””}”(hj÷h²hh³Nh´Nubj˜)”}”(hŒ``raid level``”h]”hŒ raid level”…””}”(hjÿh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj÷ubhŒò. e.g. raid0, raid1, raid5, linear, multipath, faulty. If no raid level has been set yet (array is still being assembled), the value will reflect whatever has been written to it, which may be a name like the above, or may be a number such as ”…””}”(hj÷h²hh³Nh´Nubj˜)”}”(hŒ``0``”h]”hŒ0”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj÷ubhŒ, ”…””}”(hj÷h²hh³Nh´Nubj˜)”}”(hŒ``5``”h]”hŒ5”…””}”(hj# h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj÷ubhŒ, etc.”…””}”(hj÷h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´KÂhjôubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjâubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´KÇhjßubhâ)”}”(hXfraid_disks a text file with a simple number indicating the number of devices in a fully functional array. If this is not yet known, the file will be empty. If an array is being resized this will contain the new number of devices. Some raid levels allow this value to be set while the array is active. This will reconfigure the array. Otherwise it can only be set while assembling an array. A change to this attribute will not be permitted if it would reduce the size of the array. To reduce the number of drives in an e.g. raid5, the array size must first be reduced by setting the ``array_size`` attribute. ”h]”(hè)”}”(hŒ raid_disks”h]”hŒ raid_disks”…””}”(hjK h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´KÔhjG ubhø)”}”(hhh]”hý)”}”(hXZa text file with a simple number indicating the number of devices in a fully functional array. If this is not yet known, the file will be empty. If an array is being resized this will contain the new number of devices. Some raid levels allow this value to be set while the array is active. This will reconfigure the array. Otherwise it can only be set while assembling an array. A change to this attribute will not be permitted if it would reduce the size of the array. To reduce the number of drives in an e.g. raid5, the array size must first be reduced by setting the ``array_size`` attribute.”h]”(hXAa text file with a simple number indicating the number of devices in a fully functional array. If this is not yet known, the file will be empty. If an array is being resized this will contain the new number of devices. Some raid levels allow this value to be set while the array is active. This will reconfigure the array. Otherwise it can only be set while assembling an array. A change to this attribute will not be permitted if it would reduce the size of the array. To reduce the number of drives in an e.g. raid5, the array size must first be reduced by setting the ”…””}”(hj\ h²hh³Nh´Nubj˜)”}”(hŒ``array_size``”h]”hŒ array_size”…””}”(hjd h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj\ ubhŒ attribute.”…””}”(hj\ h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´KÊhjY ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjG ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´KÔhjßubhâ)”}”(hXtchunk_size This is the size in bytes for ``chunks`` and is only relevant to raid levels that involve striping (0,4,5,6,10). The address space of the array is conceptually divided into chunks and consecutive chunks are striped onto neighbouring devices. The size should be at least PAGE_SIZE (4k) and should be a power of 2. This can only be set while assembling an array ”h]”(hè)”}”(hŒ chunk_size”h]”hŒ chunk_size”…””}”(hjŒ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´KÜhjˆ ubhø)”}”(hhh]”hý)”}”(hXhThis is the size in bytes for ``chunks`` and is only relevant to raid levels that involve striping (0,4,5,6,10). The address space of the array is conceptually divided into chunks and consecutive chunks are striped onto neighbouring devices. The size should be at least PAGE_SIZE (4k) and should be a power of 2. This can only be set while assembling an array”h]”(hŒThis is the size in bytes for ”…””}”(hj h²hh³Nh´Nubj˜)”}”(hŒ ``chunks``”h]”hŒchunks”…””}”(hj¥ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj ubhX@ and is only relevant to raid levels that involve striping (0,4,5,6,10). The address space of the array is conceptually divided into chunks and consecutive chunks are striped onto neighbouring devices. The size should be at least PAGE_SIZE (4k) and should be a power of 2. This can only be set while assembling an array”…””}”(hj h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´K×hjš ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjˆ ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´KÜhjßubhâ)”}”(hŒºlayout The ``layout`` for the array for the particular level. This is simply a number that is interpreted differently by different levels. It can be written while assembling an array. ”h]”(hè)”}”(hŒlayout”h]”hŒlayout”…””}”(hjÍ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´KáhjÉ ubhø)”}”(hhh]”hý)”}”(hŒ²The ``layout`` for the array for the particular level. This is simply a number that is interpreted differently by different levels. It can be written while assembling an array.”h]”(hŒThe ”…””}”(hjÞ h²hh³Nh´Nubj˜)”}”(hŒ ``layout``”h]”hŒlayout”…””}”(hjæ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjÞ ubhŒ¤ for the array for the particular level. This is simply a number that is interpreted differently by different levels. It can be written while assembling an array.”…””}”(hjÞ h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´KßhjÛ ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjÉ ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Káhjßubhâ)”}”(hX¥array_size This can be used to artificially constrain the available space in the array to be less than is actually available on the combined devices. Writing a number (in Kilobytes) which is less than the available size will set the size. Any reconfiguration of the array (e.g. adding devices) will not cause the size to change. Writing the word ``default`` will cause the effective size of the array to be whatever size is actually available based on ``level``, ``chunk_size`` and ``component_size``. This can be used to reduce the size of the array before reducing the number of devices in a raid4/5/6, or to support external metadata formats which mandate such clipping. ”h]”(hè)”}”(hŒ array_size”h]”hŒ array_size”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Kïhj ubhø)”}”(hhh]”(hý)”}”(hXìThis can be used to artificially constrain the available space in the array to be less than is actually available on the combined devices. Writing a number (in Kilobytes) which is less than the available size will set the size. Any reconfiguration of the array (e.g. adding devices) will not cause the size to change. Writing the word ``default`` will cause the effective size of the array to be whatever size is actually available based on ``level``, ``chunk_size`` and ``component_size``.”h]”(hXQThis can be used to artificially constrain the available space in the array to be less than is actually available on the combined devices. Writing a number (in Kilobytes) which is less than the available size will set the size. Any reconfiguration of the array (e.g. adding devices) will not cause the size to change. Writing the word ”…””}”(hj h²hh³Nh´Nubj˜)”}”(hŒ``default``”h]”hŒdefault”…””}”(hj' h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj ubhŒ_ will cause the effective size of the array to be whatever size is actually available based on ”…””}”(hj h²hh³Nh´Nubj˜)”}”(hŒ ``level``”h]”hŒlevel”…””}”(hj9 h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj ubhŒ, ”…””}”(hj h²hh³Nh´Nubj˜)”}”(hŒ``chunk_size``”h]”hŒ chunk_size”…””}”(hjK h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj ubhŒ and ”…””}”(hj h²hh³Nh´Nubj˜)”}”(hŒ``component_size``”h]”hŒcomponent_size”…””}”(hj] h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj ubhŒ.”…””}”(hj h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Kähj ubhý)”}”(hŒ«This can be used to reduce the size of the array before reducing the number of devices in a raid4/5/6, or to support external metadata formats which mandate such clipping.”h]”hŒ«This can be used to reduce the size of the array before reducing the number of devices in a raid4/5/6, or to support external metadata formats which mandate such clipping.”…””}”(hju h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Kíhj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Kïhjßubhâ)”}”(hXólogical_block_size Configure the array's logical block size in bytes. This attribute is only supported for 1.x meta. Write the value before starting array. The final array LBS uses the maximum between this configuration and LBS of all combined devices. Note that LBS cannot exceed PAGE_SIZE before RAID supports folio. WARNING: Arrays created on new kernel cannot be assembled at old kernel due to padding check, Set module parameter 'check_new_feature' to false to bypass, but data loss may occur. ”h]”(hè)”}”(hŒlogical_block_size”h]”hŒlogical_block_size”…””}”(hj“ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Kùhj ubhø)”}”(hhh]”hý)”}”(hXßConfigure the array's logical block size in bytes. This attribute is only supported for 1.x meta. Write the value before starting array. The final array LBS uses the maximum between this configuration and LBS of all combined devices. Note that LBS cannot exceed PAGE_SIZE before RAID supports folio. WARNING: Arrays created on new kernel cannot be assembled at old kernel due to padding check, Set module parameter 'check_new_feature' to false to bypass, but data loss may occur.”h]”hXåConfigure the arrayâ€™s logical block size in bytes. This attribute is only supported for 1.x meta. Write the value before starting array. The final array LBS uses the maximum between this configuration and LBS of all combined devices. Note that LBS cannot exceed PAGE_SIZE before RAID supports folio. WARNING: Arrays created on new kernel cannot be assembled at old kernel due to padding check, Set module parameter â€˜check_new_featureâ€™ to false to bypass, but data loss may occur.”…””}”(hj¤ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Kòhj¡ ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Kùhjßubhâ)”}”(hX˜reshape_position This is either ``none`` or a sector number within the devices of the array where ``reshape`` is up to. If this is set, the three attributes mentioned above (raid_disks, chunk_size, layout) can potentially have 2 values, an old and a new value. If these values differ, reading the attribute returns:: new (old) and writing will effect the ``new`` value, leaving the ``old`` unchanged. ”h]”(hè)”}”(hŒreshape_position”h]”hŒreshape_position”…””}”(hjÂ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mhj¾ ubhø)”}”(hhh]”(hý)”}”(hX-This is either ``none`` or a sector number within the devices of the array where ``reshape`` is up to. If this is set, the three attributes mentioned above (raid_disks, chunk_size, layout) can potentially have 2 values, an old and a new value. If these values differ, reading the attribute returns::”h]”(hŒThis is either ”…””}”(hjÓ h²hh³Nh´Nubj˜)”}”(hŒ``none``”h]”hŒnone”…””}”(hjÛ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjÓ ubhŒ: or a sector number within the devices of the array where ”…””}”(hjÓ h²hh³Nh´Nubj˜)”}”(hŒ``reshape``”h]”hŒreshape”…””}”(hjí h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjÓ ubhŒÐ is up to. If this is set, the three attributes mentioned above (raid_disks, chunk_size, layout) can potentially have 2 values, an old and a new value. If these values differ, reading the attribute returns:”…””}”(hjÓ h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´KühjÐ ubjG)”}”(hŒ new (old)”h]”hŒ new (old)”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”jVjWuh1jFh³hÊh´MhjÐ ubhý)”}”(hŒIand writing will effect the ``new`` value, leaving the ``old`` unchanged.”h]”(hŒand writing will effect the ”…””}”(hjh²hh³Nh´Nubj˜)”}”(hŒ``new``”h]”hŒnew”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjubhŒ value, leaving the ”…””}”(hjh²hh³Nh´Nubj˜)”}”(hŒ``old``”h]”hŒold”…””}”(hj-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjubhŒ unchanged.”…””}”(hjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MhjÐ ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj¾ ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhjßubhâ)”}”(hXºcomponent_size For arrays with data redundancy (i.e. not raid0, linear, faulty, multipath), all components must be the same size - or at least there must a size that they all provide space for. This is a key part or the geometry of the array. It is measured in sectors and can be read from here. Writing to this value may resize the array if the personality supports it (raid1, raid5, raid6), and if the component drives are large enough. ”h]”(hè)”}”(hŒcomponent_size”h]”hŒcomponent_size”…””}”(hjUh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MhjQubhø)”}”(hhh]”hý)”}”(hXªFor arrays with data redundancy (i.e. not raid0, linear, faulty, multipath), all components must be the same size - or at least there must a size that they all provide space for. This is a key part or the geometry of the array. It is measured in sectors and can be read from here. Writing to this value may resize the array if the personality supports it (raid1, raid5, raid6), and if the component drives are large enough.”h]”hXªFor arrays with data redundancy (i.e. not raid0, linear, faulty, multipath), all components must be the same size - or at least there must a size that they all provide space for. This is a key part or the geometry of the array. It is measured in sectors and can be read from here. Writing to this value may resize the array if the personality supports it (raid1, raid5, raid6), and if the component drives are large enough.”…””}”(hjfh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mhjcubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjQubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhjßubhâ)”}”(hX&metadata_version This indicates the format that is being used to record metadata about the array. It can be 0.90 (traditional format), 1.0, 1.1, 1.2 (newer format in varying locations) or ``none`` indicating that the kernel isn't managing metadata at all. Alternately it can be ``external:`` followed by a string which is set by user-space. This indicates that metadata is managed by a user-space program. Any device failure or other event that requires a metadata update will cause array activity to be suspended until the event is acknowledged. ”h]”(hè)”}”(hŒmetadata_version”h]”hŒmetadata_version”…””}”(hj„h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mhj€ubhø)”}”(hhh]”hý)”}”(hXThis indicates the format that is being used to record metadata about the array. It can be 0.90 (traditional format), 1.0, 1.1, 1.2 (newer format in varying locations) or ``none`` indicating that the kernel isn't managing metadata at all. Alternately it can be ``external:`` followed by a string which is set by user-space. This indicates that metadata is managed by a user-space program. Any device failure or other event that requires a metadata update will cause array activity to be suspended until the event is acknowledged.”h]”(hŒ¬This indicates the format that is being used to record metadata about the array. It can be 0.90 (traditional format), 1.0, 1.1, 1.2 (newer format in varying locations) or ”…””}”(hj•h²hh³Nh´Nubj˜)”}”(hŒ``none``”h]”hŒnone”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj•ubhŒT indicating that the kernel isnâ€™t managing metadata at all. Alternately it can be ”…””}”(hj•h²hh³Nh´Nubj˜)”}”(hŒ ``external:``”h]”hŒ external:”…””}”(hj¯h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj•ubhX followed by a string which is set by user-space. This indicates that metadata is managed by a user-space program. Any device failure or other event that requires a metadata update will cause array activity to be suspended until the event is acknowledged.”…””}”(hj•h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mhj’ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj€ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhjßubhâ)”}”(hŒøresync_start The point at which resync should start. If no resync is needed, this will be a very large number (or ``none`` since 2.6.30-rc1). At array creation it will default to 0, though starting the array as ``clean`` will set it much larger. ”h]”(hè)”}”(hŒresync_start”h]”hŒresync_start”…””}”(hj×h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MhjÓubhø)”}”(hhh]”hý)”}”(hŒêThe point at which resync should start. If no resync is needed, this will be a very large number (or ``none`` since 2.6.30-rc1). At array creation it will default to 0, though starting the array as ``clean`` will set it much larger.”h]”(hŒfThe point at which resync should start. If no resync is needed, this will be a very large number (or ”…””}”(hjèh²hh³Nh´Nubj˜)”}”(hŒ``none``”h]”hŒnone”…””}”(hjðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjèubhŒZ since 2.6.30-rc1). At array creation it will default to 0, though starting the array as ”…””}”(hjèh²hh³Nh´Nubj˜)”}”(hŒ ``clean``”h]”hŒclean”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjèubhŒ will set it much larger.”…””}”(hjèh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mhjåubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjÓubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhjßubhâ)”}”(hX>new_dev This file can be written but not read. The value written should be a block device number as major:minor. e.g. 8:0 This will cause that device to be attached to the array, if it is available. It will then appear at md/dev-XXX (depending on the name of the device) and further configuration is then possible. ”h]”(hè)”}”(hŒnew_dev”h]”hŒnew_dev”…””}”(hj*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M&hj&ubhø)”}”(hhh]”hý)”}”(hX5This file can be written but not read. The value written should be a block device number as major:minor. e.g. 8:0 This will cause that device to be attached to the array, if it is available. It will then appear at md/dev-XXX (depending on the name of the device) and further configuration is then possible.”h]”hX5This file can be written but not read. The value written should be a block device number as major:minor. e.g. 8:0 This will cause that device to be attached to the array, if it is available. It will then appear at md/dev-XXX (depending on the name of the device) and further configuration is then possible.”…””}”(hj;h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M"hj8ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj&ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M&hjßubhâ)”}”(hX¨safe_mode_delay When an md array has seen no write requests for a certain period of time, it will be marked as ``clean``. When another write request arrives, the array is marked as ``dirty`` before the write commences. This is known as ``safe_mode``. The ``certain period`` is controlled by this file which stores the period as a number of seconds. The default is 200msec (0.200). Writing a value of 0 disables safemode. ”h]”(hè)”}”(hŒsafe_mode_delay”h]”hŒsafe_mode_delay”…””}”(hjYh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M/hjUubhø)”}”(hhh]”hý)”}”(hX—When an md array has seen no write requests for a certain period of time, it will be marked as ``clean``. When another write request arrives, the array is marked as ``dirty`` before the write commences. This is known as ``safe_mode``. The ``certain period`` is controlled by this file which stores the period as a number of seconds. The default is 200msec (0.200). Writing a value of 0 disables safemode.”h]”(hŒ_When an md array has seen no write requests for a certain period of time, it will be marked as ”…””}”(hjjh²hh³Nh´Nubj˜)”}”(hŒ ``clean``”h]”hŒclean”…””}”(hjrh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjjubhŒ>. When another write request arrives, the array is marked as ”…””}”(hjjh²hh³Nh´Nubj˜)”}”(hŒ ``dirty``”h]”hŒdirty”…””}”(hj„h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjjubhŒ/ before the write commences. This is known as ”…””}”(hjjh²hh³Nh´Nubj˜)”}”(hŒ ``safe_mode``”h]”hŒ safe_mode”…””}”(hj–h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjjubhŒ. The ”…””}”(hjjh²hh³Nh´Nubj˜)”}”(hŒ``certain period``”h]”hŒcertain period”…””}”(hj¨h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjjubhŒ” is controlled by this file which stores the period as a number of seconds. The default is 200msec (0.200). Writing a value of 0 disables safemode.”…””}”(hjjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M)hjgubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjUubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M/hjßubhâ)”}”(hXarray_state This file contains a single word which describes the current state of the array. In many cases, the state can be set by writing the word for the desired state, however some states cannot be explicitly set, and some transitions are not allowed. Select/poll works on this file. All changes except between Active_idle and active (which can be frequent and are not very interesting) are notified. active->active_idle is reported if the metadata is externally managed. clear No devices, no size, no level Writing is equivalent to STOP_ARRAY ioctl inactive May have some settings, but array is not active all IO results in error When written, doesn't tear down array, but just stops it suspended (not supported yet) All IO requests will block. The array can be reconfigured. Writing this, if accepted, will block until array is quiescent readonly no resync can happen. no superblocks get written. Write requests fail read-auto like readonly, but behaves like ``clean`` on a write request. clean no pending writes, but otherwise active. When written to inactive array, starts without resync If a write request arrives then if metadata is known, mark ``dirty`` and switch to ``active``. if not known, block and switch to write-pending If written to an active array that has pending writes, then fails. active fully active: IO and resync can be happening. When written to inactive array, starts with resync write-pending clean, but writes are blocked waiting for ``active`` to be written. active-idle like active, but no writes have been seen for a while (safe_mode_delay). ”h]”(hè)”}”(hŒarray_state”h]”hŒarray_state”…””}”(hjÐh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MfhjÌubhø)”}”(hhh]”(hý)”}”(hŒôThis file contains a single word which describes the current state of the array. In many cases, the state can be set by writing the word for the desired state, however some states cannot be explicitly set, and some transitions are not allowed.”h]”hŒôThis file contains a single word which describes the current state of the array. In many cases, the state can be set by writing the word for the desired state, however some states cannot be explicitly set, and some transitions are not allowed.”…””}”(hjáh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M2hjÞubhý)”}”(hŒÝSelect/poll works on this file. All changes except between Active_idle and active (which can be frequent and are not very interesting) are notified. active->active_idle is reported if the metadata is externally managed.”h]”hŒÝSelect/poll works on this file. All changes except between Active_idle and active (which can be frequent and are not very interesting) are notified. active->active_idle is reported if the metadata is externally managed.”…””}”(hjïh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M7hjÞubhÝ)”}”(hhh]”(hâ)”}”(hŒOclear No devices, no size, no level Writing is equivalent to STOP_ARRAY ioctl ”h]”(hè)”}”(hŒclear”h]”hŒclear”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M?hj ubhø)”}”(hhh]”(hý)”}”(hŒNo devices, no size, no level”h]”hŒNo devices, no size, no level”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M=hj ubhý)”}”(hŒ)Writing is equivalent to STOP_ARRAY ioctl”h]”hŒ)Writing is equivalent to STOP_ARRAY ioctl”…””}”(hj# h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M?hj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M?hjýubhâ)”}”(hŒ‹inactive May have some settings, but array is not active all IO results in error When written, doesn't tear down array, but just stops it ”h]”(hè)”}”(hŒinactive”h]”hŒinactive”…””}”(hjA h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MEhj= ubhø)”}”(hhh]”(hý)”}”(hŒGMay have some settings, but array is not active all IO results in error”h]”hŒGMay have some settings, but array is not active all IO results in error”…””}”(hjR h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MBhjO ubhý)”}”(hŒ8When written, doesn't tear down array, but just stops it”h]”hŒ:When written, doesnâ€™t tear down array, but just stops it”…””}”(hj` h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MEhjO ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj= ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MEhjýubhâ)”}”(hŒ™suspended (not supported yet) All IO requests will block. The array can be reconfigured. Writing this, if accepted, will block until array is quiescent ”h]”(hè)”}”(hŒsuspended (not supported yet)”h]”hŒsuspended (not supported yet)”…””}”(hj~ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MJhjz ubhø)”}”(hhh]”(hý)”}”(hŒ:All IO requests will block. The array can be reconfigured.”h]”hŒ:All IO requests will block. The array can be reconfigured.”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MHhjŒ ubhý)”}”(hŒ>Writing this, if accepted, will block until array is quiescent”h]”hŒ>Writing this, if accepted, will block until array is quiescent”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MJhjŒ ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjz ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MJhjýubhâ)”}”(hŒQreadonly no resync can happen. no superblocks get written. Write requests fail ”h]”(hè)”}”(hŒreadonly”h]”hŒreadonly”…””}”(hj» h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MOhj· ubhø)”}”(hhh]”(hý)”}”(hŒ2no resync can happen. no superblocks get written.”h]”hŒ2no resync can happen. no superblocks get written.”…””}”(hjÌ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MMhjÉ ubhý)”}”(hŒWrite requests fail”h]”hŒWrite requests fail”…””}”(hjÚ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MOhjÉ ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj· ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MOhjýubhâ)”}”(hŒHread-auto like readonly, but behaves like ``clean`` on a write request. ”h]”(hè)”}”(hŒ read-auto”h]”hŒ read-auto”…””}”(hjø h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MRhjô ubhø)”}”(hhh]”hý)”}”(hŒ=like readonly, but behaves like ``clean`` on a write request.”h]”(hŒ like readonly, but behaves like ”…””}”(hj h²hh³Nh´Nubj˜)”}”(hŒ ``clean``”h]”hŒclean”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj ubhŒ on a write request.”…””}”(hj h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MRhjubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjô ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MRhjýubhâ)”}”(hX9clean no pending writes, but otherwise active. When written to inactive array, starts without resync If a write request arrives then if metadata is known, mark ``dirty`` and switch to ``active``. if not known, block and switch to write-pending If written to an active array that has pending writes, then fails.”h]”(hè)”}”(hŒclean”h]”hŒclean”…””}”(hj9h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M\hj5ubhø)”}”(hhh]”(hý)”}”(hŒ(no pending writes, but otherwise active.”h]”hŒ(no pending writes, but otherwise active.”…””}”(hjJh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MUhjGubhý)”}”(hŒ5When written to inactive array, starts without resync”h]”hŒ5When written to inactive array, starts without resync”…””}”(hjXh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MWhjGubhý)”}”(hŒŽIf a write request arrives then if metadata is known, mark ``dirty`` and switch to ``active``. if not known, block and switch to write-pending”h]”(hŒ;If a write request arrives then if metadata is known, mark ”…””•¡}”(hjfh²hh³Nh´Nubj˜)”}”(hŒ ``dirty``”h]”hŒdirty”…””}”(hjnh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjfubhŒ and switch to ”…””}”(hjfh²hh³Nh´Nubj˜)”}”(hŒ ``active``”h]”hŒactive”…””}”(hj€h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjfubhŒ1. if not known, block and switch to write-pending”…””}”(hjfh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MYhjGubhý)”}”(hŒBIf written to an active array that has pending writes, then fails.”h]”hŒBIf written to an active array that has pending writes, then fails.”…””}”(hj˜h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M]hjGubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj5ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M\hjýubhâ)”}”(hŒhactive fully active: IO and resync can be happening. When written to inactive array, starts with resync ”h]”(hè)”}”(hŒactive”h]”hŒactive”…””}”(hj¶h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M`hj²ubhø)”}”(hhh]”hý)”}”(hŒ`fully active: IO and resync can be happening. When written to inactive array, starts with resync”h]”hŒ`fully active: IO and resync can be happening. When written to inactive array, starts with resync”…””}”(hjÇh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M_hjÄubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj²ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M`hjýubhâ)”}”(hŒRwrite-pending clean, but writes are blocked waiting for ``active`` to be written. ”h]”(hè)”}”(hŒ write-pending”h]”hŒ write-pending”…””}”(hjåh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mchjáubhø)”}”(hhh]”hý)”}”(hŒCclean, but writes are blocked waiting for ``active`` to be written.”h]”(hŒ*clean, but writes are blocked waiting for ”…””}”(hjöh²hh³Nh´Nubj˜)”}”(hŒ ``active``”h]”hŒactive”…””}”(hjþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjöubhŒ to be written.”…””}”(hjöh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mchjóubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjáubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mchjýubhâ)”}”(hŒUactive-idle like active, but no writes have been seen for a while (safe_mode_delay). ”h]”(hè)”}”(hŒactive-idle”h]”hŒactive-idle”…””}”(hj&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mfhj"ubhø)”}”(hhh]”hý)”}”(hŒHlike active, but no writes have been seen for a while (safe_mode_delay).”h]”hŒHlike active, but no writes have been seen for a while (safe_mode_delay).”…””}”(hj7h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mfhj4ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj"ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mfhjýubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhjÞubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjÌubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mfhjßubhâ)”}”(hX–consistency_policy This indicates how the array maintains consistency in case of unexpected shutdown. It can be: none Array has no redundancy information, e.g. raid0, linear. resync Full resync is performed and all redundancy is regenerated when the array is started after unclean shutdown. bitmap Resync assisted by a write-intent bitmap. journal For raid4/5/6, journal device is used to log transactions and replay after unclean shutdown. ppl For raid5 only, Partial Parity Log is used to close the write hole and eliminate resync. The accepted values when writing to this file are ``ppl`` and ``resync``, used to enable and disable PPL. ”h]”(hè)”}”(hŒconsistency_policy”h]”hŒconsistency_policy”…””}”(hjgh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mhjcubhø)”}”(hhh]”(hý)”}”(hŒ]This indicates how the array maintains consistency in case of unexpected shutdown. It can be:”h]”hŒ]This indicates how the array maintains consistency in case of unexpected shutdown. It can be:”…””}”(hjxh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MihjuubhÝ)”}”(hhh]”(hâ)”}”(hŒ>none Array has no redundancy information, e.g. raid0, linear. ”h]”(hè)”}”(hŒnone”h]”hŒnone”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mmhj‰ubhø)”}”(hhh]”hý)”}”(hŒ8Array has no redundancy information, e.g. raid0, linear.”h]”hŒ8Array has no redundancy information, e.g. raid0, linear.”…””}”(hjžh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mmhj›ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj‰ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mmhj†ubhâ)”}”(hŒtresync Full resync is performed and all redundancy is regenerated when the array is started after unclean shutdown. ”h]”(hè)”}”(hŒresync”h]”hŒresync”…””}”(hj¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mqhj¸ubhø)”}”(hhh]”hý)”}”(hŒlFull resync is performed and all redundancy is regenerated when the array is started after unclean shutdown.”h]”hŒlFull resync is performed and all redundancy is regenerated when the array is started after unclean shutdown.”…””}”(hjÍh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MphjÊubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj¸ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mqhj†ubhâ)”}”(hŒ1bitmap Resync assisted by a write-intent bitmap. ”h]”(hè)”}”(hŒbitmap”h]”hŒbitmap”…””}”(hjëh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mthjçubhø)”}”(hhh]”hý)”}”(hŒ)Resync assisted by a write-intent bitmap.”h]”hŒ)Resync assisted by a write-intent bitmap.”…””}”(hjüh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mthjùubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjçubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mthj†ubhâ)”}”(hŒejournal For raid4/5/6, journal device is used to log transactions and replay after unclean shutdown. ”h]”(hè)”}”(hŒjournal”h]”hŒjournal”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mxhjubhø)”}”(hhh]”hý)”}”(hŒ\For raid4/5/6, journal device is used to log transactions and replay after unclean shutdown.”h]”hŒ\For raid4/5/6, journal device is used to log transactions and replay after unclean shutdown.”…””}”(hj+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mwhj(ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mxhj†ubhâ)”}”(hŒ]ppl For raid5 only, Partial Parity Log is used to close the write hole and eliminate resync. ”h]”(hè)”}”(hŒppl”h]”hŒppl”…””}”(hjIh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M|hjEubhø)”}”(hhh]”hý)”}”(hŒXFor raid5 only, Partial Parity Log is used to close the write hole and eliminate resync.”h]”hŒXFor raid5 only, Partial Parity Log is used to close the write hole and eliminate resync.”…””}”(hjZh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M{hjWubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjEubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M|hj†ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhjuubhý)”}”(hŒiThe accepted values when writing to this file are ``ppl`` and ``resync``, used to enable and disable PPL.”h]”(hŒ2The accepted values when writing to this file are ”…””}”(hjzh²hh³Nh´Nubj˜)”}”(hŒ``ppl``”h]”hŒppl”…””}”(hj‚h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjzubhŒ and ”…””}”(hjzh²hh³Nh´Nubj˜)”}”(hŒ ``resync``”h]”hŒresync”…””}”(hj”h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjzubhŒ!, used to enable and disable PPL.”…””}”(hjzh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M~hjuubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjcubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhjßubhâ)”}”(hŒhuuid This indicates the UUID of the array in the following format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx ”h]”(hè)”}”(hŒuuid”h]”hŒuuid”…””}”(hj¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mƒhj¸ubhø)”}”(hhh]”hý)”}”(hŒbThis indicates the UUID of the array in the following format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”h]”hŒbThis indicates the UUID of the array in the following format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”…””}”(hjÍh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M‚hjÊubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj¸ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mƒhjßubhâ)”}”(hX¥bitmap_type [RW] When read, this file will display the current and available bitmap for this array. The currently active bitmap will be enclosed in [] brackets. Writing an bitmap name or ID to this file will switch control of this array to that new bitmap. Note that writing a new bitmap for created array is forbidden. none No bitmap bitmap The default internal bitmap llbitmap The lockless internal bitmap ”h]”(hè)”}”(hŒbitmap_type”h]”hŒbitmap_type”…””}”(hjëh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M‘hjçubhø)”}”(hhh]”(hý)”}”(hX3[RW] When read, this file will display the current and available bitmap for this array. The currently active bitmap will be enclosed in [] brackets. Writing an bitmap name or ID to this file will switch control of this array to that new bitmap. Note that writing a new bitmap for created array is forbidden.”h]”hX3[RW] When read, this file will display the current and available bitmap for this array. The currently active bitmap will be enclosed in [] brackets. Writing an bitmap name or ID to this file will switch control of this array to that new bitmap. Note that writing a new bitmap for created array is forbidden.”…””}”(hjüh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M†hjùubhÝ)”}”(hhh]”(hâ)”}”(hŒnone No bitmap”h]”(hè)”}”(hŒnone”h]”hŒnone”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MŒhj ubhø)”}”(hhh]”hý)”}”(hŒ No bitmap”h]”hŒ No bitmap”…””}”(hj"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mhjubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MŒhj ubhâ)”}”(hŒ"bitmap The default internal bitmap”h]”(hè)”}”(hŒbitmap”h]”hŒbitmap”…””}”(hj@h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MŽhj<ubhø)”}”(hhh]”hý)”}”(hŒThe default internal bitmap”h]”hŒThe default internal bitmap”…””}”(hjQh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MhjNubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj<ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MŽhj ubhâ)”}”(hŒ&llbitmap The lockless internal bitmap ”h]”(hè)”}”(hŒllbitmap”h]”hŒllbitmap”…””}”(hjoh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M‘hjkubhø)”}”(hhh]”hý)”}”(hŒThe lockless internal bitmap”h]”hŒThe lockless internal bitmap”…””}”(hj€h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M‘hj}ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjkubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M‘hj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhjùubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjçubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M‘hjßubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhjÛubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙh³hÊh´KÁhjZh²hubhý)”}”(hŒ‹If bitmap_type is not none, then additional bitmap attributes bitmap/xxx or llbitmap/xxx will be created after md device KOBJ_CHANGE event.”h]”hŒ‹If bitmap_type is not none, then additional bitmap attributes bitmap/xxx or llbitmap/xxx will be created after md device KOBJ_CHANGE event.”…””}”(hj¸h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M“hjZh²hubhý)”}”(hŒ?If bitmap_type is bitmap, then the md device will also contain:”h]”hŒ?If bitmap_type is bitmap, then the md device will also contain:”…””}”(hjÆh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M–hjZh²hubjÚ)”}”(hXcbitmap/location This indicates where the write-intent bitmap for the array is stored. It can be one of ``none``, ``file`` or ``[+-]N``. ``file`` may later be extended to ``file:/file/name`` ``[+-]N`` means that many sectors from the start of the metadata. This is replicated on all devices. For arrays with externally managed metadata, the offset is from the beginning of the device. bitmap/chunksize The size, in bytes, of the chunk which will be represented by a single bit. For RAID456, it is a portion of an individual device. For RAID10, it is a portion of the array. For RAID1, it is both (they come to the same thing). bitmap/time_base The time, in seconds, between looking for bits in the bitmap to be cleared. In the current implementation, a bit will be cleared between 2 and 3 times ``time_base`` after all the covered blocks are known to be in-sync. bitmap/backlog When write-mostly devices are active in a RAID1, write requests to those devices proceed in the background - the filesystem (or other user of the device) does not have to wait for them. ``backlog`` sets a limit on the number of concurrent background writes. If there are more than this, new writes will by synchronous. bitmap/metadata This can be either ``internal`` or ``external``. ``internal`` is the default and means the metadata for the bitmap is stored in the first 256 bytes of the allocated space and is managed by the md module. ``external`` means that bitmap metadata is managed externally to the kernel (i.e. by some userspace program) bitmap/can_clear This is either ``true`` or ``false``. If ``true``, then bits in the bitmap will be cleared when the corresponding blocks are thought to be in-sync. If ``false``, bits will never be cleared. This is automatically set to ``false`` if a write happens on a degraded array, or if the array becomes degraded during a write. When metadata is managed externally, it should be set to true once the array becomes non-degraded, and this fact has been recorded in the metadata. ”h]”hÝ)”}”(hhh]”(hâ)”}”(hXƒbitmap/location This indicates where the write-intent bitmap for the array is stored. It can be one of ``none``, ``file`` or ``[+-]N``. ``file`` may later be extended to ``file:/file/name`` ``[+-]N`` means that many sectors from the start of the metadata. This is replicated on all devices. For arrays with externally managed metadata, the offset is from the beginning of the device. ”h]”(hè)”}”(hŒbitmap/location”h]”hŒbitmap/location”…””}”(hjßh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M¢hjÛubhø)”}”(hhh]”(hý)”}”(hŒEThis indicates where the write-intent bitmap for the array is stored.”h]”hŒEThis indicates where the write-intent bitmap for the array is stored.”…””}”(hjðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M™hjíubhý)”}”(hŒ©It can be one of ``none``, ``file`` or ``[+-]N``. ``file`` may later be extended to ``file:/file/name`` ``[+-]N`` means that many sectors from the start of the metadata.”h]”(hŒIt can be one of ”…””}”(hjþh²hh³Nh´Nubj˜)”}”(hŒ``none``”h]”hŒnone”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjþubhŒ, ”…””}”(hjþh²hh³Nh´Nubj˜)”}”(hŒ``file``”h]”hŒfile”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjþubhŒ or ”…””}”(hjþh²hh³Nh´Nubj˜)”}”(hŒ ``[+-]N``”h]”hŒ[+-]N”…””}”(hj*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjþubhŒ. ”…””}”(hjþh²hh³Nh´Nubj˜)”}”(hŒ``file``”h]”hŒfile”…””}”(hj<h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjþubhŒ may later be extended to ”…””}”(hjþh²hh³Nh´Nubj˜)”}”(hŒ``file:/file/name``”h]”hŒfile:/file/name”…””}”(hjNh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjþubhŒ ”…””}”(hjþh²hh³Nh´Nubj˜)”}”(hŒ ``[+-]N``”h]”hŒ[+-]N”…””}”(hj`h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjþubhŒ8 means that many sectors from the start of the metadata.”…””}”(hjþh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mœhjíubhý)”}”(hŒ€This is replicated on all devices. For arrays with externally managed metadata, the offset is from the beginning of the device.”h]”hŒ€This is replicated on all devices. For arrays with externally managed metadata, the offset is from the beginning of the device.”…””}”(hjxh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M hjíubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjÛubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M¢hjØubhâ)”}”(hŒôbitmap/chunksize The size, in bytes, of the chunk which will be represented by a single bit. For RAID456, it is a portion of an individual device. For RAID10, it is a portion of the array. For RAID1, it is both (they come to the same thing). ”h]”(hè)”}”(hŒbitmap/chunksize”h]”hŒbitmap/chunksize”…””}”(hj–h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M¨hj’ubhø)”}”(hhh]”hý)”}”(hŒâThe size, in bytes, of the chunk which will be represented by a single bit. For RAID456, it is a portion of an individual device. For RAID10, it is a portion of the array. For RAID1, it is both (they come to the same thing).”h]”hŒâThe size, in bytes, of the chunk which will be represented by a single bit. For RAID456, it is a portion of an individual device. For RAID10, it is a portion of the array. For RAID1, it is both (they come to the same thing).”…””}”(hj§h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M¥hj¤ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj’ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M¨hjØubhâ)”}”(hŒìbitmap/time_base The time, in seconds, between looking for bits in the bitmap to be cleared. In the current implementation, a bit will be cleared between 2 and 3 times ``time_base`` after all the covered blocks are known to be in-sync. ”h]”(hè)”}”(hŒbitmap/time_base”h]”hŒbitmap/time_base”…””}”(hjÅh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M®hjÁubhø)”}”(hhh]”hý)”}”(hŒÚThe time, in seconds, between looking for bits in the bitmap to be cleared. In the current implementation, a bit will be cleared between 2 and 3 times ``time_base`` after all the covered blocks are known to be in-sync.”h]”(hŒ—The time, in seconds, between looking for bits in the bitmap to be cleared. In the current implementation, a bit will be cleared between 2 and 3 times ”…””}”(hjÖh²hh³Nh´Nubj˜)”}”(hŒ ``time_base``”h]”hŒ time_base”…””}”(hjÞh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjÖubhŒ6 after all the covered blocks are known to be in-sync.”…””}”(hjÖh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M«hjÓubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjÁubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M®hjØubhâ)”}”(hXObitmap/backlog When write-mostly devices are active in a RAID1, write requests to those devices proceed in the background - the filesystem (or other user of the device) does not have to wait for them. ``backlog`` sets a limit on the number of concurrent background writes. If there are more than this, new writes will by synchronous. ”h]”(hè)”}”(hŒbitmap/backlog”h]”hŒbitmap/backlog”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M¶hjubhø)”}”(hhh]”hý)”}”(hX?When write-mostly devices are active in a RAID1, write requests to those devices proceed in the background - the filesystem (or other user of the device) does not have to wait for them. ``backlog`` sets a limit on the number of concurrent background writes. If there are more than this, new writes will by synchronous.”h]”(hŒºWhen write-mostly devices are active in a RAID1, write requests to those devices proceed in the background - the filesystem (or other user of the device) does not have to wait for them. ”…””}”(hjh²hh³Nh´Nubj˜)”}”(hŒ``backlog``”h]”hŒbacklog”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjubhŒz sets a limit on the number of concurrent background writes. If there are more than this, new writes will by synchronous.”…””}”(hjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M±hjubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M¶hjØubhâ)”}”(hXUbitmap/metadata This can be either ``internal`` or ``external``. ``internal`` is the default and means the metadata for the bitmap is stored in the first 256 bytes of the allocated space and is managed by the md module. ``external`` means that bitmap metadata is managed externally to the kernel (i.e. by some userspace program) ”h]”(hè)”}”(hŒbitmap/metadata”h]”hŒbitmap/metadata”…””}”(hjGh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MÂhjCubhø)”}”(hhh]”(hý)”}”(hŒ0This can be either ``internal`` or ``external``.”h]”(hŒThis can be either ”…””}”(hjXh²hh³Nh´Nubj˜)”}”(hŒ``internal``”h]”hŒinternal”…””}”(hj`h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjXubhŒ or ”…””}”(hjXh²hh³Nh´Nubj˜)”}”(hŒ``external``”h]”hŒexternal”…””}”(hjrh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjXubhŒ.”…””}”(hjXh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M¹hjUubhÝ)”}”(hhh]”(hâ)”}”(hŒ›``internal`` is the default and means the metadata for the bitmap is stored in the first 256 bytes of the allocated space and is managed by the md module. ”h]”(hè)”}”(hŒ``internal``”h]”j˜)”}”(hj“h]”hŒinternal”…””}”(hj•h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj‘ubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M¾hjubhø)”}”(hhh]”hý)”}”(hŒis the default and means the metadata for the bitmap is stored in the first 256 bytes of the allocated space and is managed by the md module.”h]”hŒis the default and means the metadata for the bitmap is stored in the first 256 bytes of the allocated space and is managed by the md module.”…””}”(hj«h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M¼hj¨ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M¾hjŠubhâ)”}”(hŒm``external`` means that bitmap metadata is managed externally to the kernel (i.e. by some userspace program) ”h]”(hè)”}”(hŒ``external``”h]”j˜)”}”(hjËh]”hŒexternal”…””}”(hjÍh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjÉubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MÂhjÅubhø)”}”(hhh]”hý)”}”(hŒ_means that bitmap metadata is managed externally to the kernel (i.e. by some userspace program)”h]”hŒ_means that bitmap metadata is managed externally to the kernel (i.e. by some userspace program)”…””}”(hjãh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MÁhjàubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjÅubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MÂhjŠubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhjUubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjCubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MÂhjØubhâ)”}”(hXåbitmap/can_clear This is either ``true`` or ``false``. If ``true``, then bits in the bitmap will be cleared when the corresponding blocks are thought to be in-sync. If ``false``, bits will never be cleared. This is automatically set to ``false`` if a write happens on a degraded array, or if the array becomes degraded during a write. When metadata is managed externally, it should be set to true once the array becomes non-degraded, and this fact has been recorded in the metadata. ”h]”(hè)”}”(hŒbitmap/can_clear”h]”hŒbitmap/can_clear”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MÌhjubhø)”}”(hhh]”hý)”}”(hXÓThis is either ``true`` or ``false``. If ``true``, then bits in the bitmap will be cleared when the corresponding blocks are thought to be in-sync. If ``false``, bits will never be cleared. This is automatically set to ``false`` if a write happens on a degraded array, or if the array becomes degraded during a write. When metadata is managed externally, it should be set to true once the array becomes non-degraded, and this fact has been recorded in the metadata.”h]”(hŒThis is either ”…””}”(hj$h²hh³Nh´Nubj˜)”}”(hŒ``true``”h]”hŒtrue”…””}”(hj,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj$ubhŒ or ”…””}”(hj$h²hh³Nh´Nubj˜)”}”(hŒ ``false``”h]”hŒfalse”…””}”(hj>h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj$ubhŒ. If ”…””}”(hj$h²hh³Nh´Nubj˜)”}”(hŒ``true``”h]”hŒtrue”…””}”(hjPh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj$ubhŒg, then bits in the bitmap will be cleared when the corresponding blocks are thought to be in-sync. If ”…””}”(hj$h²hh³Nh´Nubj˜)”}”(hŒ ``false``”h]”hŒfalse”…””}”(hjbh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj$ubhŒ;, bits will never be cleared. This is automatically set to ”…””}”(hj$h²hh³Nh´Nubj˜)”}”(hŒ ``false``”h]”hŒfalse”…””}”(hjth²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj$ubhŒí if a write happens on a degraded array, or if the array becomes degraded during a write. When metadata is managed externally, it should be set to true once the array becomes non-degraded, and this fact has been recorded in the metadata.”…””}”(hj$h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MÅhj!ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MÌhjØubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhjÔubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙh³hÊh´M˜hjZh²hubhý)”}”(hŒAIf bitmap_type is llbitmap, then the md device will also contain:”h]”hŒAIf bitmap_type is llbitmap, then the md device will also contain:”…””}”(hj¤h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MÎhjZh²hubjÚ)”}”(hXìllbitmap/bits This is read-only, show status of bitmap bits, the number of each value. llbitmap/metadata This is read-only, show bitmap metadata, include chunksize, chunkshift, chunks, offset and daemon_sleep. llbitmap/daemon_sleep This is read-write, time in seconds that daemon function will be triggered to clear dirty bits. llbitmap/barrier_idle This is read-write, time in seconds that page barrier will be idled, means dirty bits in the page will be cleared. ”h]”hÝ)”}”(hhh]”(hâ)”}”(hŒWllbitmap/bits This is read-only, show status of bitmap bits, the number of each value. ”h]”(hè)”}”(hŒ llbitmap/bits”h]”hŒ llbitmap/bits”…””}”(hj½h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MÒhj¹ubhø)”}”(hhh]”hý)”}”(hŒHThis is read-only, show status of bitmap bits, the number of each value.”h]”hŒHThis is read-only, show status of bitmap bits, the number of each value.”…””}”(hjÎh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MÑhjËubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj¹ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MÒhj¶ubhâ)”}”(hŒ{llbitmap/metadata This is read-only, show bitmap metadata, include chunksize, chunkshift, chunks, offset and daemon_sleep. ”h]”(hè)”}”(hŒllbitmap/metadata”h]”hŒllbitmap/metadata”…””}”(hjìh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MÖhjèubhø)”}”(hhh]”hý)”}”(hŒhThis is read-only, show bitmap metadata, include chunksize, chunkshift, chunks, offset and daemon_sleep.”h]”hŒhThis is read-only, show bitmap metadata, include chunksize, chunkshift, chunks, offset and daemon_sleep.”…””}”(hjýh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MÕhjúubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjèubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MÖhj¶ubhâ)”}”(hŒvllbitmap/daemon_sleep This is read-write, time in seconds that daemon function will be triggered to clear dirty bits. ”h]”(hè)”}”(hŒllbitmap/daemon_sleep”h]”hŒllbitmap/daemon_sleep”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MÚhjubhø)”}”(hhh]”hý)”}”(hŒ_This is read-write, time in seconds that daemon function will be triggered to clear dirty bits.”h]”hŒ_This is read-write, time in seconds that daemon function will be triggered to clear dirty bits.”…””}”(hj,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MÙhj)ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MÚhj¶ubhâ)”}”(hŒ‰llbitmap/barrier_idle This is read-write, time in seconds that page barrier will be idled, means dirty bits in the page will be cleared. ”h]”(hè)”}”(hŒllbitmap/barrier_idle”h]”hŒllbitmap/barrier_idle”…””}”(hjJh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MÞhjFubhø)”}”(hhh]”hý)”}”(hŒrThis is read-write, time in seconds that page barrier will be idled, means dirty bits in the page will be cleared.”h]”hŒrThis is read-write, time in seconds that page barrier will be idled, means dirty bits in the page will be cleared.”…””}”(hj[h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MÝhjXubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjFubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MÞhj¶ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhj²ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙh³hÊh´MÐhjZh²hubhý)”}”(hŒmAs component devices are added to an md array, they appear in the ``md`` directory as new directories named::”h]”(hŒBAs component devices are added to an md array, they appear in the ”…””}”(hjh²hh³Nh´Nubj˜)”}”(hŒ``md``”h]”hŒmd”…””}”(hj‰h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjubhŒ$ directory as new directories named:”…””}”(hjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MàhjZh²hubjG)”}”(hŒdev-XXX”h]”hŒdev-XXX”…””}”hj¡sbah}”(h]”h ]”h"]”h$]”h&]”jVjWuh1jFh³hÊh´MãhjZh²hubhý)”}”(hŒawhere ``XXX`` is a name that the kernel knows for the device, e.g. hdb1. Each directory contains:”h]”(hŒwhere ”…””}”(hj¯h²hh³Nh´Nubj˜)”}”(hŒ``XXX``”h]”hŒXXX”…””}”(hj·h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj¯ubhŒT is a name that the kernel knows for the device, e.g. hdb1. Each directory contains:”…””}”(hj¯h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MåhjZh²hubjÚ)”}”(hX/block a symlink to the block device in /sys/block, e.g.:: /sys/block/md0/md/dev-hdb1/block -> ../../../../block/hdb/hdb1 super A file containing an image of the superblock read from, or written to, that device. state A file recording the current state of the device in the array which can be a comma separated list of: faulty device has been kicked from active use due to a detected fault, or it has unacknowledged bad blocks in_sync device is a fully in-sync member of the array writemostly device will only be subject to read requests if there are no other options. This applies only to raid1 arrays. blocked device has failed, and the failure hasn't been acknowledged yet by the metadata handler. Writes that would write to this device if it were not faulty are blocked. spare device is working, but not a full member. This includes spares that are in the process of being recovered to write_error device has ever seen a write error. want_replacement device is (mostly) working but probably should be replaced, either due to errors or due to user request. replacement device is a replacement for another active device with same raid_disk. This list may grow in future. This can be written to. Writing ``faulty`` simulates a failure on the device. Writing ``remove`` removes the device from the array. Writing ``writemostly`` sets the writemostly flag. Writing ``-writemostly`` clears the writemostly flag. Writing ``blocked`` sets the ``blocked`` flag. Writing ``-blocked`` clears the ``blocked`` flags and allows writes to complete and possibly simulates an error. Writing ``in_sync`` sets the in_sync flag. Writing ``write_error`` sets writeerrorseen flag. Writing ``-write_error`` clears writeerrorseen flag. Writing ``want_replacement`` is allowed at any time except to a replacement device or a spare. It sets the flag. Writing ``-want_replacement`` is allowed at any time. It clears the flag. Writing ``replacement`` or ``-replacement`` is only allowed before starting the array. It sets or clears the flag. This file responds to select/poll. Any change to ``faulty`` or ``blocked`` causes an event. errors An approximate count of read errors that have been detected on this device but have not caused the device to be evicted from the array (either because they were corrected or because they happened while the array was read-only). When using version-1 metadata, this value persists across restarts of the array. This value can be written while assembling an array thus providing an ongoing count for arrays with metadata managed by userspace. slot This gives the role that the device has in the array. It will either be ``none`` if the device is not active in the array (i.e. is a spare or has failed) or an integer less than the ``raid_disks`` number for the array indicating which position it currently fills. This can only be set while assembling an array. A device for which this is set is assumed to be working. offset This gives the location in the device (in sectors from the start) where data from the array will be stored. Any part of the device before this offset is not touched, unless it is used for storing metadata (Formats 1.1 and 1.2). size The amount of the device, after the offset, that can be used for storage of data. This will normally be the same as the component_size. This can be written while assembling an array. If a value less than the current component_size is written, it will be rejected. recovery_start When the device is not ``in_sync``, this records the number of sectors from the start of the device which are known to be correct. This is normally zero, but during a recovery operation it will steadily increase, and if the recovery is interrupted, restoring this value can cause recovery to avoid repeating the earlier blocks. With v1.x metadata, this value is saved and restored automatically. This can be set whenever the device is not an active member of the array, either before the array is activated, or before the ``slot`` is set. Setting this to ``none`` is equivalent to setting ``in_sync``. Setting to any other value also clears the ``in_sync`` flag. bad_blocks This gives the list of all known bad blocks in the form of start address and length (in sectors respectively). If output is too big to fit in a page, it will be truncated. Writing ``sector length`` to this file adds new acknowledged (i.e. recorded to disk safely) bad blocks. unacknowledged_bad_blocks This gives the list of known-but-not-yet-saved-to-disk bad blocks in the same form of ``bad_blocks``. If output is too big to fit in a page, it will be truncated. Writing to this file adds bad blocks without acknowledging them. This is largely for testing. ppl_sector, ppl_size Location and size (in sectors) of the space used for Partial Parity Log on this device. ”h]”hÝ)”}”(hhh]”(hâ)”}”(hŒblock a symlink to the block device in /sys/block, e.g.:: /sys/block/md0/md/dev-hdb1/block -> ../../../../block/hdb/hdb1 ”h]”(hè)”}”(hŒblock”h]”hŒblock”…””}”(hjÚh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MëhjÖubhø)”}”(hhh]”(hý)”}”(hŒ3a symlink to the block device in /sys/block, e.g.::”h]”hŒ2a symlink to the block device in /sys/block, e.g.:”…””}”(hjëh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MéhjèubjG)”}”(hŒ>/sys/block/md0/md/dev-hdb1/block -> ../../../../block/hdb/hdb1”h]”hŒ>/sys/block/md0/md/dev-hdb1/block -> ../../../../block/hdb/hdb1”…””}”hjùsbah}”(h]”h ]”h"]”h$]”h&]”jVjWuh1jFh³hÊh´Mëhjèubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjÖubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MëhjÓubhâ)”}”(hŒZsuper A file containing an image of the superblock read from, or written to, that device. ”h]”(hè)”}”(hŒsuper”h]”hŒsuper”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mïhjubhø)”}”(hhh]”hý)”}”(hŒSA file containing an image of the superblock read from, or written to, that device.”h]”hŒSA file containing an image of the superblock read from, or written to, that device.”…””}”(hj(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mîhj%ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MïhjÓubhâ)”}”(hXústate A file recording the current state of the device in the array which can be a comma separated list of: faulty device has been kicked from active use due to a detected fault, or it has unacknowledged bad blocks in_sync device is a fully in-sync member of the array writemostly device will only be subject to read requests if there are no other options. This applies only to raid1 arrays. blocked device has failed, and the failure hasn't been acknowledged yet by the metadata handler. Writes that would write to this device if it were not faulty are blocked. spare device is working, but not a full member. This includes spares that are in the process of being recovered to write_error device has ever seen a write error. want_replacement device is (mostly) working but probably should be replaced, either due to errors or due to user request. replacement device is a replacement for another active device with same raid_disk. This list may grow in future. This can be written to. Writing ``faulty`` simulates a failure on the device. Writing ``remove`` removes the device from the array. Writing ``writemostly`` sets the writemostly flag. Writing ``-writemostly`` clears the writemostly flag. Writing ``blocked`` sets the ``blocked`` flag. Writing ``-blocked`` clears the ``blocked`` flags and allows writes to complete and possibly simulates an error. Writing ``in_sync`` sets the in_sync flag. Writing ``write_error`` sets writeerrorseen flag. Writing ``-write_error`` clears writeerrorseen flag. Writing ``want_replacement`` is allowed at any time except to a replacement device or a spare. It sets the flag. Writing ``-want_replacement`` is allowed at any time. It clears the flag. Writing ``replacement`` or ``-replacement`` is only allowed before starting the array. It sets or clears the flag. This file responds to select/poll. Any change to ``faulty`` or ``blocked`` causes an event. ”h]”(hè)”}”(hŒstate”h]”hŒstate”…””}”(hjFh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M?hjBubhø)”}”(hhh]”(hý)”}”(hŒeA file recording the current state of the device in the array which can be a comma separated list of:”h]”hŒeA file recording the current state of the device in the array which can be a comma separated list of:”…””}”(hjWh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MòhjTubjÚ)”}”(hX faulty device has been kicked from active use due to a detected fault, or it has unacknowledged bad blocks in_sync device is a fully in-sync member of the array writemostly device will only be subject to read requests if there are no other options. This applies only to raid1 arrays. blocked device has failed, and the failure hasn't been acknowledged yet by the metadata handler. Writes that would write to this device if it were not faulty are blocked. spare device is working, but not a full member. This includes spares that are in the process of being recovered to write_error device has ever seen a write error. want_replacement device is (mostly) working but probably should be replaced, either due to errors or due to user request. replacement device is a replacement for another active device with same raid_disk. ”h]”hÝ)”}”(hhh]”(hâ)”}”(hŒkfaulty device has been kicked from active use due to a detected fault, or it has unacknowledged bad blocks ”h]”(hè)”}”(hŒfaulty”h]”hŒfaulty”…””}”(hjph²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Møhjlubhø)”}”(hhh]”hý)”}”(hŒcdevice has been kicked from active use due to a detected fault, or it has unacknowledged bad blocks”h]”hŒcdevice has been kicked from active use due to a detected fault, or it has unacknowledged bad blocks”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Möhj~ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjlubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Møhjiubhâ)”}”(hŒ6in_sync device is a fully in-sync member of the array ”h]”(hè)”}”(hŒin_sync”h]”hŒin_sync”…””}”(hjŸh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mûhj›ubhø)”}”(hhh]”hý)”}”(hŒ-device is a fully in-sync member of the array”h]”hŒ-device is a fully in-sync member of the array”…””}”(hj°h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mûhjubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj›ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mûhjiubhâ)”}”(hŒ|writemostly device will only be subject to read requests if there are no other options. This applies only to raid1 arrays. ”h]”(hè)”}”(hŒwritemostly”h]”hŒwritemostly”…””}”(hjÎh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MhjÊubhø)”}”(hhh]”(hý)”}”(hŒKdevice will only be subject to read requests if there are no other options.”h]”hŒKdevice will only be subject to read requests if there are no other options.”…””}”(hjßh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MþhjÜubhý)”}”(hŒ"This applies only to raid1 arrays.”h]”hŒ"This applies only to raid1 arrays.”…””}”(hjíh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MhjÜubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjÊubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhjiubhâ)”}”(hŒ¬blocked device has failed, and the failure hasn't been acknowledged yet by the metadata handler. Writes that would write to this device if it were not faulty are blocked. ”h]”(hè)”}”(hŒblocked”h]”hŒblocked”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mhjubhø)”}”(hhh]”(hý)”}”(hŒXdevice has failed, and the failure hasn't been acknowledged yet by the metadata handler.”h]”hŒZdevice has failed, and the failure hasnâ€™t been acknowledged yet by the metadata handler.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mhjubhý)”}”(hŒIWrites that would write to this device if it were not faulty are blocked.”h]”hŒIWrites that would write to this device if it were not faulty are blocked.”…””}”(hj*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhjiubhâ)”}”(hŒtspare device is working, but not a full member. This includes spares that are in the process of being recovered to ”h]”(hè)”}”(hŒspare”h]”hŒspare”…””}”(hjHh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MhjDubhø)”}”(hhh]”(hý)”}”(hŒ)device is working, but not a full member.”h]”hŒ)device is working, but not a full member.”…””}”(hjYh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MhjVubhý)”}”(hŒBThis includes spares that are in the process of being recovered to”h]”hŒBThis includes spares that are in the process of being recovered to”…””}”(hjgh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M hjVubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjDubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhjiubhâ)”}”(hŒ0write_error device has ever seen a write error. ”h]”(hè)”}”(hŒwrite_error”h]”hŒwrite_error”…””}”(hj…h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mhjubhø)”}”(hhh]”hý)”}”(hŒ#device has ever seen a write error.”h]”hŒ#device has ever seen a write error.”…””}”(hj–h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mhj“ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhjiubhâ)”}”(hŒzwant_replacement device is (mostly) working but probably should be replaced, either due to errors or due to user request. ”h]”(hè)”}”(hŒwant_replacement”h]”hŒwant_replacement”…””}”(hj´h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mhj°ubhø)”}”(hhh]”hý)”}”(hŒhdevice is (mostly) working but probably should be replaced, either due to errors or due to user request.”h]”hŒhdevice is (mostly) working but probably should be replaced, either due to errors or due to user request.”…””}”(hjÅh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MhjÂubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj°ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhjiubhâ)”}”(hŒTreplacement device is a replacement for another active device with same raid_disk. ”h]”(hè)”}”(hŒreplacement”h]”hŒreplacement”…””}”(hjãh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mhjßubhø)”}”(hhh]”hý)”}”(hŒFdevice is a replacement for another active device with same raid_disk.”h]”hŒFdevice is a replacement for another active device with same raid_disk.”…””}”(hjôh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mhjñubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjßubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhjiubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhjeubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙh³hÊh´MõhjTubhý)”}”(hŒThis list may grow in future.”h]”hŒThis list may grow in future.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MhjTubhý)”}”(hŒThis can be written to.”h]”hŒThis can be written to.”…””}”(hj(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MhjTubhý)”}”(hŒ6Writing ``faulty`` simulates a failure on the device.”h]”(hŒWriting ”…””}”(hj6h²hh³Nh´Nubj˜)”}”(hŒ ``faulty``”h]”hŒfaulty”…””}”(hj>h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj6ubhŒ$ simulates a failure on the device.”…””}”(hj6h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M!hjTubhý)”}”(hŒ5Writing ``remove`` removes the device from the array.”h]”(hŒWriting ”…””}”(hjVh²hh³Nh´Nubj˜)”}”(hŒ ``remove``”h]”hŒremove”…””}”(hj^h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjVubhŒ# removes the device from the array.”…””}”(hjVh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M#hjTubhý)”}”(hŒ2Writing ``writemostly`` sets the writemostly flag.”h]”(hŒWriting ”…””}”(hjvh²hh³Nh´Nubj˜)”}”(hŒ``writemostly``”h]”hŒwritemostly”…””}”(hj~h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjvubhŒ sets the writemostly flag.”…””}”(hjvh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M%hjTubhý)”}”(hŒ5Writing ``-writemostly`` clears the writemostly flag.”h]”(hŒWriting ”…””}”(hj–h²hh³Nh´Nubj˜)”}”(hŒ``-writemostly``”h]”hŒ-writemostly”…””}”(hjžh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj–ubhŒ clears the writemostly flag.”…””}”(hj–h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M'hjTubhý)”}”(hŒ.Writing ``blocked`` sets the ``blocked`` flag.”h]”(hŒWriting ”…””}”(hj¶h²hh³Nh´Nubj˜)”}”(hŒ``blocked``”h]”hŒblocked”…””}”(hj¾h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj¶ubhŒ sets the ”…””}”(hj¶h²hh³Nh´Nubj˜)”}”(hŒ``blocked``”h]”hŒblocked”…””}”(hjÐh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj¶ubhŒ flag.”…””}”(hj¶h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M)hjTubhý)”}”(hŒpWriting ``-blocked`` clears the ``blocked`` flags and allows writes to complete and possibly simulates an error.”h]”(hŒWriting ”…””}”(hjèh²hh³Nh´Nubj˜)”}”(hŒ``-blocked``”h]”hŒ-blocked”…””}”(hjðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjèubhŒ clears the ”…””}”(hjèh²hh³Nh´Nubj˜)”}”(hŒ``blocked``”h]”hŒblocked”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjèubhŒE flags and allows writes to complete and possibly simulates an error.”…””}”(hjèh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M+hjTubhý)”}”(hŒ*Writing ``in_sync`` sets the in_sync flag.”h]”(hŒWriting ”…””}”(hjh²hh³Nh´Nubj˜)”}”(hŒ``in_sync``”h]”hŒin_sync”…””}”(hj"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjubhŒ sets the in_sync flag.”…””}”(hjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M.hjTubhý)”}”(hŒ1Writing ``write_error`` sets writeerrorseen flag.”h]”(hŒWriting ”…””}”(hj:h²hh³Nh´Nubj˜)”}”(hŒ``write_error``”h]”hŒwrite_error”…””}”(hjBh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj:ubhŒ sets writeerrorseen flag.”…””}”(hj:h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M0hjTubhý)”}”(hŒ4Writing ``-write_error`` clears writeerrorseen flag.”h]”(hŒWriting ”…””}”(hjZh²hh³Nh´Nubj˜)”}”(hŒ``-write_error``”h]”hŒ-write_error”…””}”(hjbh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjZubhŒ clears writeerrorseen flag.”…””}”(hjZh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M2hjTubhý)”}”(hŒqWriting ``want_replacement`` is allowed at any time except to a replacement device or a spare. It sets the flag.”h]”(hŒWriting ”…””}”(hjzh²hh³Nh´Nubj˜)”}”(hŒ``want_replacement``”h]”hŒwant_replacement”…””}”(hj‚h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjzubhŒU is allowed at any time except to a replacement device or a spare. It sets the flag.”…””}”(hjzh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M4hjTubhý)”}”(hŒJWriting ``-want_replacement`` is allowed at any time. It clears the flag.”h]”(hŒWriting ”…””}”(hjšh²hh³Nh´Nubj˜)”}”(hŒ``-want_replacement``”h]”hŒ-want_replacement”…””}”(hj¢h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjšubhŒ- is allowed at any time. It clears the flag.”…””}”(hjšh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M7hjTubhý)”}”(hŒsWriting ``replacement`` or ``-replacement`` is only allowed before starting the array. It sets or clears the flag.”h]”(hŒWriting ”…””}”(hjºh²hh³Nh´Nubj˜)”}”(hŒ``replacement``”h]”hŒreplacement”…””}”(hjÂh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjºubhŒ or ”…””}”(hjºh²hh³Nh´Nubj˜)”}”(hŒ``-replacement``”h]”hŒ-replacement”…””}”(hjÔh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjºubhŒH is only allowed before starting the array. It sets or clears the flag.”…””}”(hjºh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M:hjTubhý)”}”(hŒ[This file responds to select/poll. Any change to ``faulty`` or ``blocked`` causes an event.”h]”(hŒ1This file responds to select/poll. Any change to ”…””}”(hjìh²hh³Nh´Nubj˜)”}”(hŒ ``faulty``”h]”hŒfaulty”…””}”(hjôh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjìubhŒ or ”…””}”(hjìh²hh³Nh´Nubj˜)”}”(hŒ``blocked``”h]”hŒblocked”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjìubhŒ causes an event.”…””}”(hjìh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M>hjTubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjBubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M?hjÓubhâ)”}”(hXÁerrors An approximate count of read errors that have been detected on this device but have not caused the device to be evicted from the array (either because they were corrected or because they happened while the array was read-only). When using version-1 metadata, this value persists across restarts of the array. This value can be written while assembling an array thus providing an ongoing count for arrays with metadata managed by userspace. ”h]”(hè)”}”(hŒerrors”h]”hŒerrors”…””}”(hj.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MJhj*ubhø)”}”(hhh]”(hý)”}”(hX5An approximate count of read errors that have been detected on this device but have not caused the device to be evicted from the array (either because they were corrected or because they happened while the array was read-only). When using version-1 metadata, this value persists across restarts of the array.”h]”hX5An approximate count of read errors that have been detected on this device but have not caused the device to be evicted from the array (either because they were corrected or because they happened while the array was read-only). When using version-1 metadata, this value persists across restarts of the array.”…””}”(hj?h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MBhj<ubhý)”}”(hŒ‚This value can be written while assembling an array thus providing an ongoing count for arrays with metadata managed by userspace.”h]”hŒ‚This value can be written while assembling an array thus providing an ongoing count for arrays with metadata managed by userspace.”…””}”(hjMh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MHhj<ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj*ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MJhjÓubhâ)”}”(hXyslot This gives the role that the device has in the array. It will either be ``none`` if the device is not active in the array (i.e. is a spare or has failed) or an integer less than the ``raid_disks`` number for the array indicating which position it currently fills. This can only be set while assembling an array. A device for which this is set is assumed to be working. ”h]”(hè)”}”(hŒslot”h]”hŒslot”…””}”(hjkh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MRhjgubhø)”}”(hhh]”hý)”}”(hXsThis gives the role that the device has in the array. It will either be ``none`` if the device is not active in the array (i.e. is a spare or has failed) or an integer less than the ``raid_disks`` number for the array indicating which position it currently fills. This can only be set while assembling an array. A device for which this is set is assumed to be working.”h]”(hŒIThis gives the role that the device has in the array. It will either be ”…””}”(hj|h²hh³Nh´Nubj˜)”}”(hŒ``none``”h]”hŒnone”…””}”(hj„h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj|ubhŒf if the device is not active in the array (i.e. is a spare or has failed) or an integer less than the ”…””}”(hj|h²hh³Nh´Nubj˜)”}”(hŒ``raid_disks``”h]”hŒ raid_disks”…””}”(hj–h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj|ubhŒ® number for the array indicating which position it currently fills. This can only be set while assembling an array. A device for which this is set is assumed to be working.”…””}”(hj|h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MMhjyubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjgubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MRhjÓubhâ)”}”(hŒìoffset This gives the location in the device (in sectors from the start) where data from the array will be stored. Any part of the device before this offset is not touched, unless it is used for storing metadata (Formats 1.1 and 1.2). ”h]”(hè)”}”(hŒoffset”h]”hŒoffset”…””}”(hj¾h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MXhjºubhø)”}”(hhh]”hý)”}”(hŒäThis gives the location in the device (in sectors from the start) where data from the array will be stored. Any part of the device before this offset is not touched, unless it is used for storing metadata (Formats 1.1 and 1.2).”h]”hŒäThis gives the location in the device (in sectors from the start) where data from the array will be stored. Any part of the device before this offset is not touched, unless it is used for storing metadata (Formats 1.1 and 1.2).”…””}”(hjÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MUhjÌubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjºubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MXhjÓubhâ)”}”(hXsize The amount of the device, after the offset, that can be used for storage of data. This will normally be the same as the component_size. This can be written while assembling an array. If a value less than the current component_size is written, it will be rejected. ”h]”(hè)”}”(hŒsize”h]”hŒsize”…””}”(hjíh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M_hjéubhø)”}”(hhh]”hý)”}”(hX The amount of the device, after the offset, that can be used for storage of data. This will normally be the same as the component_size. This can be written while assembling an array. If a value less than the current component_size is written, it will be rejected.”h]”hX The amount of the device, after the offset, that can be used for storage of data. This will normally be the same as the component_size. This can be written while assembling an array. If a value less than the current component_size is written, it will be rejected.”…””}”(hjþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M[hjûubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjéubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M_hjÓubhâ)”}”(hXªrecovery_start When the device is not ``in_sync``, this records the number of sectors from the start of the device which are known to be correct. This is normally zero, but during a recovery operation it will steadily increase, and if the recovery is interrupted, restoring this value can cause recovery to avoid repeating the earlier blocks. With v1.x metadata, this value is saved and restored automatically. This can be set whenever the device is not an active member of the array, either before the array is activated, or before the ``slot`` is set. Setting this to ``none`` is equivalent to setting ``in_sync``. Setting to any other value also clears the ``in_sync`` flag. ”h]”(hè)”}”(hŒrecovery_start”h]”hŒrecovery_start”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mohjubhø)”}”(hhh]”(hý)”}”(hXWhen the device is not ``in_sync``, this records the number of sectors from the start of the device which are known to be correct. This is normally zero, but during a recovery operation it will steadily increase, and if the recovery is interrupted, restoring this value can cause recovery to avoid repeating the earlier blocks. With v1.x metadata, this value is saved and restored automatically.”h]”(hŒWhen the device is not ”…””}”(hj-h²hh³Nh´Nubj˜)”}”(hŒ``in_sync``”h]”hŒin_sync”…””}”(hj5h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj-ubhXk, this records the number of sectors from the start of the device which are known to be correct. This is normally zero, but during a recovery operation it will steadily increase, and if the recovery is interrupted, restoring this value can cause recovery to avoid repeating the earlier blocks. With v1.x metadata, this value is saved and restored automatically.”…””}”(hj-h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mbhj*ubhý)”}”(hŒŽThis can be set whenever the device is not an active member of the array, either before the array is activated, or before the ``slot`` is set.”h]”(hŒ~This can be set whenever the device is not an active member of the array, either before the array is activated, or before the ”…””}”(hjMh²hh³Nh´Nubj˜)”}”(hŒ``slot``”h]”hŒslot”…””}”(hjUh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjMubhŒ is set.”…””}”(hjMh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mjhj*ubhý)”}”(hŒ{Setting this to ``none`` is equivalent to setting ``in_sync``. Setting to any other value also clears the ``in_sync`` flag.”h]”(hŒSetting this to ”…””}”(hjmh²hh³Nh´Nubj˜)”}”(hŒ``none``”h]”hŒnone”…””}”(hjuh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjmubhŒ is equivalent to setting ”…””}”(hjmh²hh³Nh´Nubj˜)”}”(hŒ``in_sync``”h]”hŒin_sync”…””}”(hj‡h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjmubhŒ-. Setting to any other value also clears the ”…””}”(hjmh²hh³Nh´Nubj˜)”}”(hŒ``in_sync``”h]”hŒin_sync”…””}”(hj™h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjmubhŒ flag.”…””}”(hjmh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mnhj*ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MohjÓubhâ)”}”(hXbad_blocks This gives the list of all known bad blocks in the form of start address and length (in sectors respectively). If output is too big to fit in a page, it will be truncated. Writing ``sector length`` to this file adds new acknowledged (i.e. recorded to disk safely) bad blocks. ”h]”(hè)”}”(hŒ bad_blocks”h]”hŒ bad_blocks”…””}”(hjÁh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mvhj½ubhø)”}”(hhh]”hý)”}”(hXThis gives the list of all known bad blocks in the form of start address and length (in sectors respectively). If output is too big to fit in a page, it will be truncated. Writing ``sector length`` to this file adds new acknowledged (i.e. recorded to disk safely) bad blocks.”h]”(hŒ´This gives the list of all known bad blocks in the form of start address and length (in sectors respectively). If output is too big to fit in a page, it will be truncated. Writing ”…””}”(hjÒh²hh³Nh´Nubj˜)”}”(hŒ``sector length``”h]”hŒ sector length”…””}”(hjÚh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjÒubhŒN to this file adds new acknowledged (i.e. recorded to disk safely) bad blocks.”…””}”(hjÒh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MrhjÏubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj½ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MvhjÓubhâ)”}”(hXunacknowledged_bad_blocks This gives the list of known-but-not-yet-saved-to-disk bad blocks in the same form of ``bad_blocks``. If output is too big to fit in a page, it will be truncated. Writing to this file adds bad blocks without acknowledging them. This is largely for testing. ”h]”(hè)”}”(hŒunacknowledged_bad_blocks”h]”hŒunacknowledged_bad_blocks”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M}hjþubhø)”}”(hhh]”hý)”}”(hXThis gives the list of known-but-not-yet-saved-to-disk bad blocks in the same form of ``bad_blocks``. If output is too big to fit in a page, it will be truncated. Writing to this file adds bad blocks without acknowledging them. This is largely for testing.”h]”(hŒVThis gives the list of known-but-not-yet-saved-to-disk bad blocks in the same form of ”…””}”(hjh²hh³Nh´Nubj˜)”}”(hŒ``bad_blocks``”h]”hŒ bad_blocks”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjubhŒœ. If output is too big to fit in a page, it will be truncated. Writing to this file adds bad blocks without acknowledging them. This is largely for testing.”…””}”(hjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Myhjubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjþubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M}hjÓubhâ)”}”(hŒnppl_sector, ppl_size Location and size (in sectors) of the space used for Partial Parity Log on this device. ”h]”(hè)”}”(hŒppl_sector, ppl_size”h]”hŒppl_sector, ppl_size”…””}”(hjCh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M‚hj?ubhø)”}”(hhh]”hý)”}”(hŒWLocation and size (in sectors) of the space used for Partial Parity Log on this device.”h]”hŒWLocation and size (in sectors) of the space used for Partial Parity Log on this device.”…””}”(hjTh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M€hjQubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj?ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M‚hjÓubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhjÏubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙh³hÊh´MèhjZh²hubhý)”}”(hŒfAn active md device will also contain an entry for each active device in the array. These are named::”h]”hŒeAn active md device will also contain an entry for each active device in the array. These are named:”…””}”(hjzh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M„hjZh²hubjG)”}”(hŒrdNN”h]”hŒrdNN”…””}”hjˆsbah}”(h]”h ]”h"]”h$]”h&]”jVjWuh1jFh³hÊh´M‡hjZh²hubhý)”}”(hŒÂwhere ``NN`` is the position in the array, starting from 0. So for a 3 drive array there will be rd0, rd1, rd2. These are symbolic links to the appropriate ``dev-XXX`` entry. Thus, for example::”h]”(hŒwhere ”…””}”(hj–h²hh³Nh´Nubj˜)”}”(hŒ``NN``”h]”hŒNN”…””}”(hjžh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj–ubhŒ is the position in the array, starting from 0. So for a 3 drive array there will be rd0, rd1, rd2. These are symbolic links to the appropriate ”…””}”(hj–h²hh³Nh´Nubj˜)”}”(hŒ``dev-XXX``”h]”hŒdev-XXX”…””}”(hj°h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj–ubhŒ entry. Thus, for example:”…””}”(hj–h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M‰hjZh²hubjG)”}”(hŒcat /sys/block/md*/md/rd*/state”h]”hŒcat /sys/block/md*/md/rd*/state”…””}”hjÈsbah}”(h]”h ]”h"]”h$]”h&]”jVjWuh1jFh³hÊh´MŽhjZh²hubhý)”}”(hŒ$will show ``in_sync`` on every line.”h]”(hŒ will show ”…””}”(hjÖh²hh³Nh´Nubj˜)”}”(hŒ``in_sync``”h]”hŒin_sync”…””}”(hjÞh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjÖubhŒ on every line.”…””}”(hjÖh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MhjZh²hubhý)”}”(hŒPActive md devices for levels that support data redundancy (1,4,5,6,10) also have”h]”hŒPActive md devices for levels that support data redundancy (1,4,5,6,10) also have”…””}”(hjöh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M”hjZh²hubjÚ)”}”(hXÙsync_action a text file that can be used to monitor and control the rebuild process. It contains one word which can be one of: resync redundancy is being recalculated after unclean shutdown or creation recover a hot spare is being built to replace a failed/missing device idle nothing is happening check A full check of redundancy was requested and is happening. This reads all blocks and checks them. A repair may also happen for some raid levels. repair A full check and repair is happening. This is similar to ``resync``, but was requested by the user, and the write-intent bitmap is NOT used to optimise the process. This file is writable, and each of the strings that could be read are meaningful for writing. ``idle`` will stop an active resync/recovery etc. There is no guarantee that another resync/recovery may not be automatically started again, though some event will be needed to trigger this. ``resync`` or ``recovery`` can be used to restart the corresponding operation if it was stopped with ``idle``. ``check`` and ``repair`` will start the appropriate process providing the current state is ``idle``. This file responds to select/poll. Any important change in the value triggers a poll event. Sometimes the value will briefly be ``recover`` if a recovery seems to be needed, but cannot be achieved. In that case, the transition to ``recover`` isn't notified, but the transition away is. degraded This contains a count of the number of devices by which the arrays is degraded. So an optimal array will show ``0``. A single failed/missing drive will show ``1``, etc. This file responds to select/poll, any increase or decrease in the count of missing devices will trigger an event. mismatch_count When performing ``check`` and ``repair``, and possibly when performing ``resync``, md will count the number of errors that are found. The count in ``mismatch_cnt`` is the number of sectors that were re-written, or (for ``check``) would have been re-written. As most raid levels work in units of pages rather than sectors, this may be larger than the number of actual errors by a factor of the number of sectors in a page. bitmap_set_bits If the array has a write-intent bitmap, then writing to this attribute can set bits in the bitmap, indicating that a resync would need to check the corresponding blocks. Either individual numbers or start-end pairs can be written. Multiple numbers can be separated by a space. Note that the numbers are ``bit`` numbers, not ``block`` numbers. They should be scaled by the bitmap_chunksize. sync_speed_min, sync_speed_max These are similar to ``/proc/sys/dev/raid/speed_limit_{min,max}`` however they only apply to the particular array. If no value has been written to these, or if the word ``system`` is written, then the system-wide value is used. If a value, in kibibytes-per-second is written, then it is used. When the files are read, they show the currently active value followed by ``(local)`` or ``(system)`` depending on whether it is a locally set or system-wide value. sync_completed This shows the number of sectors that have been completed of whatever the current sync_action is, followed by the number of sectors in total that could need to be processed. The two numbers are separated by a ``/`` thus effectively showing one value, a fraction of the process that is complete. A ``select`` on this attribute will return when resync completes, when it reaches the current sync_max (below) and possibly at other times. sync_speed This shows the current actual speed, in K/sec, of the current sync_action. It is averaged over the last 30 seconds. suspend_lo, suspend_hi The two values, given as numbers of sectors, indicate a range within the array where IO will be blocked. This is currently only supported for raid4/5/6. sync_min, sync_max The two values, given as numbers of sectors, indicate a range within the array where ``check``/``repair`` will operate. Must be a multiple of chunk_size. When it reaches ``sync_max`` it will pause, rather than complete. You can use ``select`` or ``poll`` on ``sync_completed`` to wait for that number to reach sync_max. Then you can either increase ``sync_max``, or can write ``idle`` to ``sync_action``. The value of ``max`` for ``sync_max`` effectively disables the limit. When a resync is active, the value can only ever be increased, never decreased. The value of ``0`` is the minimum for ``sync_min``. ”•‹h]”hÝ)”}”(hhh]”(hâ)”}”(hXCsync_action a text file that can be used to monitor and control the rebuild process. It contains one word which can be one of: resync redundancy is being recalculated after unclean shutdown or creation recover a hot spare is being built to replace a failed/missing device idle nothing is happening check A full check of redundancy was requested and is happening. This reads all blocks and checks them. A repair may also happen for some raid levels. repair A full check and repair is happening. This is similar to ``resync``, but was requested by the user, and the write-intent bitmap is NOT used to optimise the process. This file is writable, and each of the strings that could be read are meaningful for writing. ``idle`` will stop an active resync/recovery etc. There is no guarantee that another resync/recovery may not be automatically started again, though some event will be needed to trigger this. ``resync`` or ``recovery`` can be used to restart the corresponding operation if it was stopped with ``idle``. ``check`` and ``repair`` will start the appropriate process providing the current state is ``idle``. This file responds to select/poll. Any important change in the value triggers a poll event. Sometimes the value will briefly be ``recover`` if a recovery seems to be needed, but cannot be achieved. In that case, the transition to ``recover`` isn't notified, but the transition away is. ”h]”(hè)”}”(hŒsync_action”h]”hŒsync_action”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MÃhjubhø)”}”(hhh]”(hý)”}”(hŒsa text file that can be used to monitor and control the rebuild process. It contains one word which can be one of:”h]”hŒsa text file that can be used to monitor and control the rebuild process. It contains one word which can be one of:”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M˜hjubjÚ)”}”(hX¡ resync redundancy is being recalculated after unclean shutdown or creation recover a hot spare is being built to replace a failed/missing device idle nothing is happening check A full check of redundancy was requested and is happening. This reads all blocks and checks them. A repair may also happen for some raid levels. repair A full check and repair is happening. This is similar to ``resync``, but was requested by the user, and the write-intent bitmap is NOT used to optimise the process. This file is writable, and each of the strings that could be read are meaningful for writing. ``idle`` will stop an active resync/recovery etc. There is no guarantee that another resync/recovery may not be automatically started again, though some event will be needed to trigger this. ``resync`` or ``recovery`` can be used to restart the corresponding operation if it was stopped with ``idle``. ``check`` and ``repair`` will start the appropriate process providing the current state is ``idle``. This file responds to select/poll. Any important change in the value triggers a poll event. Sometimes the value will briefly be ``recover`` if a recovery seems to be needed, but cannot be achieved. In that case, the transition to ``recover`` isn't notified, but the transition away is. ”h]”(jÚ)”}”(hXhresync redundancy is being recalculated after unclean shutdown or creation recover a hot spare is being built to replace a failed/missing device idle nothing is happening check A full check of redundancy was requested and is happening. This reads all blocks and checks them. A repair may also happen for some raid levels. repair A full check and repair is happening. This is similar to ``resync``, but was requested by the user, and the write-intent bitmap is NOT used to optimise the process. ”h]”hÝ)”}”(hhh]”(hâ)”}”(hŒKresync redundancy is being recalculated after unclean shutdown or creation ”h]”(hè)”}”(hŒresync”h]”hŒresync”…””}”(hj=h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mhj9ubhø)”}”(hhh]”hý)”}”(hŒCredundancy is being recalculated after unclean shutdown or creation”h]”hŒCredundancy is being recalculated after unclean shutdown or creation”…””}”(hjNh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MœhjKubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj9ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhj6ubhâ)”}”(hŒFrecover a hot spare is being built to replace a failed/missing device ”h]”(hè)”}”(hŒrecover”h]”hŒrecover”…””}”(hjlh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M¡hjhubhø)”}”(hhh]”hý)”}”(hŒ=a hot spare is being built to replace a failed/missing device”h]”hŒ=a hot spare is being built to replace a failed/missing device”…””}”(hj}h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M hjzubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjhubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M¡hj6ubhâ)”}”(hŒidle nothing is happening”h]”(hè)”}”(hŒidle”h]”hŒidle”…””}”(hj›h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M£hj—ubhø)”}”(hhh]”hý)”}”(hŒnothing is happening”h]”hŒnothing is happening”…””}”(hj¬h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M¤hj©ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj—ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M£hj6ubhâ)”}”(hŒ˜check A full check of redundancy was requested and is happening. This reads all blocks and checks them. A repair may also happen for some raid levels. ”h]”(hè)”}”(hŒcheck”h]”hŒcheck”…””}”(hjÊh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M©hjÆubhø)”}”(hhh]”hý)”}”(hŒ‘A full check of redundancy was requested and is happening. This reads all blocks and checks them. A repair may also happen for some raid levels.”h]”hŒ‘A full check of redundancy was requested and is happening. This reads all blocks and checks them. A repair may also happen for some raid levels.”…””}”(hjÛh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M¦hjØubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjÆubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M©hj6ubhâ)”}”(hŒrepair A full check and repair is happening. This is similar to ``resync``, but was requested by the user, and the write-intent bitmap is NOT used to optimise the process. ”h]”(hè)”}”(hŒrepair”h]”hŒrepair”…””}”(hjùh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M¯hjõubhø)”}”(hhh]”hý)”}”(hŒ¥A full check and repair is happening. This is similar to ``resync``, but was requested by the user, and the write-intent bitmap is NOT used to optimise the process.”h]”(hŒ:A full check and repair is happening. This is similar to ”…””}”(hj h²hh³Nh´Nubj˜)”}”(hŒ ``resync``”h]”hŒresync”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj ubhŒa, but was requested by the user, and the write-intent bitmap is NOT used to optimise the process.”…””}”(hj h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M¬hjubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjõubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M¯hj6ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhj2ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙh³hÊh´M›hj.ubhý)”}”(hŒ]This file is writable, and each of the strings that could be read are meaningful for writing.”h]”hŒ]This file is writable, and each of the strings that could be read are meaningful for writing.”…””}”(hjBh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M±hj.ubjÚ)”}”(hX–``idle`` will stop an active resync/recovery etc. There is no guarantee that another resync/recovery may not be automatically started again, though some event will be needed to trigger this. ``resync`` or ``recovery`` can be used to restart the corresponding operation if it was stopped with ``idle``. ``check`` and ``repair`` will start the appropriate process providing the current state is ``idle``. ”h]”(hý)”}”(hŒ¿``idle`` will stop an active resync/recovery etc. There is no guarantee that another resync/recovery may not be automatically started again, though some event will be needed to trigger this.”h]”(j˜)”}”(hŒ``idle``”h]”hŒidle”…””}”(hjXh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjTubhŒ· will stop an active resync/recovery etc. There is no guarantee that another resync/recovery may not be automatically started again, though some event will be needed to trigger this.”…””}”(hjTh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M´hjPubhý)”}”(hŒn``resync`` or ``recovery`` can be used to restart the corresponding operation if it was stopped with ``idle``.”h]”(j˜)”}”(hŒ ``resync``”h]”hŒresync”…””}”(hjth²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjpubhŒ or ”…””}”(hjph²hh³Nh´Nubj˜)”}”(hŒ``recovery``”h]”hŒrecovery”…””}”(hj†h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjpubhŒK can be used to restart the corresponding operation if it was stopped with ”…””}”(hjph²hh³Nh´Nubj˜)”}”(hŒ``idle``”h]”hŒidle”…””}”(hj˜h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjpubhŒ.”…””}”(hjph²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M¹hjPubhý)”}”(hŒd``check`` and ``repair`` will start the appropriate process providing the current state is ``idle``.”h]”(j˜)”}”(hŒ ``check``”h]”hŒcheck”…””}”(hj´h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj°ubhŒ and ”…””}”(hj°h²hh³Nh´Nubj˜)”}”(hŒ ``repair``”h]”hŒrepair”…””}”(hjÆh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj°ubhŒC will start the appropriate process providing the current state is ”…””}”(hj°h²hh³Nh´Nubj˜)”}”(hŒ``idle``”h]”hŒidle”…””}”(hjØh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj°ubhŒ.”…””}”(hj°h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M¼hjPubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÙh³hÊh´M´hj.ubhý)”}”(hXThis file responds to select/poll. Any important change in the value triggers a poll event. Sometimes the value will briefly be ``recover`` if a recovery seems to be needed, but cannot be achieved. In that case, the transition to ``recover`` isn't notified, but the transition away is.”h]”(hŒ‚This file responds to select/poll. Any important change in the value triggers a poll event. Sometimes the value will briefly be ”…””}”(hjöh²hh³Nh´Nubj˜)”}”(hŒ``recover``”h]”hŒrecover”…””}”(hjþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjöubhŒ[ if a recovery seems to be needed, but cannot be achieved. In that case, the transition to ”…””}”(hjöh²hh³Nh´Nubj˜)”}”(hŒ``recover``”h]”hŒrecover”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjöubhŒ. isnâ€™t notified, but the transition away is.”…””}”(hjöh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M¿hj.ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÙh³hÊh´M›hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MÃhjubhâ)”}”(hX(degraded This contains a count of the number of devices by which the arrays is degraded. So an optimal array will show ``0``. A single failed/missing drive will show ``1``, etc. This file responds to select/poll, any increase or decrease in the count of missing devices will trigger an event. ”h]”(hè)”}”(hŒdegraded”h]”hŒdegraded”…””}”(hj>h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MËhj:ubhø)”}”(hhh]”(hý)”}”(hŒªThis contains a count of the number of devices by which the arrays is degraded. So an optimal array will show ``0``. A single failed/missing drive will show ``1``, etc.”h]”(hŒoThis contains a count of the number of devices by which the arrays is degraded. So an optimal array will show ”…””}”(hjOh²hh³Nh´Nubj˜)”}”(hŒ``0``”h]”hŒ0”…””}”(hjWh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjOubhŒ+. A single failed/missing drive will show ”…””}”(hjOh²hh³Nh´Nubj˜)”}”(hŒ``1``”h]”hŒ1”…””}”(hjih²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjOubhŒ, etc.”…””}”(hjOh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MÆhjLubhý)”}”(hŒrThis file responds to select/poll, any increase or decrease in the count of missing devices will trigger an event.”h]”hŒrThis file responds to select/poll, any increase or decrease in the count of missing devices will trigger an event.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MÊhjLubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj:ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MËhjubhâ)”}”(hX·mismatch_count When performing ``check`` and ``repair``, and possibly when performing ``resync``, md will count the number of errors that are found. The count in ``mismatch_cnt`` is the number of sectors that were re-written, or (for ``check``) would have been re-written. As most raid levels work in units of pages rather than sectors, this may be larger than the number of actual errors by a factor of the number of sectors in a page. ”h]”(hè)”}”(hŒmismatch_count”h]”hŒmismatch_count”…””}”(hjŸh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MÔhj›ubhø)”}”(hhh]”hý)”}”(hX§When performing ``check`` and ``repair``, and possibly when performing ``resync``, md will count the number of errors that are found. The count in ``mismatch_cnt`` is the number of sectors that were re-written, or (for ``check``) would have been re-written. As most raid levels work in units of pages rather than sectors, this may be larger than the number of actual errors by a factor of the number of sectors in a page.”h]”(hŒWhen performing ”…””}”(hj°h²hh³Nh´Nubj˜)”}”(hŒ ``check``”h]”hŒcheck”…””}”(hj¸h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj°ubhŒ and ”…””}”(hj°h²hh³Nh´Nubj˜)”}”(hŒ ``repair``”h]”hŒrepair”…””}”(hjÊh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj°ubhŒ, and possibly when performing ”…””}”(hj°h²hh³Nh´Nubj˜)”}”(hŒ ``resync``”h]”hŒresync”…””}”(hjÜh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj°ubhŒC, md will count the number of errors that are found. The count in ”…””}”(hj°h²hh³Nh´Nubj˜)”}”(hŒ``mismatch_cnt``”h]”hŒmismatch_cnt”…””}”(hjîh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj°ubhŒ8 is the number of sectors that were re-written, or (for ”…””}”(hj°h²hh³Nh´Nubj˜)”}”(hŒ ``check``”h]”hŒcheck”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj°ubhŒÂ) would have been re-written. As most raid levels work in units of pages rather than sectors, this may be larger than the number of actual errors by a factor of the number of sectors in a page.”…””}”(hj°h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MÎhjubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj›ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MÔhjubhâ)”}”(hX˜bitmap_set_bits If the array has a write-intent bitmap, then writing to this attribute can set bits in the bitmap, indicating that a resync would need to check the corresponding blocks. Either individual numbers or start-end pairs can be written. Multiple numbers can be separated by a space. Note that the numbers are ``bit`` numbers, not ``block`` numbers. They should be scaled by the bitmap_chunksize. ”h]”(hè)”}”(hŒbitmap_set_bits”h]”hŒbitmap_set_bits”…””}”(hj( h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´MÞhj$ ubhø)”}”(hhh]”(hý)”}”(hXIf the array has a write-intent bitmap, then writing to this attribute can set bits in the bitmap, indicating that a resync would need to check the corresponding blocks. Either individual numbers or start-end pairs can be written. Multiple numbers can be separated by a space.”h]”hXIf the array has a write-intent bitmap, then writing to this attribute can set bits in the bitmap, indicating that a resync would need to check the corresponding blocks. Either individual numbers or start-end pairs can be written. Multiple numbers can be separated by a space.”…””}”(hj9 h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M×hj6 ubhý)”}”(hŒpNote that the numbers are ``bit`` numbers, not ``block`` numbers. They should be scaled by the bitmap_chunksize.”h]”(hŒNote that the numbers are ”…””}”(hjG h²hh³Nh´Nubj˜)”}”(hŒ``bit``”h]”hŒbit”…””}”(hjO h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjG ubhŒ numbers, not ”…””}”(hjG h²hh³Nh´Nubj˜)”}”(hŒ ``block``”h]”hŒblock”…””}”(hja h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjG ubhŒ8 numbers. They should be scaled by the bitmap_chunksize.”…””}”(hjG h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MÝhj6 ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj$ ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´MÞhjubhâ)”}”(hXìsync_speed_min, sync_speed_max These are similar to ``/proc/sys/dev/raid/speed_limit_{min,max}`` however they only apply to the particular array. If no value has been written to these, or if the word ``system`` is written, then the system-wide value is used. If a value, in kibibytes-per-second is written, then it is used. When the files are read, they show the currently active value followed by ``(local)`` or ``(system)`` depending on whether it is a locally set or system-wide value. ”h]”(hè)”}”(hŒsync_speed_min, sync_speed_max”h]”hŒsync_speed_min, sync_speed_max”…””}”(hj‰ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mêhj… ubhø)”}”(hhh]”(hý)”}”(hŒrThese are similar to ``/proc/sys/dev/raid/speed_limit_{min,max}`` however they only apply to the particular array.”h]”(hŒThese are similar to ”…””}”(hjš h²hh³Nh´Nubj˜)”}”(hŒ,``/proc/sys/dev/raid/speed_limit_{min,max}``”h]”hŒ(/proc/sys/dev/raid/speed_limit_{min,max}”…””}”(hj¢ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjš ubhŒ1 however they only apply to the particular array.”…””}”(hjš h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Máhj— ubhý)”}”(hŒ²If no value has been written to these, or if the word ``system`` is written, then the system-wide value is used. If a value, in kibibytes-per-second is written, then it is used.”h]”(hŒ6If no value has been written to these, or if the word ”…””}”(hjº h²hh³Nh´Nubj˜)”}”(hŒ ``system``”h]”hŒsystem”…””}”(hjÂ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjº ubhŒr is written, then the system-wide value is used. If a value, in kibibytes-per-second is written, then it is used.”…””}”(hjº h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mähj— ubhý)”}”(hŒ¤When the files are read, they show the currently active value followed by ``(local)`` or ``(system)`` depending on whether it is a locally set or system-wide value.”h]”(hŒJWhen the files are read, they show the currently active value followed by ”…””}”(hjÚ h²hh³Nh´Nubj˜)”}”(hŒ``(local)``”h]”hŒ(local)”…””}”(hjâ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjÚ ubhŒ or ”…””}”(hjÚ h²hh³Nh´Nubj˜)”}”(hŒ``(system)``”h]”hŒ(system)”…””}”(hjô h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjÚ ubhŒ? depending on whether it is a locally set or system-wide value.”…””}”(hjÚ h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mèhj— ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj… ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mêhjubhâ)”}”(hXÅsync_completed This shows the number of sectors that have been completed of whatever the current sync_action is, followed by the number of sectors in total that could need to be processed. The two numbers are separated by a ``/`` thus effectively showing one value, a fraction of the process that is complete. A ``select`` on this attribute will return when resync completes, when it reaches the current sync_max (below) and possibly at other times. ”h]”(hè)”}”(hŒsync_completed”h]”hŒsync_completed”…””}”(hj!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mõhj!ubhø)”}”(hhh]”(hý)”}”(hX(This shows the number of sectors that have been completed of whatever the current sync_action is, followed by the number of sectors in total that could need to be processed. The two numbers are separated by a ``/`` thus effectively showing one value, a fraction of the process that is complete.”h]”(hŒÒThis shows the number of sectors that have been completed of whatever the current sync_action is, followed by the number of sectors in total that could need to be processed. The two numbers are separated by a ”…””}”(hj-!h²hh³Nh´Nubj˜)”}”(hŒ``/``”h]”hŒ/”…””}”(hj5!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hj-!ubhŒQ thus effectively showing one value, a fraction of the process that is complete.”…””}”(hj-!h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Míhj*!ubhý)”}”(hŒ‹A ``select`` on this attribute will return when resync completes, when it reaches the current sync_max (below) and possibly at other times.”h]”(hŒA ”…””}”(hjM!h²hh³Nh´Nubj˜)”}”(hŒ ``select``”h]”hŒselect”…””}”(hjU!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjM!ubhŒ on this attribute will return when resync completes, when it reaches the current sync_max (below) and possibly at other times.”…””}”(hjM!h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Móhj*!ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj!ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mõhjubhâ)”}”(hŒ€sync_speed This shows the current actual speed, in K/sec, of the current sync_action. It is averaged over the last 30 seconds. ”h]”(hè)”}”(hŒ sync_speed”h]”hŒ sync_speed”…””}”(hj}!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mùhjy!ubhø)”}”(hhh]”hý)”}”(hŒtThis shows the current actual speed, in K/sec, of the current sync_action. It is averaged over the last 30 seconds.”h]”hŒtThis shows the current actual speed, in K/sec, of the current sync_action. It is averaged over the last 30 seconds.”…””}”(hjŽ!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Møhj‹!ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjy!ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mùhjubhâ)”}”(hŒ±suspend_lo, suspend_hi The two values, given as numbers of sectors, indicate a range within the array where IO will be blocked. This is currently only supported for raid4/5/6. ”h]”(hè)”}”(hŒsuspend_lo, suspend_hi”h]”hŒsuspend_lo, suspend_hi”…””}”(hj¬!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mþhj¨!ubhø)”}”(hhh]”hý)”}”(hŒ™The two values, given as numbers of sectors, indicate a range within the array where IO will be blocked. This is currently only supported for raid4/5/6.”h]”hŒ™The two values, given as numbers of sectors, indicate a range within the array where IO will be blocked. This is currently only supported for raid4/5/6.”…””}”(hj½!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mühjº!ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj¨!ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mþhjubhâ)”}”(hXvsync_min, sync_max The two values, given as numbers of sectors, indicate a range within the array where ``check``/``repair`` will operate. Must be a multiple of chunk_size. When it reaches ``sync_max`` it will pause, rather than complete. You can use ``select`` or ``poll`` on ``sync_completed`` to wait for that number to reach sync_max. Then you can either increase ``sync_max``, or can write ``idle`` to ``sync_action``. The value of ``max`` for ``sync_max`` effectively disables the limit. When a resync is active, the value can only ever be increased, never decreased. The value of ``0`` is the minimum for ``sync_min``. ”h]”(hè)”}”(hŒsync_min, sync_max”h]”hŒsync_min, sync_max”…””}”(hjÛ!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mhj×!ubhø)”}”(hhh]”(hý)”}”(hX•The two values, given as numbers of sectors, indicate a range within the array where ``check``/``repair`` will operate. Must be a multiple of chunk_size. When it reaches ``sync_max`` it will pause, rather than complete. You can use ``select`` or ``poll`` on ``sync_completed`` to wait for that number to reach sync_max. Then you can either increase ``sync_max``, or can write ``idle`` to ``sync_action``.”h]”(hŒUThe two values, given as numbers of sectors, indicate a range within the array where ”…””}”(hjì!h²hh³Nh´Nubj˜)”}”(hŒ ``check``”h]”hŒcheck”…””}”(hjô!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjì!ubhŒ/”…””}”(hjì!h²hh³Nh´Nubj˜)”}”(hŒ ``repair``”h]”hŒrepair”…””}”(hj"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjì!ubhŒA will operate. Must be a multiple of chunk_size. When it reaches ”…””}”(hjì!h²hh³Nh´Nubj˜)”}”(hŒ``sync_max``”h]”hŒsync_max”…””}”(hj"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjì!ubhŒ2 it will pause, rather than complete. You can use ”…””}”(hjì!h²hh³Nh´Nubj˜)”}”(hŒ ``select``”h]”hŒselect”…””}”(hj*"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjì!ubhŒ or ”…””}”(hjì!h²hh³Nh´Nubj˜)”}”(hŒ``poll``”h]”hŒpoll”…””}”(hj<"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjì!ubhŒ on ”…””}”(hjì!h²hh³Nh´Nubj˜)”}”(hŒ``sync_completed``”h]”hŒsync_completed”…””}”(hjN"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjì!ubhŒJ to wait for that number to reach sync_max. Then you can either increase ”…””}”(hjì!h²hh³Nh´Nubj˜)”}”(hŒ``sync_max``”h]”hŒsync_max”…””}”(hj`"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjì!ubhŒ, or can write ”…””}”(hjì!h²hh³Nh´Nubj˜)”}”(hŒ``idle``”h]”hŒidle”…””}”(hjr"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjì!ubhŒ to ”…””}”(hjì!h²hh³Nh´Nubj˜)”}”(hŒ``sync_action``”h]”hŒsync_action”…””}”(hj„"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjì!ubhŒ.”…””}”(hjì!h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mhjé!ubhý)”}”(hŒÉThe value of ``max`` for ``sync_max`` effectively disables the limit. When a resync is active, the value can only ever be increased, never decreased. The value of ``0`` is the minimum for ``sync_min``.”h]”(hŒ The value of ”…””}”(hjœ"h²hh³Nh´Nubj˜)”}”(hŒ``max``”h]”hŒmax”…””}”(hj¤"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjœ"ubhŒ for ”…””}”(hjœ"h²hh³Nh´Nubj˜)”}”(hŒ``sync_max``”h]”hŒsync_max”…””}”(hj¶"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjœ"ubhŒ~ effectively disables the limit. When a resync is active, the value can only ever be increased, never decreased. The value of ”…””}”(hjœ"h²hh³Nh´Nubj˜)”}”(hŒ``0``”h]”hŒ0”…””}”(hjÈ"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjœ"ubhŒ is the minimum for ”…””}”(hjœ"h²hh³Nh´Nubj˜)”}”(hŒ``sync_min``”h]”hŒsync_min”…””}”(hjÚ"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j—hjœ"ubhŒ.”…””}”(hjœ"h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M hjé!ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj×!ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙh³hÊh´M—hjZh²hubhý)”}”(hŒ×Each active md device may also have attributes specific to the personality module that manages it. These are specific to the implementation of the module and could change substantially if the implementation changes.”h]”hŒ×Each active md device may also have attributes specific to the personality module that manages it. These are specific to the implementation of the module and could change substantially if the implementation changes.”…””}”(hj #h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MhjZh²hubhý)”}”(hŒThese currently include:”h]”hŒThese currently include:”…””}”(hj#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´MhjZh²hubjÚ)”}”(hX–stripe_cache_size (currently raid5 only) number of entries in the stripe cache. This is writable, but there are upper and lower limits (32768, 17). Default is 256. strip_cache_active (currently raid5 only) number of active entries in the stripe cache preread_bypass_threshold (currently raid5 only) number of times a stripe requiring preread will be bypassed by a stripe that does not require preread. For fairness defaults to 1. Setting this to 0 disables bypass accounting and requires preread stripes to wait until all full-width stripe- writes are complete. Valid values are 0 to stripe_cache_size. journal_mode (currently raid5 only) The cache mode for raid5. raid5 could include an extra disk for caching. The mode can be "write-through" or "write-back". The default is "write-through". ppl_write_hint NVMe stream ID to be set for each PPL write request.”h]”hÝ)”}”(hhh]”(hâ)”}”(hŒ§stripe_cache_size (currently raid5 only) number of entries in the stripe cache. This is writable, but there are upper and lower limits (32768, 17). Default is 256. ”h]”(hè)”}”(hŒ)stripe_cache_size (currently raid5 only)”h]”hŒ)stripe_cache_size (currently raid5 only)”…””}”(hj1#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mhj-#ubhø)”}”(hhh]”hý)”}”(hŒ|number of entries in the stripe cache. This is writable, but there are upper and lower limits (32768, 17). Default is 256.”h]”hŒ|number of entries in the stripe cache. This is writable, but there are upper and lower limits (32768, 17). Default is 256.”…””}”(hjB#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mhj?#ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj-#ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhj*#ubhâ)”}”(hŒWstrip_cache_active (currently raid5 only) number of active entries in the stripe cache ”h]”(hè)”}”(hŒ)strip_cache_active (currently raid5 only)”h]”hŒ)strip_cache_active (currently raid5 only)”…””}”(hj`#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´Mhj\#ubhø)”}”(hhh]”hý)”}”(hŒ,number of active entries in the stripe cache”h]”hŒ,number of active entries in the stripe cache”…””}”(hjq#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mhjn#ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj\#ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´Mhj*#ubhâ)”}”(hXcpreread_bypass_threshold (currently raid5 only) number of times a stripe requiring preread will be bypassed by a stripe that does not require preread. For fairness defaults to 1. Setting this to 0 disables bypass accounting and requires preread stripes to wait until all full-width stripe- writes are complete. Valid values are 0 to stripe_cache_size. ”h]”(hè)”}”(hŒ/preread_bypass_threshold (currently raid5 only)”h]”hŒ/preread_bypass_threshold (currently raid5 only)”…””}”(hj#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M#hj‹#ubhø)”}”(hhh]”hý)”}”(hX2number of times a stripe requiring preread will be bypassed by a stripe that does not require preread. For fairness defaults to 1. Setting this to 0 disables bypass accounting and requires preread stripes to wait until all full-width stripe- writes are complete. Valid values are 0 to stripe_cache_size.”h]”hX2number of times a stripe requiring preread will be bypassed by a stripe that does not require preread. For fairness defaults to 1. Setting this to 0 disables bypass accounting and requires preread stripes to wait until all full-width stripe- writes are complete. Valid values are 0 to stripe_cache_size.”…””}”(hj #h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´Mhj#ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hj‹#ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M#hj*#ubhâ)”}”(hŒ¾journal_mode (currently raid5 only) The cache mode for raid5. raid5 could include an extra disk for caching. The mode can be "write-through" or "write-back". The default is "write-through". ”h]”(hè)”}”(hŒ#journal_mode (currently raid5 only)”h]”hŒ#journal_mode (currently raid5 only)”…””}”(hj¾#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M(hjº#ubhø)”}”(hhh]”hý)”}”(hŒ™The cache mode for raid5. raid5 could include an extra disk for caching. The mode can be "write-through" or "write-back". The default is "write-through".”h]”hŒ¥The cache mode for raid5. raid5 could include an extra disk for caching. The mode can be â€œwrite-throughâ€ or â€œwrite-backâ€. The default is â€œwrite-throughâ€.”…””}”(hjÏ#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M&hjÌ#ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjº#ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M(hj*#ubhâ)”}”(hŒCppl_write_hint NVMe stream ID to be set for each PPL write request.”h]”(hè)”}”(hŒppl_write_hint”h]”hŒppl_write_hint”…””}”(hjí#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hçh³hÊh´M*hjé#ubhø)”}”(hhh]”hý)”}”(hŒ4NVMe stream ID to be set for each PPL write request.”h]”hŒ4NVMe stream ID to be set for each PPL write request.”…””}”(hjþ#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hüh³hÊh´M+hjû#ubah}”(h]”h ]”h"]”h$]”h&]”uh1h÷hjé#ubeh}”(h]”h ]”h"]”h$]”h&]”uh1háh³hÊh´M*hj*#ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhj&#ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙh³hÊh´MhjZh²hubeh}”(h]”Œmd-devices-in-sysfs”ah ]”h"]”Œmd devices in sysfs”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kµubeh}”(h]”Œraid-arrays”ah ]”h"]”Œraid arrays”ah$]”h&]”uh1hµhhh²hh³hÊh´Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”hÊuh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(hºNŒ generator”NŒ datestamp”NŒsource_link”NŒ source_url”NŒ toc_backlinks”jäŒfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒreport_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jV$Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”hÊŒ_destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j1$j.$jªj§jYjVj}jzj»j¸jëjèj¢jŸjjj¦j£jjjÞjÛjWjTj)$j&$uŒ nametypes”}”(j1$‰jª‰jY‰j}‰j»‰jë‰j¢‰j‰j¦‰j‰jÞ‰jW‰j)$‰uh}”(j.$h·j§hËjVjjzj\j¸j€jèj¾jŸjîjjj£jjj©jÛj"jTjáj&$jZuŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ decoration”Nh²hub.