Linux Device-Mapper Development

• Thread Index

• Re: dm-multipath: Accept failed paths for multipath maps
  • From: John Utz <John.Utz@xxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/15] block copy: initial XCOPY offload support
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/15] block copy: initial XCOPY offload support
  • From: Tomas Henzl <thenzl@xxxxxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH 5/5] libmultipath: Accept "*" as a valid regular expression
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH 4/5] libmultipath: Print line number for which parsing failed
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH 3/5] libmultipath: Zero-terminate sysfs_attr_get_value() result
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH 1/5] ALUA prioritizer: Remove an unused variable
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH 2/5] libmultipath: Simplify read_line()
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH 0/5] Five small multipath-tools patches
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [dm-crypt] LUKS on a jffs2 partition
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: John Utz <John.Utz@xxxxxxx>
• [git pull] device mapper fixes for 3.16-rc6
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [BUG] dm-writeboost: too big nr_rambuf_pool causes massive memory pressure or panic.
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [RFC] writeboost: rename "migration" to "writeback"
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: John Utz <John.Utz@xxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-multipath: Accept failed paths for multipath maps
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH ] multipath: Fall back to getuid_callout if ID_SERIAL attribute is missing.
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: [PATCH] blk-lib: fix error reporting
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 6/15] block copy: use asynchronous notification
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 8/15] dm: introduce dm_ask_for_duplicate_bios
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 14/15] dm kcopyd: change mutex to spinlock
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 10/15] dm linear: support copy
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 15/15] dm kcopyd: call copy offload with asynchronous callback
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 13/15] dm kcopyd: support copy offload
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 12/15] dm kcopyd: introduce the function submit_job
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 11/15] dm stripe: support copy
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 9/15] dm: implement copy
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 4/15] block copy: use a timer to fix a theoretical deadlock
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 7/15] dm: remove num_write_bios
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 5/15] block copy: use merge_bvec_fn for copies
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3/15] block copy: report the amount of copied data
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/15] block copy: use two bios
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/15] block copy: initial XCOPY offload support
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 0/15] SCSI XCOPY support for the kernel and device mapper
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: ANNOUNCE: SCSI XCOPY support for the kernel and device mapper
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: ANNOUNCE: SCSI XCOPY support for the kernel and device mapper
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• ANNOUNCE: SCSI XCOPY support for the kernel and device mapper
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: device mapper target vs personality, how do you decide to pick one or the other?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: device mapper target vs personality, how do you decide to pick one or the other?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: device mapper target vs personality, how do you decide to pick one or the other?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: device mapper target vs personality, how do you decide to pick one or the other?
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: insitu-comp
  • From: testfile82 <testfile82@xxxxxxxxxxx>
• [BUG] dm-writeboost: too big nr_rambuf_pool causes massive memory pressure or panic.
  • From: Satoru Takeuchi <satoru.takeuchi@xxxxxxxxx>
• [RFC] writeboost: rename "migration" to "writeback"
  • From: Satoru Takeuchi <satoru.takeuchi@xxxxxxxxx>
• Re: device mapper target vs personality, how do you decide to pick one or the other?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: device mapper target vs personality, how do you decide to pick one or the other?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: device mapper target vs personality, how do you decide to pick one or the other?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• device mapper target vs personality, how do you decide to pick one or the other?
  • From: John Utz <John.Utz@xxxxxxx>
• [git pull] device mapper fixes for 3.16-rc5
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• kpartx bug when using very long paths?
  • From: Patrick Schleizer <patrick-mailinglists@xxxxxxxxxx>
• [PATCH v2] dm-table: make dm_table_supports_discards static
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-table: make dm_table_supports_discards static
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: "Zhang, Yanmin" <yanmin_zhang@xxxxxxxxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Alexey Kardashevskiy <aik@xxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: "xinhui.pan" <xinhuix.pan@xxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: fix an error code in local_init()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] blk-lib: fix error reporting
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] blk-lib: fix error reporting
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch] dm: fix an error code in local_init()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH] blk-lib: fix error reporting
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH] multipath: add option '-i' to ignore wwids file
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
  • From: "xinhui.pan" <xinhuix.pan@xxxxxxxxx>
• Re: [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] multipath: add option '-i' to ignore wwids file
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 03/12] enable gcc format-security check
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH] blk-lib: fix error reporting
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 05/12] allow users to add wwids to /etc/multipath/wwids with -a
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 04/12] change conf->dry_run to conf->cmd
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 03/12] enable gcc format-security check
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 02/12] Return the correct size buffer in set_value()
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] Don't forget to reload table when both reload and rename is required
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 01/12] Fix memory issues in path reordering failure code paths
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] check info.exists to get valid value
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Paul Mackerras <paulus@xxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Paul Mackerras <paulus@xxxxxxxxx>
• Regression in 3.15 on POWER8 with multipath SCSI
  • From: Paul Mackerras <paulus@xxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Paul Mackerras <paulus@xxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] Update ETERNUS DX entry
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: all cache blocks marked as dirty in writethrough mode, "Data loss may occur", constant write activity
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: Regression in 3.15 on POWER8 with multipath SCSI
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: all cache blocks marked as dirty in writethrough mode, "Data loss may occur", constant write activity
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: huangminfei <huangminfei@xxxxxxxxx>
• Re: [PATCH] dm-io: Fix a race condition in the wake up code for sync_io
  • From: huangminfei <huangminfei@xxxxxxxxx>
