€•_VŒ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”Œ8/translations/zh_CN/admin-guide/device-mapper/log-writes”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ8/translations/zh_TW/admin-guide/device-mapper/log-writes”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ8/translations/it_IT/admin-guide/device-mapper/log-writes”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ8/translations/ja_JP/admin-guide/device-mapper/log-writes”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ8/translations/ko_KR/admin-guide/device-mapper/log-writes”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ8/translations/pt_BR/admin-guide/device-mapper/log-writes”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ8/translations/sp_SP/admin-guide/device-mapper/log-writes”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ dm-log-writes”h]”hŒ dm-log-writes”…””}”(hh¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhh·h²hh³ŒR/var/lib/git/docbuild/linux/Documentation/admin-guide/device-mapper/log-writes.rst”h´KubhŒ paragraph”“”)”}”(hXúThis target takes 2 devices, one to pass all IO to normally, and one to log all of the write operations to. This is intended for file system developers wishing to verify the integrity of metadata or data as the file system is written to. There is a log_write_entry written for every WRITE request and the target is able to take arbitrary data from userspace to insert into the log. The data that is in the WRITE requests is copied into the log to make the replay happen exactly as it happened originally.”h]”hXúThis target takes 2 devices, one to pass all IO to normally, and one to log all of the write operations to. This is intended for file system developers wishing to verify the integrity of metadata or data as the file system is written to. There is a log_write_entry written for every WRITE request and the target is able to take arbitrary data from userspace to insert into the log. The data that is in the WRITE requests is copied into the log to make the replay happen exactly as it happened originally.”…””}”(hhÍh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khh·h²hubh¶)”}”(hhh]”(h»)”}”(hŒ Log Ordering”h]”hŒ Log Ordering”…””}”(hhÞh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhhÛh²hh³hÊh´KubhÌ)”}”(hXrWe log things in order of completion once we are sure the write is no longer in cache. This means that normal WRITE requests are not actually logged until the next REQ_PREFLUSH request. This is to make it easier for userspace to replay the log in a way that correlates to what is on disk and not what is in cache, to make it easier to detect improper waiting/flushing.”h]”hXrWe log things in order of completion once we are sure the write is no longer in cache. This means that normal WRITE requests are not actually logged until the next REQ_PREFLUSH request. This is to make it easier for userspace to replay the log in a way that correlates to what is on disk and not what is in cache, to make it easier to detect improper waiting/flushing.”…””}”(hhìh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KhhÛh²hubhÌ)”}”(hXÁThis works by attaching all WRITE requests to a list once the write completes. Once we see a REQ_PREFLUSH request we splice this list onto the request and once the FLUSH request completes we log all of the WRITEs and then the FLUSH. Only completed WRITEs, at the time the REQ_PREFLUSH is issued, are added in order to simulate the worst case scenario with regard to power failures. Consider the following example (W means write, C means complete):”h]”hXÁThis works by attaching all WRITE requests to a list once the write completes. Once we see a REQ_PREFLUSH request we splice this list onto the request and once the FLUSH request completes we log all of the WRITEs and then the FLUSH. Only completed WRITEs, at the time the REQ_PREFLUSH is issued, are added in order to simulate the worst case scenario with regard to power failures. Consider the following example (W means write, C means complete):”…””}”(hhúh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KhhÛh²hubhŒ block_quote”“”)”}”(hŒ W1,W2,W3,C3,C2,Wflush,C1,Cflush ”h]”hÌ)”}”(hŒW1,W2,W3,C3,C2,Wflush,C1,Cflush”h]”hŒW1,W2,W3,C3,C2,Wflush,C1,Cflush”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj ubah}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´KhhÛh²hubhÌ)”}”(hŒ!The log would show the following:”h]”hŒ!The log would show the following:”…””}”(hj"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KhhÛh²hubj )”}”(hŒW3,W2,flush,W1.... ”h]”hÌ)”}”(hŒW3,W2,flush,W1....”h]”hŒW3,W2,flush,W1....”…””}”(hj4h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K!hj0ubah}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´K!hhÛh²hubhÌ)”}”(hŒ°Again this is to simulate what is actually on disk, this allows us to detect cases where a power failure at a particular point in time would create an inconsistent file system.”h]”hŒ°Again this is to simulate what is actually on disk, this allows us to detect cases where a power failure at a particular point in time would create an inconsistent file system.”…””}”(hjHh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K#hhÛh²hubhÌ)”}”(hŒ•Any REQ_FUA requests bypass this flushing mechanism and are logged as soon as they complete as those requests will obviously bypass the device cache.”h]”hŒ•Any REQ_FUA requests bypass this flushing mechanism and are logged as soon as they complete as those requests will obviously bypass the device cache.”…””}”(hjVh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K'hhÛh²hubhÌ)”}”(hŒÈAny REQ_OP_DISCARD requests are treated like WRITE requests. Otherwise we would have all the DISCARD requests, and then the WRITE requests and then the FLUSH request. Consider the following example:”h]”hŒÈAny REQ_OP_DISCARD requests are treated like WRITE requests. Otherwise we would have all the DISCARD requests, and then the WRITE requests and then the FLUSH request. Consider the following example:”…””}”(hjdh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K*hhÛh²hubj )”}”(hŒ&WRITE block 1, DISCARD block 1, FLUSH ”h]”hÌ)”}”(hŒ%WRITE block 1, DISCARD block 1, FLUSH”h]”hŒ%WRITE block 1, DISCARD block 1, FLUSH”…””}”(hjvh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K.hjrubah}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´K.hhÛh²hubhÌ)”}”(hŒHIf we logged DISCARD when it completed, the replay would look like this:”h]”hŒHIf we logged DISCARD when it completed, the replay would look like this:”…””}”(hjŠh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K0hhÛh²hubj )”}”(hŒDISCARD 1, WRITE 1, FLUSH ”h]”hÌ)”}”(hŒDISCARD 1, WRITE 1, FLUSH”h]”hŒDISCARD 1, WRITE 1, FLUSH”…””}”(hjœh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K2hj˜ubah}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÊh´K2hhÛh²hubhÌ)”}”(hŒMwhich isn't quite what happened and wouldn't be caught during the log replay.”h]”hŒQwhich isn’t quite what happened and wouldn’t be caught during the log replay.”…””}”(hj°h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K4hhÛh²hubeh}”(h]”Œ log-ordering”ah ]”h"]”Œ log ordering”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kubh¶)”}”(hhh]”(h»)”}”(hŒTarget interface”h]”hŒTarget interface”…””}”(hjÉh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjÆh²hh³hÊh´K7ubhŒenumerated_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hX%Constructor log-writes ============= ============================================== dev_path Device that all of the IO will go to normally. log_dev_path Device where the log entries are written to. ============= ============================================== ”h]”(hÌ)”}”(hŒ Constructor”h]”hŒ Constructor”…””}”(hjâh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K9hjÞubhÌ)”}”(hŒ$log-writes ”h]”hŒ$log-writes ”…””}”(hjðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K;hjÞubhŒtable”“”)”}”(hhh]”hŒtgroup”“”)”}”(hhh]”(hŒcolspec”“”)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”K uh1jhjubj )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”K.uh1jhjubhŒtbody”“”)”}”(hhh]”(hŒrow”“”)”}”(hhh]”(hŒentry”“”)”}”(hhh]”hÌ)”}”(hŒdev_path”h]”hŒdev_path”…””}”(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Œ.Device that all of the IO will go to normally.”h]”hŒ.Device that all of the IO will go to normally.”…””}”(hjDh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K>hjAubah}”(h]”h ]”h"]”h$]”h&]”uh1j(hj%ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j#hj ubj$)”}”(hhh]”(j))”}”(hhh]”hÌ)”}”(hŒ log_dev_path”h]”hŒ log_dev_path”…””}”(hjdh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K?hjaubah}”(h]”h ]”h"]”h$]”h&]”uh1j(hj^ubj))”}”(hhh]”hÌ)”}”(hŒ,Device where the log entries are written to.”h]”hŒ,Device where the log entries are written to.”…””}”(hj{h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K?hjxubah}”(h]”h ]”h"]”h$]”h&]”uh1j(hj^ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j#hj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhjubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1jhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jþhjÞubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÜhjÙh²hh³hÊh´NubjÝ)”}”(hX Status <#logged entries> =========================== ======================== #logged entries Number of logged entries highest allocated sector Highest allocated sector =========================== ======================== ”h]”(hÌ)”}”(hŒStatus”h]”hŒStatus”…””}”(hj²h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KBhj®ubhÌ)”}”(hŒ,<#logged entries> ”h]”hŒ,<#logged entries> ”…””}”(hjÀh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KDhj®ubjÿ)”}”(hhh]”j)”}”(hhh]”(j )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1jhjÑubj )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1jhjÑubj)”}”(hhh]”(j$)”}”(hhh]”(j))”}”(hhh]”hÌ)”}”(hŒ#logged entries”h]”hŒ#logged entries”…””}”(hjñh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KGhjîubah}”(h]”h ]”h"]”h$]”h&]”uh1j(hjëubj))”}”(hhh]”hÌ)”}”(hŒNumber of logged entries”h]”hŒNumber of logged entries”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KGhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j(hjëubeh}”(h]”h ]”h"]”h$]”h&]”uh1j#hjèubj$)”}”(hhh]”(j))”}”(hhh]”hÌ)”}”(hŒhighest allocated sector”h]”hŒhighest allocated sector”…””}”(hj(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KHhj%ubah}”(h]”h ]”h"]”h$]”h&]”uh1j(hj"ubj))”}”(hhh]”hÌ)”}”(hŒHighest allocated sector”h]”hŒHighest allocated sector”…””}”(hj?h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KHhj<ubah}”(h]”h ]”h"]”h$]”h&]”uh1j(hj"ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j#hjèubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhjÑubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1jhjÎubah}”(h]”h ]”h"]”h$]”h&]”uh1jþhj®ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÜhjÙh²hh³hÊh´NubjÝ)”}”(hŒ Messages ”h]”hÌ)”}”(hŒMessages”h]”hŒMessages”…””}”(hjvh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KKhjrubah}”(h]”h ]”h"]”h$]”h&]”uh1jÜhjÙh²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œ lowerroman”Œprefix”hŒsuffix”Œ)”uh1j×hjÆh²hh³hÊh´K9ubj )”}”(hXimark You can use a dmsetup message to set an arbitrary mark in a log. For example say you want to fsck a file system after every write, but first you need to replay up to the mkfs to make sure we're fsck'ing something reasonable, you would do something like this:: mkfs.btrfs -f /dev/mapper/log dmsetup message log 0 mark mkfs This would allow you to replay the log up to the mkfs mark and then replay from that point on doing the fsck check in the interval that you want. Every log has a mark at the end labeled "dm-log-writes-end". ”h]”(hÌ)”}”(hŒmark ”h]”hŒmark ”…””}”(hj™h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KMhj•ubj )”}”(hX%You can use a dmsetup message to set an arbitrary mark in a log. For example say you want to fsck a file system after every write, but first you need to replay up to the mkfs to make sure we're fsck'ing something reasonable, you would do something like this:: mkfs.btrfs -f /dev/mapper/log dmsetup message log 0 mark mkfs This would allow you to replay the log up to the mkfs mark and then replay from that point on doing the fsck check in the interval that you want. Every log has a mark at the end labeled "dm-log-writes-end". ”h]”(hÌ)”}”(hXYou can use a dmsetup message to set an arbitrary mark in a log. For example say you want to fsck a file system after every write, but first you need to replay up to the mkfs to make sure we're fsck'ing something reasonable, you would do something like this::”h]”hXYou can use a dmsetup message to set an arbitrary mark in a log. For example say you want to fsck a file system after every write, but first you need to replay up to the mkfs to make sure we’re fsck’ing something reasonable, you would do something like this:”…””}”(hj«h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KOhj§ubhŒ literal_block”“”)”}”(hŒHmkfs.btrfs -f /dev/mapper/log dmsetup message log 0 mark mkfs ”h]”hŒHmkfs.btrfs -f /dev/mapper/log dmsetup message log 0 mark mkfs ”…””}”hj»sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1j¹h³hÊh´KUhj§ubhÌ)”}”(hŒ‘This would allow you to replay the log up to the mkfs mark and then replay from that point on doing the fsck check in the interval that you want.”h]”hŒ‘This would allow you to replay the log up to the mkfs mark and then replay from that point on doing the fsck check in the interval that you want.”…””}”(hjËh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KYhj§ubhÌ)”}”(hŒ dmsetup message log 0 mark fsync md5sum /mnt/btrfs-test/foo umount /mnt/btrfs-test dmsetup remove log replay-log --log /dev/sdc --replay /dev/sdb --end-mark fsync mount /dev/sdb /mnt/btrfs-test md5sum /mnt/btrfs-test/foo Another option is to do a complicated file system operation and verify the file system is consistent during the entire operation. You could do this with: TABLE="0 $(blockdev --getsz /dev/sdb) log-writes /dev/sdb /dev/sdc" dmsetup create log --table "$TABLE" mkfs.btrfs -f /dev/mapper/log dmsetup message log 0 mark mkfs mount /dev/mapper/log /mnt/btrfs-test btrfs filesystem balance /mnt/btrfs-test umount /mnt/btrfs-test dmsetup remove log replay-log --log /dev/sdc --replay /dev/sdb --end-mark mkfs btrfsck /dev/sdb replay-log --log /dev/sdc --replay /dev/sdb --start-mark mkfs \ --fsck "btrfsck /dev/sdb" --check fua”h]”hXTABLE="0 $(blockdev --getsz /dev/sdb) log-writes /dev/sdb /dev/sdc" dmsetup create log --table "$TABLE" mkfs.btrfs -f /dev/mapper/log dmsetup message log 0 mark mkfs mount /dev/mapper/log /mnt/btrfs-test dmsetup message log 0 mark fsync md5sum /mnt/btrfs-test/foo umount /mnt/btrfs-test dmsetup remove log replay-log --log /dev/sdc --replay /dev/sdb --end-mark fsync mount /dev/sdb /mnt/btrfs-test md5sum /mnt/btrfs-test/foo Another option is to do a complicated file system operation and verify the file system is consistent during the entire operation. You could do this with: TABLE="0 $(blockdev --getsz /dev/sdb) log-writes /dev/sdb /dev/sdc" dmsetup create log --table "$TABLE" mkfs.btrfs -f /dev/mapper/log dmsetup message log 0 mark mkfs mount /dev/mapper/log /mnt/btrfs-test btrfs filesystem balance /mnt/btrfs-test umount /mnt/btrfs-test dmsetup remove log replay-log --log /dev/sdc --replay /dev/sdb --end-mark mkfs btrfsck /dev/sdb replay-log --log /dev/sdc --replay /dev/sdb --start-mark mkfs \ --fsck "btrfsck /dev/sdb" --check fua”…””}”hjRsbah}”(h]”h ]”h"]”h$]”h&]”jÉjÊuh1j¹h³hÊh´Kkhj3h²hubhÌ)”}”(hŒÂAnd that will replay the log until it sees a FUA request, run the fsck command and if the fsck passes it will replay to the next FUA, until it is completed or the fsck command exists abnormally.”h]”hŒÂAnd that will replay the log until it sees a FUA request, run the fsck command and if the fsck passes it will replay to the next FUA, until it is completed or the fsck command exists abnormally.”…””}”(hj`h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj3h²hubeh}”(h]”Œ example-usage”ah ]”h"]”Œ example usage”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kfubeh}”(h]”Œ dm-log-writes”ah ]”h"]”Œ dm-log-writes”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”j Œ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”}”(j{jxjÃjÀjøjõj0j-jsjpuŒ nametypes”}”(j{‰jÉjø‰j0‰js‰uh}”(jxh·jÀhÛjõjÆj-jûjpj3uŒ 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.