<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/Documentation/admin-guide/device-mapper, branch v5.8</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v5.8</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v5.8'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2020-06-19T16:21:56Z</updated>
<entry>
<title>docs: device-mapper: add dm-ebs.rst to an index file</title>
<updated>2020-06-19T16:21:56Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
<email>mchehab+huawei@kernel.org</email>
</author>
<published>2020-06-15T06:47:00Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=e0034433a7e4f1d74e86fe801f7c017b48f81315'/>
<id>urn:sha1:e0034433a7e4f1d74e86fe801f7c017b48f81315</id>
<content type='text'>
Solves this Sphinx warning:
	Documentation/admin-guide/device-mapper/dm-ebs.rst: WARNING: document isn't included in any toctree

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
Signed-off-by: Mike Snitzer &lt;snitzer@redhat.com&gt;
</content>
</entry>
<entry>
<title>dm integrity: add status line documentation</title>
<updated>2020-06-05T18:59:40Z</updated>
<author>
<name>Mikulas Patocka</name>
<email>mpatocka@redhat.com</email>
</author>
<published>2020-06-02T13:48:10Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=40e9c5ac4e3d670799a247944c330e5126935a7c'/>
<id>urn:sha1:40e9c5ac4e3d670799a247944c330e5126935a7c</id>
<content type='text'>
Signed-off-by: Mikulas Patocka &lt;mpatocka@redhat.com&gt;
Signed-off-by: Mike Snitzer &lt;snitzer@redhat.com&gt;
</content>
</entry>
<entry>
<title>dm zoned: metadata version 2</title>
<updated>2020-05-20T21:09:43Z</updated>
<author>
<name>Hannes Reinecke</name>
<email>hare@suse.de</email>
</author>
<published>2020-05-11T08:24:30Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=bd5c40313a1467e4683d92456fc5219d94823f24'/>
<id>urn:sha1:bd5c40313a1467e4683d92456fc5219d94823f24</id>
<content type='text'>
Implement handling for metadata version 2. The new metadata adds a
label and UUID for the device mapper device, and additional UUID for
the underlying block devices.

It also allows for an additional regular drive to be used for
emulating random access zones. The emulated zones will be placed
logically in front of the zones from the zoned block device, causing
the superblocks and metadata to be stored on that device.

The first zone of the original zoned device will be used to hold
another, tertiary copy of the metadata; this copy carries a generation
number of 0 and is never updated; it's just used for identification.

Signed-off-by: Hannes Reinecke &lt;hare@suse.de&gt;
Reviewed-by: Bob Liu &lt;bob.liu@oracle.com&gt;
Reviewed-by: Damien Le Moal &lt;damien.lemoal@wdc.com&gt;
Signed-off-by: Mike Snitzer &lt;snitzer@redhat.com&gt;
</content>
</entry>
<entry>
<title>dm zoned: add 'message' callback</title>
<updated>2020-05-15T14:29:36Z</updated>
<author>
<name>Hannes Reinecke</name>
<email>hare@suse.de</email>
</author>
<published>2020-05-11T08:24:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=90b39d58f39e1f3f3147caee6fb2a71528db74a2'/>
<id>urn:sha1:90b39d58f39e1f3f3147caee6fb2a71528db74a2</id>
<content type='text'>
Add callback for 'dmsetup message' to allow the reclaim process
to be triggered manually.
Eg.

	dmsetup message /dev/dm-X 0 message

will start the reclaim process even if the default threshold
of 50 percent of free random zones is not reached.

Signed-off-by: Hannes Reinecke &lt;hare@suse.de&gt;
Reviewed-by: Bob Liu &lt;bob.liu@oracle.com&gt;
Reviewed-by: Damien Le Moal &lt;damien.lemoal@wdc.com&gt;
Signed-off-by: Mike Snitzer &lt;snitzer@redhat.com&gt;
</content>
</entry>
<entry>
<title>dm zoned: add 'status' callback</title>
<updated>2020-05-15T14:29:36Z</updated>
<author>
<name>Hannes Reinecke</name>
<email>hare@suse.de</email>
</author>
<published>2020-05-11T08:24:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=bc3d5717d242a37d2e9ea85d7e7b2e3569324d24'/>
<id>urn:sha1:bc3d5717d242a37d2e9ea85d7e7b2e3569324d24</id>
<content type='text'>
Add callback to supply information for 'dmsetup status'
and 'dmsetup table'. The output for 'dmsetup status' is

0 &lt;size&gt; zoned &lt;nr_zones&gt; zones &lt;nr_unmap_rnd&gt;/&lt;nr_rnd&gt; random &lt;nr_unmap_seq&gt;/&lt;nr_seq&gt; sequential

where &lt;nr_unmap_rnd&gt; is the number of unmapped (ie free) random zones,
&lt;nr_rnd&gt; the total number of random zones, &lt;nr_unmap_seq&gt; the number
of unmapped sequential zones, and &lt;nr_seq&gt; the total number of
sequential zones.