• Re: dm-io: Prevent the danging point of the sync io callback function
  • From: huangminfei <huangminfei@xxxxxxxxx>
• [PATCH] dm-io: Fix a race condition in the wake up code for sync_io
  • From: Minfei Huang <huangminfei@xxxxxxxxx>
• all cache blocks marked as dirty in writethrough mode, "Data loss may occur", constant write activity
  • From: Marc Lehmann <schmorp@xxxxxxxxxx>
• [PATCH 06/12] Make multipath add wwids from kernel cmdline mpath.wwids with -A
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 05/12] allow users to add wwids to /etc/multipath/wwids with -a
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 08/12] Add missing interactive commands to multipathd man page
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 00/12] miscellaneous multipath patches
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 01/12] Fix memory issues in path reordering failure code paths
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 11/12] make prioritizers use checker_timeout, if set
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 03/12] enable gcc format-security check
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 04/12] change conf->dry_run to conf->cmd
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 12/12] Add multipath.conf force_sync option
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 07/12] Make multipathd orphan paths that were removed externally
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 02/12] Return the correct size buffer in set_value()
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 10/12] Improve multipath.conf syntax checking
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 09/12] orphan paths on failed add
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: dm-io: Prevent the danging point of the sync io callback function
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-io: Prevent the danging point of the sync io callback function
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• v3.15 dm-mpath regression: cable pull test causes I/O hang
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Minfei Huang <huangminfei@xxxxxxxxx>
• [PATCH] block: flush queued bios when the process blocks
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] check info.exists to get valid value
  • From: Vaughan Cao <vaughan.cao@xxxxxxxxxx>
• [PATCH] Don't forget to reload table when both reload and rename is required
  • From: Vaughan Cao <vaughan.cao@xxxxxxxxxx>
• Re: dmdedup target mkfs.ext3 failed
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• dmdedup target mkfs.ext3 failed
  • From: lvshuo <testfile82@xxxxxxxxxxx>
• LVM2 release 2.02.107: New argument --select
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [PATCH]multipath: Wrong sysfs attribute used for iSCSI settings.
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• [PATCH ] multipath: Fall back to getuid_callout if ID_SERIAL attribute is missing.
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: [PATCH ] multipath: Fall back to getuid_callout if ID_SERIAL attribute is missing.
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] dm: allocate a special workqueue for deferred remove
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [git pull] device mapper changes for 3.16
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-thin: Export proper discard_granularity
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm-thin: Export proper discard_granularity
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm-thin: Export proper discard_granularity
  • From: Lukas Czerner <lczerner@xxxxxxxxxx>
• Re: [PATCH] kpartx: fix extended partition size for >512b sectors
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] libmultipath: Use existing user friendly name if possible
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH]multipath-tools: Mismatch between allocation length and transfer length in rdac prio
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: multipath-tools: mismatch between CDB allocation length and SG_IO dxfer_len
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] libmultipath: Use existing user friendly name if possible
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH] kpartx: fix extended partition size for >512b sectors
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [RFC PATCH 0/7] dm-mpath: Do not clone requests
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: good dm-mpath test setup?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] dm-mpath: Do not clone requests
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] dm-mpath: Do not clone requests
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] dm-mpath: Do not clone requests
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH 0/7] dm-mpath: Do not clone requests
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [RFC PATCH 0/7] dm-mpath: Do not clone requests
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH 5/7] dm: move free_rq_clone() out of dm_unprep_request()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 7/7] dm: do not clone requests
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 1/7] dm: use dm_rq_target_io as argument for dm_done()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 3/7] dm: move rq_completed() out of enclosing functions
  • From: Hannes Reinecke <hare@xxxxxxx>
• [RFC PATCH 0/7] dm-mpath: Do not clone requests
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 6/7] dm: open-code free_rq_clone()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 4/7] dm: open-code dm_kill_unmapped_request()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 2/7] dm: remove handling of DM_ENDIO_INCOMPLETE
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: dm: disable WRITE SAME if it fails
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: good dm-mpath test setup?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: good dm-mpath test setup?
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: good dm-mpath test setup?
  • From: Hannes Reinecke <hare@xxxxxxx>
• good dm-mpath test setup?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: dm: disable WRITE SAME if it fails
  • From: alex chen <alex.chen@xxxxxxxxxx>
• Re: dm: disable WRITE SAME if it fails
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: disable WRITE SAME if it fails
  • From: alex chen <alex.chen@xxxxxxxxxx>
• Re: dm: disable WRITE SAME if it fails
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: disable WRITE SAME if it fails
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: 3.13-1 dm cache possible race condition
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: disable WRITE SAME if it fails
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Persistent Overlay COW Full: Flipped the Invalid bit in a hexdump; how do I grow it now?
  • From: Frederick Grose <fgrose@xxxxxxxxx>
• Persistent Overlay COW Full: Flipped the Invalid bit in a hexdump; how do I grow it now?
  • From: Rahul Nabar <rpnabar@xxxxxxxxx>
• dm: disable WRITE SAME if it fails
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Status of SCSI referrals support in dm-multipath
  • From: Hannes Reinecke <hare@xxxxxxx>
• Status of SCSI referrals support in dm-multipath
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: [PATCH] dm linear: disable WRITE SAME if it fails
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] dm linear: disable WRITE SAME if it fails
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [PATCH] dm linear: disable WRITE SAME if it fails
  • From: alex chen <alex.chen@xxxxxxxxxx>
• [git pull] device mapper fixes for 3.15 final
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [patch] DM RAID: fix a couple integer overflows
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 1/1] driver/md/block: Alloc space for member flush_rq
  • From: "Li, Zhen-Hua" <zhen-hual@xxxxxx>
• Re: [PATCH 1/1] driver/md/block: Alloc space for member flush_rq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/1] driver/md/block: Alloc space for member flush_rq
  • From: "Li, Zhen-Hua" <zhen-hual@xxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: block: flush queued bios when the process blocks
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: block: flush queued bios when the process blocks
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] block: flush queued bios when the process blocks
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] block: flush queued bios when the process blocks
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Problem with overlay free space
  • From: Ришат Терегулов <rtereguloff@xxxxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: slab_common: fix the check for duplicate slab names
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: slab_common: fix the check for duplicate slab names
  • From: Pekka Enberg <penberg@xxxxxx>
• [PATCH] md: Use time_in_range()
  • From: Manuel Schölling <manuel.schoelling@xxxxxx>
• Re: [PATCH v2] dm thin: return ENOSPC instead of EIO when error_if_no_space enabled
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: slab_common: fix the check for duplicate slab names
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-writeboost: Progress Report
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH] dm thin: return ENOSPC instead of EIO when error_if_no_space enabled
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH v2] dm thin: return ENOSPC instead of EIO when error_if_no_space enabled
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm thin: return ENOSPC instead of EIO when error_if_no_space enabled
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: Re-using bio
  • From: Enoch Root <enokhroot@xxxxxxxxx>
• Re-using bio
  • From: Enoch Root <enokhroot@xxxxxxxxx>
• Re: [PATCH] multipath: Fix some minor issues in path reordering code
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: multipath-tools: mismatch between CDB allocation length and SG_IO dxfer_len
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: multipath-tools: mismatch between CDB allocation length and SG_IO dxfer_len
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [PATCH] multipath: Fix some minor issues in path reordering code
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: multipath-tools: mismatch between CDB allocation length and SG_IO dxfer_len
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: [PATCH] dm: check era->md is non-NULL before closing it
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH] dm: check era->md is non-NULL before closing it
  • From: naota@xxxxxxxxx
• [PATCH]multipath-tools: Mismatch between allocation length and transfer length in rdac prio
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: Status of Linux LVM thin provisioning
  • From: Patrik Horník <patrik@xxxxxx>
• Re: Status of Linux LVM thin provisioning
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: thin_repair doesn't do size checking on the output device
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Status of Linux LVM thin provisioning
  • From: Patrik Horník <patrik@xxxxxx>
• thin_repair doesn't do size checking on the output device
  • From: "M.H. Tsai" <mingnus@xxxxxxxxx>
• dm-writeboost: Progress Report
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• [git pull] device mapper fixes for 3.15-rc6
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: an interesting note on LUN coalescing
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: Problem with multipath
  • From: Tommaso <tomcec@xxxxxxxxx>
• Re: an interesting note on LUN coalescing
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: [PATCH] libmultipath: Use existing user friendly name if possible
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: an interesting note on LUN coalescing
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: an interesting note on LUN coalescing
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: [PATCH] libmultipath: Use existing user friendly name if possible
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: an interesting note on LUN coalescing
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: an interesting note on LUN coalescing
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: path coalescing once more
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: path coalescing once more
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• an interesting note on LUN coalescing
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• path coalescing once more
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: Performance question when blocks in thin-pool are assume zeroed
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Performance question when blocks in thin-pool are assume zeroed
  • From: Wayne Chou <gmmark12@xxxxxxxxx>
• Performance question when blocks in thin-pool are assume zeroed
  • From: Wayne Chou <gmmark12@xxxxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm thin: allow metadata commit if pool is in PM_OUT_OF_DATA_SPACE mode
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: if i create a new dm target type, do i need to add its init to the _inits[] and its exit to the _exits[]?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: if i create a new dm target type, do i need to add its init to the _inits[] and its exit to the _exits[]?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• if i create a new dm target type, do i need to add its init to the _inits[] and its exit to the _exits[]?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: are there usage examples for dm_sm_metadata_{create|open}?
  • From: John Utz <John.Utz@xxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: are there usage examples for dm_sm_metadata_{create|open}?
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• 3.15-rc4: circular locking dependency triggered by dm-multipath
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: Can device mapper be taught to return new errors and sense codes that are part of the ZAC/ZBC spec?
  • From: "John L. Utz III (WDC)" <john.utz@xxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: sg_persist triggers block kernel event ???
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• sg_persist triggers block kernel event ???
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: Can device mapper be taught to return new errors and sense codes that are part of the ZAC/ZBC spec?
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Can device mapper be taught to return new errors and sense codes that are part of the ZAC/ZBC spec?
  • From: John Utz <John.Utz@xxxxxxx>
• are there usage examples for dm_sm_metadata_{create|open}?
  • From: John Utz <John.Utz@xxxxxxx>