Signed-off-by: Hannes Reinecke &lt;hare@suse.de&gt;
Reviewed-by: Bob Liu &lt;bob.liu@oracle.com&gt;
Reviewed-by: Damien Le Moal &lt;damien.lemoal@wdc.com&gt;
Signed-off-by: Mike Snitzer &lt;snitzer@redhat.com&gt;
</content>
</entry>
<entry>
<title>dm: add emulated block size target</title>
<updated>2020-05-15T14:29:35Z</updated>
<author>
<name>Heinz Mauelshagen</name>
<email>heinzm@redhat.com</email>
</author>
<published>2020-03-09T22:26:38Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d3c7b35c20d60650bac8b55c17b194adda03a979'/>
<id>urn:sha1:d3c7b35c20d60650bac8b55c17b194adda03a979</id>
<content type='text'>
This new target is similar to the linear target except that it emulates
a smaller logical block size on a device with a larger logical block
size.  Its main purpose is to emulate 512 byte sectors on 4K native
disks (i.e. 512e).

See Documentation/admin-guide/device-mapper/dm-ebs.rst for details.

Reviewed-by: Damien Le Moal &lt;DamienLeMoal@wdc.com&gt;
Signed-off-by: Heinz Mauelshagen &lt;heinzm@redhat.com&gt;
Signed-off-by: Randy Dunlap &lt;rdunlap@infradead.org&gt; [Kconfig fixes]
Signed-off-by: Zheng Bin &lt;zhengbin13@huawei.com&gt; [static fixes]
Signed-off-by: Mike Snitzer &lt;snitzer@redhat.com&gt;
</content>
</entry>
<entry>
<title>dm integrity: document allow_discard option</title>
<updated>2020-04-14T17:54:07Z</updated>
<author>
<name>Milan Broz</name>
<email>gmazyland@gmail.com</email>
</author>
<published>2020-04-08T21:40:08Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=0a2bd55c194ae8322638aceb4cc276cbf8b2f8b9'/>
<id>urn:sha1:0a2bd55c194ae8322638aceb4cc276cbf8b2f8b9</id>
<content type='text'>
Add decription of the allow_discard option added in commit
84597a44a9d86ac949900441cea7da0af0f2f473.

Signed-off-by: Milan Broz &lt;gmazyland@gmail.com&gt;
Signed-off-by: Mike Snitzer &lt;snitzer@redhat.com&gt;
</content>
</entry>
<entry>
<title>dm raid: table line rebuild status fixes</title>
<updated>2020-01-07T16:43:37Z</updated>
<author>
<name>Heinz Mauelshagen</name>
<email>heinzm@redhat.com</email>
</author>
<published>2019-12-19T16:58:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=43f3952a51f8198d365acb7f51fe42d578fe5d0a'/>
<id>urn:sha1:43f3952a51f8198d365acb7f51fe42d578fe5d0a</id>
<content type='text'>
raid_status() wasn't emitting rebuild flags on the table line properly
because the rdev number was not yet set properly; index raid component
devices array directly to solve.

Also fix wrong argument count on emitted table line caused by 1 too
many rebuild/write_mostly argument and consider any journal_(dev|mode)
pairs.

Link: https://bugzilla.redhat.com/1782045
Signed-off-by: Heinz Mauelshagen &lt;heinzm@redhat.com&gt;
Signed-off-by: Mike Snitzer &lt;snitzer@redhat.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'for-5.5/dm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm</title>
<updated>2019-12-13T22:13:15Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2019-12-13T22:13:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=15da849c910da05622c75c5741dd6e176a8b6fe2'/>
<id>urn:sha1:15da849c910da05622c75c5741dd6e176a8b6fe2</id>
<content type='text'>
Pull device mapper fixes from Mike Snitzer:

 - Fix DM multipath by restoring full path selector functionality for
   bio-based configurations that don't haave a SCSI device handler.

 - Fix dm-btree removal to ensure non-root btree nodes have at least
   (max_entries / 3) entries. This resolves userspace thin_check
   utility's report of "too few entries in btree_node".

 - Fix both the DM thin-provisioning and dm-clone targets to properly
   flush the data device prior to metadata commit. This resolves the
   potential for inconsistency across a power loss event when the data
   device has a volatile writeback cache.

 - Small documentation fixes to dm-clone and dm-integrity.

* tag 'for-5.5/dm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm:
  docs: dm-integrity: remove reference to ARC4
  dm thin: Flush data device before committing metadata
  dm thin metadata: Add support for a pre-commit callback
  dm clone: Flush destination device before committing metadata
  dm clone metadata: Use a two phase commit
  dm clone metadata: Track exact changes per transaction
  dm btree: increase rebalance threshold in __rebalance2()
  dm: add dm-clone to the documentation index
  dm mpath: remove harmful bio-based optimization
</content>
</entry>
<entry>
<title>docs: dm-integrity: remove reference to ARC4</title>
<updated>2019-12-10T15:02:43Z</updated>
<author>
<name>Eric Biggers</name>
<email>ebiggers@google.com</email>
</author>
<published>2019-12-07T03:59:21Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=7fc979f8204fb763e203d3e716c17d352eb96b35'/>
<id>urn:sha1:7fc979f8204fb763e203d3e716c17d352eb96b35</id>
<content type='text'>
ARC4 is no longer considered secure, so it shouldn't be used, even as
just an example.

Signed-off-by: Eric Biggers &lt;ebiggers@google.com&gt;
Signed-off-by: Mike Snitzer &lt;snitzer@redhat.com&gt;
</content>
</entry>
</feed>