• [git pull] device mapper fixes for 3.15-rc4
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Fix segfault when fast_io_fail_tmo is empty in config file.
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [PATCH] Fix segfault when fast_io_fail_tmo is empty in config file.
  • From: Jose Castillo <jcastillo@xxxxxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH RFC 08/10] dm-dedup: Kconfig changes
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 02/10] dm-dedup: core deduplication logic
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 03/10] dm-dedup: hash computation
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 04/10] dm-dedup: implementation of the read-on-write procedure
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 10/10] dm-dedup: documentation
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 01/10] dm-dedup: main data structures
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 05/10] dm-dedup: COW B-tree backend
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 09/10] dm-dedup: status function
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 06/10] dm-dedup: inram backend
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• [PATCH RFC 07/10] dm-dedup: Makefile changes
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [PATCH 6/6] dm: introduce dm_ask_for_duplicate_bios
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 6/6] dm: introduce dm_ask_for_duplicate_bios
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 6/6] dm: introduce dm_ask_for_duplicate_bios
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [Gluster-devel] Puppet-Gluster+ThinP
  • From: Lukáš Czerner <lczerner@xxxxxxxxxx>
• Re: [Gluster-devel] Puppet-Gluster+ThinP
  • From: James <purpleidea@xxxxxxxxx>
• Re: [Gluster-devel] Puppet-Gluster+ThinP
  • From: James <purpleidea@xxxxxxxxx>
• Re: [Gluster-devel] Puppet-Gluster+ThinP
  • From: David Teigland <teigland@xxxxxxxxxx>
• Re: [Gluster-devel] Puppet-Gluster+ThinP
  • From: James <purpleidea@xxxxxxxxx>
• path coalescing problems revisited
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• a problem about dm_kcopyd_copy()
  • From: lihuiba <magazine.lihuiba@xxxxxxx>
• Re: [Gluster-devel] Puppet-Gluster+ThinP
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: [Gluster-devel] Puppet-Gluster+ThinP
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: dm-verity: Fix biovecs hash calculation regression
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-verity: Fix biovecs hash calculation regression
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-verity: Fix biovecs hash calculation regression
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: path coalescing in multipath
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: path coalescing in multipath
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• path coalescing in multipath
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: [PATCH] libmultipath: Use existing user friendly name if possible
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: [PATCH] libmultipath: Use existing user friendly name if possible
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: [PATCH 0/9] dm-crypt patches
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: [PATCH 0/9] dm-crypt patches
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Correct Routing Setup for Multipath
  • From: Eric K <iggiggitoo@xxxxxxxxx>
• Re: [PATCH 0/9] dm-crypt patches
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/9] dm-crypt patches
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• kpartx -d fails to delete partition mapping for long filenames
  • From: "Carsten Scholtes" <Carsten_Scholtes@xxxxxxx>
• not able to find dm-integrity source code
  • From: Shiva <shivaramakrishnan740@xxxxxxxxx>
• not able to find dm-integrity source code
  • From: Shiva <shivaramakrishnan740@xxxxxxxxx>
• Re: block: use kmalloc alignment for bio slab
  • From: Jens Axboe <axboe@xxxxxx>
• dm-integrity source code link?
  • From: Shiva <shivaramakrishnan740@xxxxxxxxx>
• Re: block: use kmalloc alignment for bio slab
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm-verity usage help related
  • From: Shivaramakrishnan Vaidyanathan <shivaramakrishnan740@xxxxxxxxx>
• dm-verity usage understanding
  • From: Shiva <shivaramakrishnan740@xxxxxxxxx>
• Re: [PATCH 0/9] dm-crypt patches
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 9/9] dm-crypt: sort writes
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 8/9] dm-crypt: offload writes to thread
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 6/9] dm-crypt: avoid deadlock in mempools
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 7/9] dm-crypt: remove io_pool
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 5/9] dm-crypt: don't allocate pages for a partial request
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 4/9] dm-crypt: use unbound workqueue for request processing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/9] bio: use kmalloc alignment for bio slab
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3/9] dm-crypt: use per-bio data
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/9] dm-crypt: remove per-cpu structure
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 0/9] dm-crypt patches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• multipath-tools: mismatch between CDB allocation length and SG_IO dxfer_len
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• [git pull] device mapper changes for 3.15
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] block: use kmalloc alignment for bio slab
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 8/9] dm crypt: offload writes to thread
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: [PATCH 9/9] dm crypt: sort writes
  • From: Akira Hayakawa <hayakawa@xxxxxxxxxxxxx>
• Re: [PATCH 9/9] dm crypt: sort writes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 9/9] dm crypt: sort writes
  • From: Akira Hayakawa <hayakawa@xxxxxxxxxxxxx>
• Re: [PATCH 9/9] dm crypt: sort writes
  • From: Akira Hayakawa <hayakawa@xxxxxxxxxxxxx>
• Re: [PATCH 9/9] dm crypt: sort writes
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH 8/9] dm crypt: offload writes to thread
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH 8/9] dm crypt: offload writes to thread
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 8/9] dm crypt: offload writes to thread
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 8/9] dm crypt: offload writes to thread
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 9/9] dm crypt: sort writes
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH 8/9] dm crypt: offload writes to thread
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 8/9] dm crypt: offload writes to thread
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: [PATCH 9/9] dm crypt: sort writes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 9/9] dm crypt: sort writes
  • From: Akira Hayakawa <hayakawa@xxxxxxxxxxxxx>
• Re: [PATCH 9/9] dm crypt: sort writes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 9/9] dm crypt: sort writes
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [PATCH] libmultipath: Use existing user friendly name if possible
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• [PATCH 6/9] dm crypt: avoid deadlock in mempools
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 7/9] dm crypt: remove io_pool
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 8/9] dm crypt: offload writes to thread
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/9] dm crypt: fix cpu hotplug crash by removing per-cpu structure
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 5/9] dm crypt: don't allocate pages for a partial request
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 3/9] dm crypt: use per-bio data
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 2/9] block: use kmalloc alignment for bio slab
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 9/9] dm crypt: sort writes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 4/9] dm crypt: use unbound workqueue for request processing
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 0/9] dm crypt: improve cpu scalability
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] avoid recursion in bio_endio
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3/4] [dm-cache] Switch to new dm_bm_flush() interface.
  • From: Joe Thornber <ejt@xxxxxxxxxx>
• [PATCH 4/4] [dm-thin, dm-cache, dm-era] Take care to copy the space map roots before locking the superblock.
  • From: Joe Thornber <ejt@xxxxxxxxxx>
• [PATCH 0/4] Patchset to fix possible corruption with dm-thin et al.
  • From: Joe Thornber <ejt@xxxxxxxxxx>
• [PATCH 1/4] [perstent-data] Simplify dm_bm_flush_and_unlock() -> dm_bm_flush()
  • From: Joe Thornber <ejt@xxxxxxxxxx>
• [PATCH 2/4] [persistent-data] change the semantics of dm_tm_commit().
  • From: Joe Thornber <ejt@xxxxxxxxxx>
• Re: [PATCH RFC v1 00/01] dm-lightnvm introduction
  • From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
• Re: slab_common: fix the check for duplicate slab names
  • From: Christoph Lameter <cl@xxxxxxxxx>
• [PATCH] dm-cache: discard block size causes data corruption
  • From: heinzm@xxxxxxxxxx
• Re: best way to detect a dm device is dm-multipath from userspace?
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: best way to detect a dm device is dm-multipath from userspace?
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• best way to detect a dm device is dm-multipath from userspace?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: slab_common: fix the check for duplicate slab names
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Multipath not using multiple NICs at once
  • From: Eric <iggiggitoo@xxxxxxxxx>
• Re: Multipath not using multiple NICs at once
  • From: Eric <iggiggitoo@xxxxxxxxx>
• Re: [PATCH RFC v1 01/01] dm-lightnvm: An open FTL for open firmware SSDs
  • From: Takashi HOSHINO <hoshino@xxxxxxxxxxxxxxxxx>
• Re: [PATCH RFC v1 01/01] dm-lightnvm: An open FTL for open firmware SSDs
  • From: Matias Bjorling <m@xxxxxxxxxxx>
• Re: [PATCH RFC v1 00/01] dm-lightnvm introduction
  • From: Matias Bjorling <m@xxxxxxxxxxx>
• Re: [PATCH RFC v1 01/01] dm-lightnvm: An open FTL for open firmware SSDs
  • From: Matias Bjorling <m@xxxxxxxxxxx>
• Re: [PATCH RFC v1 00/01] dm-lightnvm introduction
  • From: David Lang <david@xxxxxxx>
• Re: [PATCH RFC v1 01/01] dm-lightnvm: An open FTL for open firmware SSDs
  • From: Akira Hayakawa <hayakawa@xxxxxxxxxxxxx>
• [PATCH] drivers/md: Use RCU_INIT_POINTER(x, NULL) in dm.c
  • From: Monam Agarwal <monamagarwal123@xxxxxxxxx>
• Re: [PATCH RFC v1 01/01] dm-lightnvm: An open FTL for open firmware SSDs
  • From: Matias Bjorling <m@xxxxxxxxxxx>
• Re: [PATCH RFC v1 01/01] dm-lightnvm: An open FTL for open firmware SSDs
  • From: Matias Bjorling <m@xxxxxxxxxxx>
• Re: [PATCH RFC v1 00/01] dm-lightnvm introduction
  • From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
• Re: [PATCH RFC v1 00/01] dm-lightnvm introduction
  • From: Matias Bjorling <m@xxxxxxxxxxx>
• Multipath not using multiple NICs at once
  • From: Eric <iggiggitoo@xxxxxxxxx>
• Re: [PATCH RFC v1 00/01] dm-lightnvm introduction
  • From: Matias Bjorling <m@xxxxxxxxxxx>
• Re: [PATCH RFC v1 01/01] dm-lightnvm: An open FTL for open firmware SSDs
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: Multipath not using multiple NICs at once
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: Multipath not using multiple NICs at once
  • From: urgrue <urgrue@xxxxxxxxxxx>
• Multipath not using multiple NICs at once
  • From: Eric <iggiggitoo@xxxxxxxxx>
• Re: [PATCH RFC v1 01/01] dm-lightnvm: An open FTL for open firmware SSDs
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH RFC v1 01/01] dm-lightnvm: An open FTL for open firmware SSDs
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: udevsettle command takes long time to settle in RHEL 5.9 & 5.10
  • From: Arunachalam <k.arunachalam@xxxxxxxxx>
• Re: udevsettle command takes long time to settle in RHEL 5.9 & 5.10
  • From: Arunachalam <k.arunachalam@xxxxxxxxx>
• Re: [PATCH RFC v1 00/01] dm-lightnvm introduction
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH RFC v1 01/01] dm-lightnvm: An open FTL for open firmware SSDs
  • From: Matias Bjørling <m@xxxxxxxxxxx>
• [PATCH RFC v1 00/01] dm-lightnvm introduction
  • From: Matias Bjørling <m@xxxxxxxxxxx>
• Re: [dm-crypt] trouble with dm-crypt and NFS: server hangs
  • From: Stephen Cousins <steve.cousins@xxxxxxxxx>
• multipath-tools: race condition between 'mutipath -r' and multipathd path checker causing segfault
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: [dm-crypt] trouble with dm-crypt and NFS: server hangs
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: How dm multipath handle IO
  • From: Nicolas Michel <be.nicolas.michel@xxxxxxxxx>
• Re: [patch v3]DM: dm-insitu-comp: a compressed DM target for SSD
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch v3]DM: dm-insitu-comp: a compressed DM target for SSD
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch v3]DM: dm-insitu-comp: a compressed DM target for SSD
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: multipath prio issues
  • From: Ross Anderson <rosander@xxxxxxxxx>
• Re: [patch v3]DM: dm-insitu-comp: a compressed DM target for SSD
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: multipath prio issues
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH 2/6] dm: introduce dm_accept_partial_bio
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/6] dm: introduce dm_accept_partial_bio
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• multipath prio issues
  • From: Ross Anderson <rosander@xxxxxxxxx>
• Re: [PATCH 2/6] dm: introduce dm_accept_partial_bio
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [patch v3]DM: dm-insitu-comp: a compressed DM target for SSD
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/6] dm: introduce dm_accept_partial_bio
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/6] dm: introduce dm_accept_partial_bio
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/6] dm: introduce dm_accept_partial_bio
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/6] dm: introduce dm_accept_partial_bio
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/6] dm: introduce dm_accept_partial_bio
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-cache: dm-3.14-fixes-4
  • From: "George ." <george@xxxxxxxx>
• Re: dm-cache: dm-3.14-fixes-4
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm-cache: dm-3.14-fixes-4
  • From: "George ." <george@xxxxxxxx>
• Re: [PATCH 2/6] dm: introduce dm_accept_partial_bio
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/1] block: rework flush sequencing for blk-mq
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: [patch v3]DM: dm-insitu-comp: a compressed DM target for SSD
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: A target to just process bios background?
  • From: Akira Hayakawa <hayakawa@xxxxxxxxxxxxx>
• scsi_debug and mutipath, was Re: [PATCH 1/1] block: rework flush sequencing for blk-mq
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Kernel bug triggered in multipath
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Kernel bug triggered in multipath
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [patch v3]DM: dm-insitu-comp: a compressed DM target for SSD
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 6/6] dm: introduce dm_ask_for_duplicate_bios
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 5/6] dm: remove num_write_bios
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 4/6] dm origin: split only write bios
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3/6] dm-snapshot: make the origin target allocate per-target structure
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/6] dm: change sector_t len to unsigned
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/6] dm: introduce dm_accept_partial_bio
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Kernel bug triggered in multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Kernel bug triggered in multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [git pull] device mapper fixes to include in 3.14
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/1] block: rework flush sequencing for blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/1] block: rework flush sequencing for blk-mq
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/1] block: rework flush sequencing for blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch v3]DM: dm-insitu-comp: a compressed DM target for SSD
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: How dm multipath handle IO
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• How dm multipath handle IO
  • From: Nicolas Michel <be.nicolas.michel@xxxxxxxxx>
• Re: link against libsystemd, not libsystemd-daemon
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: kpartx fails 4k block partition *changed**
  • From: Ross Anderson <rosander@xxxxxxxxx>
• link against libsystemd, not libsystemd-daemon
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] Update FSF address
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: kpartx fails 4k block partition
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: dm: stop using bi_private
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCHv9 0/8] dm-multipath: push back requests instead of queueing
  • From: Hannes Reinecke <hare@xxxxxxx>
• kpartx fails 4k block partition
  • From: Ross Anderson <rosander@xxxxxxxxx>
• Re: [RFC PATCH] dm-multipath: Print more explicit warnings when dealing with multipath messages
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/2] multipath: Stop extra scans on stacked devices
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCHv9 0/8] dm-multipath: push back requests instead of queueing
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: udevsettle command takes long time to settle in RHEL 5.9 & 5.10
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• udevsettle command takes long time to settle in RHEL 5.9 & 5.10
  • From: Adarsh <adarshanto@xxxxxxxxx>
• [PATCH] multipath devices are not getting created for readonly devices
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH] Disable partitions scan for multipathed devices
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH] Disable partitions scan for multipathed devices
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH] Disable partitions scan for multipathed devices
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH] multipath devices are not getting created for readonly devices
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] Disable partitions scan for multipathed devices
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 1/1] dm cache: fix accesses past end of origin device
  • From: heinzm@xxxxxxxxxx
• [PATCH] Disable partitions scan for multipathed devices
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH] Disable partitions scan for multipathed devices
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [PATCH] Disable partitions scan for multipathed devices
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] Disable partitions scan for multipathed devices
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [PATCH] Disable partitions scan for multipathed devices
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [PATCH] Disable partitions scan for multipathed devices
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• Re: [PATCH 0/2] multipath: Stop extra scans on stacked devices
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH for-3.15 1/3] dm: add era target
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] Don't exit() from library
  • From: Ritesh Raj Sarraf <rrs@xxxxxxxxxx>
• Re: dm: era: use do_div for 64-bit division
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] Don't exit() from library
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH] dm: era: use do_div for 64-bit division
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• [PATCH] Don't exit() from library
  • From: Ritesh Raj Sarraf <rrs@xxxxxxxxxx>
• Re: [PATCH for-3.15 1/3] dm: add era target
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 3/3] Library with an exit()
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [patch v3]DM: dm-insitu-comp: a compressed DM target for SSD
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: A target to just process bios background?
  • From: Akira Hayakawa <hayakawa@xxxxxxxxxxxxx>
• randconfig build error with next-20140307, in drivers/md/dm-era-target.c
  • From: Jim Davis <jim.epost@xxxxxxxxx>
• Re: [PATCH 3/3] Library with an exit()
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH 1/3] Fix build failure with fomat-security. Specify the format type.
  • From: Ritesh Raj Sarraf <rrs@xxxxxxxxxx>
• [PATCH 3/3] Library with an exit()
  • From: Ritesh Raj Sarraf <rrs@xxxxxxxxxx>
• [PATCH 2/3] Minor spelling error fixes
  • From: Ritesh Raj Sarraf <rrs@xxxxxxxxxx>
• [git pull v2] device mapper fixes to include in 3.14-rc6
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: A bug in dm-persistent-data module which leads to dm-thin metadata corruption
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: A bug in dm-persistent-data module which leads to dm-thin metadata corruption
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: randconfig build error with next-20140307, in drivers/md/dm-era-target.c
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [patch v3]DM: dm-insitu-comp: a compressed DM target for SSD
  • From: Shaohua Li <shli@xxxxxxxxxx>
• A bug in dm-persistent-data module which leads to dm-thin metadata corruption
  • From: Teng-Feng Yang <shinrairis@xxxxxxxxx>
• [PATCH for-3.15 1/3] dm: add era target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-3.15 3/3] dm bitset: only flush the current word if it has been dirtied
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-3.15 2/3] dm era: support non power-of-2 blocksize
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: A target to just process bios background?
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [git pull] device mapper fixes to include in 3.14-rc6
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 4/8] dm mpath: remove process_queued_ios()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm linear: disable WRITE SAME if it fails
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] slab_common: fix the check for duplicate slab names
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• [PATCH] dm: stop using bi_private
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 4/8] dm mpath: remove process_queued_ios()
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: IO Ordering on Path Failover
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH] dm linear: disable WRITE SAME if it fails
  • From: alex chen <alex.chen@xxxxxxxxxx>
• [PATCH] slab_common: fix the check for duplicate slab names
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• A target to just process bios background?
  • From: Akira Hayakawa <hayakawa@xxxxxxxxxxxxx>
• [PATCH] dm: remove dm_get_mapinfo
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm snapshot: fix data corruption
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/9] block: Make generic_make_request handle arbitrary sized bios
  • From: Muthu Kumar <muthu.lkml@xxxxxxxxx>
• Re: [PATCH 1/9] block: Make generic_make_request handle arbitrary sized bios
  • From: Muthu Kumar <muthu.lkml@xxxxxxxxx>
• Re: [PATCH 1/9] block: Make generic_make_request handle arbitrary sized bios
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: [RFC] dm-writeboost: Persistent memory support
  • From: Jerome Glisse <j.glisse@xxxxxxxxx>
• Re: [PATCH 4/8] dm mpath: remove process_queued_ios()
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH] dm-raid: check events in super_validate
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH 1/9] block: Make generic_make_request handle arbitrary sized bios
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• IO Ordering on Path Failover
  • From: Bob Bawn <bob.bawn@xxxxxxxxxxxxx>
• Re: [PATCH] dm-raid: check events in super_validate
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH] scsi_dh_alua: Requeue another not ready check condition at ML
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• [git pull] device mapper fixes to include in 3.14-rc5
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] scsi_dh_alua: Requeue another not ready check condition at ML
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 8/8] dm-mpath: do not activate failed paths
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCHv3] dm-multipath: Accept failed paths for multipath maps
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 8/8] dm-mpath: do not activate failed paths
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 8/8] dm-mpath: do not activate failed paths
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 4/8] dm mpath: remove process_queued_ios()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 1/8] dm mpath: do not call pg_init when it is already running
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 5/8] dm mpath: reduce memory pressure when requeuing
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCHv9 0/8] dm-multipath: push back requests instead of queueing
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 2/8] dm table: add dm_table_run_md_queue_async
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 7/8] dm mpath: remove extra nesting in map function
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 3/8] dm mpath: push back requests instead of queueing
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 6/8] dm mpath: remove map_io()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 8/8] dm-mpath: do not activate failed paths
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 8/8] dm-mpath: do not activate failed paths
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/9] block: Make generic_make_request handle arbitrary sized bios
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxxxx>
• Re: [PATCH 8/8] dm-mpath: do not activate failed paths
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 8/8] dm-mpath: do not activate failed paths
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 8/8] dm-mpath: do not activate failed paths
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 4/8] dm mpath: remove process_queued_ios()
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 8/8] dm-mpath: do not activate failed paths
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 4/8] dm mpath: remove process_queued_ios()
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 8/8] dm-mpath: do not activate failed paths
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 6/8] dm mpath: remove map_io()
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH] scsi_dh_alua: Requeue another not ready check condition at ML
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• [PATCH] scsi_dh_alua: Requeue another not ready check condition at ML
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: dm-cache for Fedora 21?
  • From: "Paul B. Henson" <henson@xxxxxxx>
• Re: dm-cache for Fedora 21?
  • From: "Paul B. Henson" <henson@xxxxxxx>
• Re: dm-cache for Fedora 21?
  • From: Rolf Fokkens <rolf@xxxxxxxxxxxxxx>
• Re: [PATCH 1/9] block: Make generic_make_request handle arbitrary sized bios
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH] dm-multipath: blacklist NVMe devices
  • From: Vaughan Cao <vaughan.cao@xxxxxxxxxx>
• Re: [PATCH] dm-raid: check events in super_validate
  • From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
• Re: [PATCH] multipathd: not skip paths not belonging to a mpp in check_path
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] dm-multipath: blacklist NVMe devices
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [PATCH 6/8] dm mpath: remove map_io()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 3/8] dm mpath: push back requests instead of queueing
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 8/8] dm-mpath: do not activate failed paths
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 1/8] dm mpath: do not call pg_init when it is already running
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 2/8] dm table: add dm_table_run_md_queue_async
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 5/8] dm mpath: reduce memory pressure when requeuing
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 4/8] dm mpath: remove process_queued_ios()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 7/8] dm mpath: remove extra nesting in map function
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCHv8 0/8] dm-multipath: push back requests instead of queueing
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: dm-crypt: remove per-cpu structure
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/9] block: Make generic_make_request handle arbitrary sized bios
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH] dm-raid: check events in super_validate
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: dm-multipath: Do not stall on invalid ioctls
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm-multipath: Do not stall on invalid ioctls
  • From: Hannes Reinecke <hare@xxxxxxx>
• [dm-thin] metadata corruption
  • From: 黃崇智 <edwillam1007@xxxxxxxxx>
• Re: [PATCH] dm-raid: check events in super_validate
  • From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
• Re: [PATCH] dm-raid: check events in super_validate
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH] dm-raid: check events in super_validate
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: creating a dm-linear.ko in a current kernel.
  • From: johnstra10 <johnstra10@xxxxxxxxx>
• Re: creating a dm-linear.ko in a current kernel.
  • From: John Utz <John.Utz@xxxxxxx>
• Re: dm thin: inverted down_trylock() test
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: creating a dm-linear.ko in a current kernel.
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• [patch] dm thin: inverted down_trylock() test
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] dm-raid: check events in super_validate
  • From: NeilBrown <neilb@xxxxxxx>
• Re: creating a dm-linear.ko in a current kernel.
  • From: John Utz <John.Utz@xxxxxxx>
• creating a dm-linear.ko in a current kernel.
  • From: John Utz <John.Utz@xxxxxxx>
• [PATCH] multipathd: not skip paths not belonging to a mpp in check_path
  • From: Vaughan Cao <vaughan.cao@xxxxxxxxxx>
• [PATCH 2/2] dm-crypt: use per-bio data
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/2] bio: use kmalloc alignment for bio slab
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-crypt: remove per-cpu structure
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: dm-crypt: remove per-cpu structure
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-crypt: remove per-cpu structure
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: dm-crypt: remove per-cpu structure
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-crypt: remove per-cpu structure
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH for-dm-3.14-fixes 6/8] dm thin: fix pool_preresume resize with heavy IO races
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH for-dm-3.14-fixes 4/8] dm thin: error out I/O if inappropriate for it to be retried
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH for-dm-3.14-fixes 3/8] dm thin: set flag if metadata is out of space
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH for-dm-3.14-fixes 6/8] dm thin: fix pool_preresume resize with heavy IO races
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH for-dm-3.14-fixes 8/8] dm thin: allow metadata space larger than supported to go unused
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH for-dm-3.14-fixes 3/8] dm thin: set flag if metadata is out of space
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH for-dm-3.14-fixes 7/8] dm thin: ensure user takes action to validate data and metadata consistency
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH for-dm-3.14-fixes 6/8] dm thin: fix pool_preresume resize with heavy IO races
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH for-dm-3.14-fixes 4/8] dm thin: error out I/O if inappropriate for it to be retried
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH for-dm-3.14-fixes 3/8] dm thin: set flag if metadata is out of space
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH for-dm-3.14-fixes 2/8] dm thin: set flag when over the metadata low watermark threshold
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH for-dm-3.14-fixes 2/8] dm thin: set flag when over the metadata low watermark threshold
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH for-dm-3.14-fixes 1/8] dm thin: synchronize the pool mode during suspend
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH for-dm-3.14-fixes 2/8] dm thin: set flag when over the metadata low watermark threshold
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH]multipath-tools: Re-ordering of child paths in priority group for round-robin path selector
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: [PATCH]multipath-tools: Re-ordering of child paths in priority group for round-robin path selector
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• [PATCH v2]multipath-tools: Re-ordering of child paths in priority group for round-robin path selector
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: dm-crypt: remove per-cpu structure
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH for-dm-3.14-fixes 4/8] dm thin: error out I/O if inappropriate for it to be retried
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-dm-3.14-fixes 1/8] dm thin: synchronize the pool mode during suspend
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-dm-3.14-fixes 8/8] dm thin: allow metadata space larger than supported to go unused
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-dm-3.14-fixes 6/8] dm thin: fix pool_preresume resize with heavy IO races
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-dm-3.14-fixes 7/8] dm thin: ensure user takes action to validate data and metadata consistency
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-dm-3.14-fixes 3/8] dm thin: set flag if metadata is out of space
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-dm-3.14-fixes 0/8] dm thin: address a few fundamental problems
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-dm-3.14-fixes 2/8] dm thin: set flag when over the metadata low watermark threshold
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH for-dm-3.14-fixes 5/8] dm thin: fix the error path for the thin device constructor
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-crypt: remove per-cpu structure
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>