Linux RAID Storage Date Index

Thread Index

Re: Optimize RAID0 for max IOPS?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Optimize RAID0 for max IOPS?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Optimize RAID0 for max IOPS?
- From: Stefan /*St0fF*/ Hübner <stefan.huebner@xxxxxxxxxxxxxxxxxx>
Re: RAID0 - cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: RAID0 - cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: How to force rewrite of a smart detected bad block with raid5: checkarray?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
Re: How to force rewrite of a smart detected bad block with raid5: checkarray?
- From: NeilBrown <neilb@xxxxxxx>
Re: How to force rewrite of a smart detected bad block with raid5: checkarray?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
Re: [PATCH 5/6] Remove code for non re-striping operations.
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/2] md/raid5: FIX: manually-added spare is not used
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 0/6] OLCE raid5/0 (all arrays in container)
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID0 - cache
- From: NeilBrown <neilb@xxxxxxx>
RAID0 - cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: How to force rewrite of a smart detected bad block with raid5: checkarray?
- From: NeilBrown <neilb@xxxxxxx>
Re: Optimize RAID0 for max IOPS?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Optimize RAID0 for max IOPS?
- From: Wolfgang Denk <wd@xxxxxxx>
Re: How to force rewrite of a smart detected bad block with raid5: checkarray?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
Re: How to force rewrite of a smart detected bad block with raid5: checkarray?
- From: Richard Scobie <r.scobie@xxxxxxxxxxxx>
Re: support for external persistent cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
RAID0-cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: How to force rewrite of a smart detected bad block with raid5: checkarray?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
Re: support for external persistent cache
- From: Cory Coager <ccoager@xxxxxxxxx>
Re: support for external persistent cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: support for external persistent cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: support for external persistent cache
- From: Cory Coager <ccoager@xxxxxxxxx>
Re: support for external persistent cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
PATCH 4/5] imsm: detail_platform_imsm supports Intel SAS controller (isci driver)
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH 5/5] imsm: support for Intel SAS controller in get_disk_controller_domain handler
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH 3/5] imsm: prepare detail_platform_imsm to support different types of controllers
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH 2/5] imsm: support for Intel(R) SAS controller in imsm handler
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH 1/5] imsm platform: support for Intel(R) SAS controller.
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH 0/5] Intel SAS controller support for IMSM
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
Re: support for external persistent cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: support for external persistent cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: support for external persistent cache
- From: Cory Coager <ccoager@xxxxxxxxx>
Re: support for external persistent cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: support for external persistent cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: support for external persistent cache
- From: Cory Coager <ccoager@xxxxxxxxx>
[PATCH 6/6] FIX: Unblock disk in kernel only if it is blocked.
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 5/6] FIX: Reset disk state if disk is missing
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 4/6] FIX: Remove disks in mdmon for external metadata
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 3/6] Check number of failed disks durig raid10->raid0 takeover
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 2/6] FIX: Ping manager after level change
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 1/6] Limit no-restriping operations only for raid5
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 0/6] A few fixes connected with raid0<->raid10 takeover
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
Re: support for external persistent cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: support for external persistent cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: support for external persistent cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: support for external persistent cache
- From: Cory Coager <ccoager@xxxxxxxxx>
Re: support for external persistent cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: md raid5 blocked in get_active_stripe after disk failure
- From: David Flynn <davidf@xxxxxxxxxxxx>
I wonder what the bad blocks were storing
- From: FLD <fld@xxxxxxxxxx>
Re: How to force rewrite of a smart detected bad block with raid5: checkarray?
- From: NeilBrown <neilb@xxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: Igor Podlesny <for.poige+linux@xxxxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: NeilBrown <neilb@xxxxxxx>
Re: Optimize RAID0 for max IOPS?
- From: Jan Kasprzak <kas@xxxxxxxxxx>
Re: Optimize RAID0 for max IOPS?
- From: Jaap Crezee <jaap@xxxxxx>
Re: Optimize RAID0 for max IOPS?
- From: Stefan /*St0fF*/ Hübner <stefan.huebner@xxxxxxxxxxxxxxxxxx>
Re: How to force rewrite of a smart detected bad block with raid5: checkarray?
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: Igor Podlesny <for.poige+linux@xxxxxxxxx>
How to force rewrite of a smart detected bad block with raid5: checkarray?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
Re: Optimize RAID0 for max IOPS?
- From: Wolfgang Denk <wd@xxxxxxx>
Re: Optimize RAID0 for max IOPS?
- From: Wolfgang Denk <wd@xxxxxxx>
Re: Optimize RAID0 for max IOPS?
- From: Wolfgang Denk <wd@xxxxxxx>
Re: support for external persistent cache
- From: Cory Coager <ccoager@xxxxxxxxx>
Re: support for external persistent cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: support for external persistent cache
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
support for external persistent cache
- From: Cory Coager <ccoager@xxxxxxxxx>
Re: Optimize RAID0 for max IOPS?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Optimize RAID0 for max IOPS?
- From: Stefan /*St0fF*/ Hübner <stefan.huebner@xxxxxxxxxxxxxxxxxx>
Re: Optimize RAID0 for max IOPS?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Optimize RAID0 for max IOPS?
- From: Wolfgang Denk <wd@xxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: NeilBrown <neilb@xxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: Igor Podlesny <for.poige+linux@xxxxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: Read algorithm-raid1/raid10
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: Igor Podlesny <for.poige+linux@xxxxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: Igor Podlesny <for.poige+linux@xxxxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Hi! Why having LSR's chunk size 2^n limitation?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Read algorithm-raid1/raid10
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Hi! Why having LSR's chunk size 2^n limitation?
- From: Igor Podlesny <for.poige+linux@xxxxxxxxx>
Re: Read algorithm-raid1/raid10
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: Read algorithm-raid1/raid10
- From: Keld Jørn Simonsen <keld@xxxxxxxxxx>
Re: Read algorithm-raid1/raid10
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Read algorithm-raid1/raid10
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: RAID for USB flash drives
- From: Hank Barta <hbarta@xxxxxxxxx>
RE: [PATCH 5/6] Remove code for non re-striping operations.
- From: "Wojcik, Krzysztof" <krzysztof.wojcik@xxxxxxxxx>
[PATCH 4/4] raid0->raid10 takeover- process metadata update
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 3/4] raid0->raid10 takeover- allocate memory for added disks
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 2/4] raid0->raid10 takeover- create metadata update
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 1/4] Add raid10 -> raid0 takeover support
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 0/4] raid0<->raid10 takeover for imsm metadata
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
Re: RAID for USB flash drives
- From: Iordan Iordanov <iordan@xxxxxxxxxxxxxxx>
RE: [PATCH 1/2] md/raid5: FIX: manually-added spare is not used
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
RE: [PATCH 0/6] OLCE raid5/0 (all arrays in container)
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
RE: [PATCH 2/2] Assemble: allow to assemble spares on their own
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
RE: [PATCH] Monitor: do not move partitions to external container
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
[PATCH] Monitor: avoid adding too many spares to container
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
RE: [PATCH 5/6] FIX: mdadm hangs during reshape
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: open_dev_excl in reshape_container() fails
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 4/6] Add raid10 -> raid0 takeover support
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 3/6] Unfreeze for non re-striping transitions
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/6] Set reshape.after.data_disks for raid0<->raid10 takeover
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/6] Define imsm_analyze_change function
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] fix: Monitor: min_size must be set to 0
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 6/6] FIX: sync_completed == 0 causes reshape cancellation in metadata
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 5/6] FIX: mdadm hangs during reshape
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 4/6] FIX: mdadm throws coredump on exit in error case
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 0/6] OLCE raid5/0 (all arrays in container)
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] fix: segfault if subarray is monitored but container is not
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/2] md/raid5: FIX: manually-added spare is not used
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH UPDATED] block: restore multiple bd_link_disk_holder() support
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
--chunk & pretend?
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: [PATCH 2/2] md/raid5: FIX: reshape on degraded devices has wrong configuration
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/2] md/raid5: FIX: manually-added spare is not used
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/2] md/raid5: FIX: manually-added spare is not used
- From: NeilBrown <neilb@xxxxxxx>
Re: (help!) MD RAID6 won't --re-add devices? [SOLVED!]
- From: Bart Kus <me@xxxxxxxx>
Re: read errors corrected
- From: Jaap Crezee <jaap@xxxxxx>
Re: (help!) MD RAID6 won't --re-add devices?
- From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
Re: RAID for USB flash drives
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: (help!) MD RAID6 won't --re-add devices?
- From: Bart Kus <me@xxxxxxxx>
Re: (help!) MD RAID6 won't --re-add devices?
- From: Bart Kus <me@xxxxxxxx>
Re: ata8.00: irq_stat 0xffffffff, unknown FIS / HSM violation?
- From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Re: read errors corrected
- From: Giovanni Tessore <giotex@xxxxxxxxxx>
ata8.00: irq_stat 0xffffffff, unknown FIS / HSM violation?
- From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Re: Question with --assume-clean
- From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Re: Quick question about parted/fdisk for 2TB disks.
- From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Re: Question with --assume-clean
- From: NeilBrown <neilb@xxxxxxx>
Re: Quick question about parted/fdisk for 2TB disks.
- From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
Quick question about parted/fdisk for 2TB disks.
- From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Question with --assume-clean
- From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Re: [PATCH] Update CONFIG_MD_RAID6_PQ to CONFIG_RAID6_PQ in drivers/dma/iop-adma.c
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
How do I get rid of md126, md127?
- From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Re: RAID for USB flash drives
- From: Hank Barta <hbarta@xxxxxxxxx>
Re: open_dev_excl in reshape_container() fails
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: raid6 recovery
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH UPDATED] block: restore multiple bd_link_disk_holder() support
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: "Ted Ts'o" <tytso@xxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Tejun Heo <tj@xxxxxxxxxx>
raid6 recovery
- From: Björn Englund <be@xxxxxxxxxxx>
[PATCH UPDATED] block: restore multiple bd_link_disk_holder() support
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 2/2] raid0->raid10 takeover- process metadata update
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 1/2] raid0->raid10 takeover- allocate memory for added disks
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 0/2] Supplement for raid0->raid10 takeover for imsm metadata
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
Re: filesystem on mdadm raid from unpartioned block devices
- From: GarBoge <garboge@xxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Kay Sievers <kay.sievers@xxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Karel Zak <kzak@xxxxxxxxxx>
Re: training mpath to discern between SCSI errors
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH 2/2] md/raid5: FIX: reshape on degraded devices has wrong configuration
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 1/2] md/raid5: FIX: manually-added spare is not used
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 0/2] fixes for manually-added spares in raid5 (2nd)
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 2/2] md/raid5: FIX: reshape on degraded devices has wrong configuration
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 1/2] md/raid5: FIX: manually-added spare is not used
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 0/2] fixes for manually-added spares in raid5
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH] imsm: FIX: spare cannot be added
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
RE: open_dev_excl in reshape_container() fails
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
Re: [PATCH] block: restore multiple bd_link_disk_holder() support
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
Re: training mpath to discern between SCSI errors
- From: Hannes Reinecke <hare@xxxxxxx>
RE: open_dev_excl in reshape_container() fails
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [RFC PATCH 0/3] differentiate between I/O errors
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: training mpath to discern between SCSI errors
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
PULL REQUEST - md updates for 2.6.38
- From: NeilBrown <neilb@xxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: "Ted Ts'o" <tytso@xxxxxxx>
[git pull] device-mapper patches for 2.6.38
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: NeilBrown <neilb@xxxxxxx>
Re: Speed up reshape? (was Re: Cancel reshape?)
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: [PATCH] block: restore multiple bd_link_disk_holder() support
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: open_dev_excl in reshape_container() fails
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[PATCH] block: restore multiple bd_link_disk_holder() support
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Kay Sievers <kay.sievers@xxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Karel Zak <kzak@xxxxxxxxxx>
RE: [PATCH 5/6] Remove code for non re-striping operations.
- From: "Wojcik, Krzysztof" <krzysztof.wojcik@xxxxxxxxx>
open_dev_excl in reshape_container() fails
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
[PATCH 6/6] raid0->raid10 takeover- allocate memory for added disks
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 5/6] raid0->raid10 takeover- create metadata update
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 4/6] Add raid10 -> raid0 takeover support
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 3/6] Unfreeze for non re-striping transitions
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 2/6] Set reshape.after.data_disks for raid0<->raid10 takeover
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 1/6] Define imsm_analyze_change function
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 0/6] Add raid0<->raid10 takeover support for imsm metadata
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
RE: [PATCH 2/9] FIX: Cannot add spare to monitored container
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
[PATCH] fix: Monitor: min_size must be set to 0
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Milan Broz <mbroz@xxxxxxxxxx>
[PATCH 5/6] FIX: mdadm hangs during reshape
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 6/6] FIX: sync_completed == 0 causes reshape cancellation in metadata
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 4/6] FIX: mdadm throws coredump on exit in error case
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 3/6] FIX: reshape raid0 on second array
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 2/6] FIX: continue raid0 reshape
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 1/6] imsm: Update metadata for second array
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 0/6] OLCE raid5/0 (all arrays in container)
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Theodore Tso <tytso@xxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Kay Sievers <kay.sievers@xxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: Speed up reshape? (was Re: Cancel reshape?)
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Karel Zak <kzak@xxxxxxxxxx>
[PATCH] fix: segfault if subarray is monitored but container is not
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
(help!) MD RAID6 won't --re-add devices?
- From: Bart Kus <me@xxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Karel Zak <kzak@xxxxxxxxxx>
Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Tejun Heo <tj@xxxxxxxxxx>
RE: [PATCH 7/8] Finalize reshape after adding disks to array
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH 2/9] FIX: Cannot add spare to monitored container
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 6/9] imsm: FIX: container content gathering is not needed for size set
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 5/6] Remove code for non re-striping operations.
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 6/6] Add raid10 -> raid0 takeover support
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 4/6] FIX: Mistake in delta_disk comparison.
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 3/6] Set delta_disks for raid10 -> raid0 takeover
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/6] Define imsm_analyze_change function
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/6] reshape_super reorganization
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 8/8] FIX: reload metadata for container operation
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 7/8] Finalize reshape after adding disks to array
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 6/8] imsm: FIX: spares are not counted
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 5/8] FIX: Cannot load container information
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 4/8] imsm: FIX: old devices memory has to be released
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 3/8] imsm: FIX: local mdadm update shouldn't be done in update creation function.
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/8] imsm: FIX: mdadm should process local data
- From: NeilBrown <neilb@xxxxxxx>
Re: linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
Re: filesystem on mdadm raid from unpartioned block devices
- From: NeilBrown <neilb@xxxxxxx>
Re: linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: filesystem on mdadm raid from unpartioned block devices
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: filesystem on mdadm raid from unpartioned block devices
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
filesystem on mdadm raid from unpartioned block devices
- From: GarBoge <garboge@xxxxxxx>
Re: 0001-md-FIX-raid5-should-accept-slot-set-by-mdadm
- From: NeilBrown <neilb@xxxxxxx>
Re: md raid5 blocked in get_active_stripe after disk failure
- From: NeilBrown <neilb@xxxxxxx>
Re: md raid5 blocked in get_active_stripe after disk failure
- From: NeilBrown <neilb@xxxxxxx>
linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac()
- From: Valdis.Kletnieks@xxxxxx
[PATCH 6/6] Add raid10 -> raid0 takeover support
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 5/6] Remove code for non re-striping operations.
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 4/6] FIX: Mistake in delta_disk comparison.
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 3/6] Set delta_disks for raid10 -> raid0 takeover
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 2/6] Define imsm_analyze_change function
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 1/6] reshape_super reorganization
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 0/6] raid10->raid0 takeover for imsm metadata
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
RE: [PATCH 2/9] FIX: Cannot add spare to monitored container
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
RE: [PATCH 6/9] imsm: FIX: container content gathering is not needed for size set
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
RE: [PATCH 3/9] imsm:FIX: one spare can be added to raid0 only
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
RE: [PATCH 10/13] FIX: Cannot unmount array after reshape
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
0001-md-FIX-raid5-should-accept-slot-set-by-mdadm
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: md raid5 blocked in get_active_stripe after disk failure
- From: David Flynn <davidf@xxxxxxxxxxxx>
[PATCH 8/8] FIX: reload metadata for container operation
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 7/8] Finalize reshape after adding disks to array
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 6/8] imsm: FIX: spares are not counted
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 5/8] FIX: Cannot load container information
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 4/8] imsm: FIX: old devices memory has to be released
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 3/8] imsm: FIX: local mdadm update shouldn't be done in update creation function.
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 2/8] imsm: FIX: mdadm should process local data
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 1/8] FIX: put update in to queue for local meta update
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 0/8] OLCE Raid5/0 single array for external meta
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
md raid5 blocked in get_active_stripe after disk failure
- From: David Flynn <davidf@xxxxxxxxxxxx>
Re: [PATCH 02/13] imsm: FIX: allow for container reshape any unset size value
- From: NeilBrown <neilb@xxxxxxx>
RE: [PATCH 02/13] imsm: FIX: allow for container reshape any unset size value
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: Reshape RAID5 to a RAID6 with more (smaller) devices
- From: NeilBrown <neilb@xxxxxxx>
Reshape RAID5 to a RAID6 with more (smaller) devices
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: advanced data recovery project for the wife - need help with raid6 layout P&Q ordering
- From: NeilBrown <neilb@xxxxxxx>
Re: Subject: [PATCH 4/4] imsm: support for raid0 <-> raid5 migration
- From: NeilBrown <neilb@xxxxxxx>
Re: Subject: [PATCH 3/4] Grow_reshape: need sub-array component size in data migration.
- From: NeilBrown <neilb@xxxxxxx>
Re: Subject: [PATCH 2/4] Grow_reshape: need text_version for sub-array processing.
- From: NeilBrown <neilb@xxxxxxx>
Re: Speed up reshape? (was Re: Cancel reshape?)
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 7/9] imsm: FIX: monitor should initialize 2nd reshape only
- From: NeilBrown <neilb@xxxxxxx>
Speed up reshape? (was Re: Cancel reshape?)
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: [PATCH 6/9] imsm: FIX: container content gathering is not needed for size set
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 5/9] imsm: Update metadata for second array
- From: NeilBrown <neilb@xxxxxxx>
advanced data recovery project for the wife - need help with raid6 layout P&Q ordering
- From: Brian Wolfe <brianw@xxxxxxxxxxxx>
Re: [PATCH 4/9] imsm: FIX: only one spare is passed in update
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 3/9] imsm:FIX: one spare can be added to raid0 only
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/9] FIX: Cannot add spare to monitored container
- From: NeilBrown <neilb@xxxxxxx>
Re: Cancel reshape?
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] Monitor: skip array if error getting size
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 13/13] FIX: Fill sys_name for disk add
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 12/13] FIX: parity disks use for redundant levels only
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 10/13] FIX: Cannot unmount array after reshape
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 09/13] Finalize reshape after adding disks to array
- From: NeilBrown <neilb@xxxxxxx>
Re: Cancel reshape?
- From: NeilBrown <neilb@xxxxxxx>
Re: Cancel reshape?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: [PATCH 08/13] FIX/WORKAROUND: added disks are not used by reshape process /md/
- From: NeilBrown <neilb@xxxxxxx>
Cancel reshape?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: [PATCH 06/13] imsm: FIX: update disks status in container_contents()
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 04/13] FIX: load anchor to get all information
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 03/13] imsm: FIX: when monitor is active post update
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 02/13] imsm: FIX: allow for container reshape any unset size value
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 01/13] Manage reshape process in manage_reshape vector.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 13/13] md: fix sync_completed reporting for very large drives (>2TB)
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 12/13] md: allow suspend_lo and suspend_hi to decrease as well as increase.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 11/13] md: Don't let implementation detail of curr_resync leak out through sysfs.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 10/13] md: separate meta and data devs
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 09/13] md-new-param-to_sync_page_io
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 08/13] md-new-param-to-calc_dev_sboffset
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 07/13] md: Be more careful about clearing flags bit in ->recovery
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 06/13] md: md_stop_writes requires mddev_lock.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 05/13] md/raid5: use sysfs_notify_dirent_safe to avoid NULL pointer
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 04/13] md: Ensure no IO request to get md device before it is properly initialised.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 03/13] md: Fix single printks with multiple KERN_<level>s
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 02/13] md: fix regression resulting in delays in clearing bits in a bitmap
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 01/13] md: fix regression with re-adding devices to arrays with no metadata
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 00/13] md patches for the current merge window
- From: NeilBrown <neilb@xxxxxxx>
Re: An extensible superblock
- From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
Re: An extensible superblock
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
Re: mdadm raid5 with lvm: advantages?
- From: Zdenek Kaspar <zkaspar82@xxxxxxxxx>
Re: mdadm raid5 with lvm: advantages?
- From: Roy Keene <linux-raid@xxxxxxxxxx>
Re: mdadm raid5 with lvm: advantages?
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: mdadm raid5 with lvm: advantages?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: mdadm raid5 with lvm: advantages?
- From: Zdenek Kaspar <zkaspar82@xxxxxxxxx>
An extensible superblock
- From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
Re: mdadm raid5 with lvm: advantages?
- From: CoolCold <coolthecold@xxxxxxxxx>
Subject: [PATCH 3/4] Grow_reshape: need sub-array component size in data migration.
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
Subject: [PATCH 4/4] imsm: support for raid0 <-> raid5 migration
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
Subject: [PATCH 1/4] Grow_reshape: need text version of device name in mdinfo.
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
Subject: [PATCH 2/4] Grow_reshape: need text_version for sub-array processing.
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH 0/4] RAID 0 to/from RAID5 migration
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
Re: mdadm raid5 with lvm: advantages?
- From: Jan Kasprzak <kas@xxxxxxxxxx>
Re: mdadm raid5 with lvm: advantages?
- From: Richard Grundy <richguk@xxxxxxxxx>
[PATCH 9/9] imsm: Proceed with second array reshape only for frozen container
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 8/9] FIX: container has to be frozen during reshape
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: mdadm raid5 with lvm: advantages?
- From: Steven Haigh <netwiz@xxxxxxxxx>
[PATCH 7/9] imsm: FIX: monitor should initialize 2nd reshape only
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 6/9] imsm: FIX: container content gathering is not needed for size set
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 5/9] imsm: Update metadata for second array
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 4/9] imsm: FIX: only one spare is passed in update
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 3/9] imsm:FIX: one spare can be added to raid0 only
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 2/9] FIX: Cannot add spare to monitored container
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 1/9] imsm: FIX: set correct slot information in metadata (raid0)
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 0/9] OLCE for external meta (cont.)
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
mdadm raid5 with lvm: advantages?
- From: Richard Grundy <richguk@xxxxxxxxx>
[PATCH] Monitor: skip array if error getting size
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
Re: [PATCH] md: fix sync_completed reporting for very large drives (>2TB)
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] md: fix sync_completed reporting for very large drives (>2TB)
- From: Rémi Rérolle <rrerolle@xxxxxxxxx>
GRUB2 MD RAID detection order
- From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
Re: [PATCH v3 0/8] dm-raid (raid456) target
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
[PATCH 13/13] FIX: Fill sys_name for disk add
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 12/13] FIX: parity disks use for redundant levels only
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 11/13] FIX/WORKAROUND: Arrays cannot be opened exclusively
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 10/13] FIX: Cannot unmount array after reshape
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 09/13] Finalize reshape after adding disks to array
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 08/13] FIX/WORKAROUND: added disks are not used by reshape process /md/
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 07/13] FIX: wrong flags are passed to function
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 06/13] imsm: FIX: update disks status in container_contents()
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 05/13] msm: FIX: when mdadm reloads anchor not need for local modyfication
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 04/13] FIX: load anchor to get all information
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 03/13] imsm: FIX: when monitor is active post update
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 02/13] imsm: FIX: allow for container reshape any unset size value
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 01/13] Manage reshape process in manage_reshape vector.
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 00/13] OLCE for external meta Raid5/single array
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: Bad sectors on a degraded array
- From: Alexander <freebsd@xxxxxxxxxxx>
Re: Considering a complete rework of RAID on my home compute server
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: What exactly does echo check > /sys/block/mdX/md/sync_action do?
- From: Christian Schmidt <charlie@xxxxxxxxx>
Re: What exactly does echo check > /sys/block/mdX/md/sync_action do?
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH v3 0/8] dm-raid (raid456) target
- From: NeilBrown <neilb@xxxxxxx>
Re: What exactly does echo check > /sys/block/mdX/md/sync_action do?
- From: Christian Schmidt <charlie@xxxxxxxxx>
RE: Considering a complete rework of RAID on my home compute server
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
Re: What exactly does echo check > /sys/block/mdX/md/sync_action do?
- From: NeilBrown <neilb@xxxxxxx>
What exactly does echo check > /sys/block/mdX/md/sync_action do?
- From: Christian Schmidt <charlie@xxxxxxxxx>
RE: [PATCH 2/2] Assemble: allow to assemble spares on their own
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices
- From: NeilBrown <neilb@xxxxxxx>
Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices
- From: Matthew Gabeler-Lee <cheetah@xxxxxxxxxxx>
Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices
- From: NeilBrown <neilb@xxxxxxx>
Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices
- From: Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@xxxxxxxxx>
Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices
- From: NeilBrown <neilb@xxxxxxx>
Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices
- From: Matthew Gabeler-Lee <cheetah@xxxxxxxxxxx>
Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices
- From: Matthew Gabeler-Lee <cheetah@xxxxxxxxxxx>
Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices
- From: Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@xxxxxxxxx>
Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices
- From: Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@xxxxxxxxx>
Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices
- From: Matthew Gabeler-Lee <cheetah@xxxxxxxxxxxxxxxxxxx>
2 RAID devices with index 0 [Fwd: Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices]
- From: Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@xxxxxxxxx>
Re: Patch to issue pure flushes directly (Was: Re: [PATCH v6 0/4] ext4: Coordinate data-only flush requests sent) by fsync
- From: Tejun Heo <tj@xxxxxxxxxx>
Bad sectors on a degraded array
- From: FLD <fld@xxxxxxxxxx>
Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices
- From: Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@xxxxxxxxx>
Re: Patch to issue pure flushes directly (Was: Re: [PATCH v6 0/4] ext4: Coordinate data-only flush requests sent) by fsync
- From: Christoph Hellwig <hch@xxxxxx>
Patch to issue pure flushes directly (Was: Re: [PATCH v6 0/4] ext4: Coordinate data-only flush requests sent) by fsync
- From: "Ted Ts'o" <tytso@xxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: NeilBrown <neilb@xxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Michael Biebl <mbiebl@xxxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
Re: Considering a complete rework of RAID on my home compute server
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: Is It Hopeless?
- From: Berkey B Walker <berk@xxxxxxxxx>
Re: [PATCH v3 0/8] dm-raid (raid456) target
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
Re: [dm-devel] [PATCH v3 0/8] dm-raid (raid456) target
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
Re: Considering a complete rework of RAID on my home compute server
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: [dm-devel] [PATCH v3 0/8] dm-raid (raid456) target
- From: Phillip Susi <psusi@xxxxxxxxxx>
Re: [PATCH v3 0/8] dm-raid (raid456) target
- From: NeilBrown <neilb@xxxxxxx>
Re: Considering a complete rework of RAID on my home compute server
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: [PATCH 00/34] OLCE for external metadata (devel3.2)
- From: NeilBrown <neilb@xxxxxxx>
RE: fd partitions gone from 2 discs, md happy with it and reconstructs... bye bye datas
- From: "Philippe PIOLAT" <piolat@xxxxxxxxxxxx>
RE: Considering a complete rework of RAID on my home compute server
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
Re: Considering a complete rework of RAID on my home compute server
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Considering a complete rework of RAID on my home compute server
- From: Roman Mamedov <rm@xxxxxxxxxx>
RE: Considering a complete rework of RAID on my home compute server
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
RE: Is It Hopeless?
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
Re: [PATCH v3 0/8] dm-raid (raid456) target
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
RE: Is It Hopeless?
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
Re: filesystem corruption
- From: "Patrick H." <linux-raid@xxxxxxxxxxxx>
Re: filesystem corruption
- From: Spelic <spelic@xxxxxxxxxxxxx>
Re: Is It Hopeless?
- From: Hank Barta <hbarta@xxxxxxxxx>
Re: filesystem corruption
- From: "Patrick H." <linux-raid@xxxxxxxxxxxx>
Re: Absymal performance of O_DIRECT write on parity raid
- From: Spelic <spelic@xxxxxxxxxxxxx>
Re: filesystem corruption
- From: CoolCold <coolthecold@xxxxxxxxx>
Re: [PATCH 0/3] deal with imsm spares in Incremental
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/2] Assemble: allow to assemble spares on their own
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/2] Assemble: we need to read policy to know array domains
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/3] Assemble imsm spares in matching domain only
- From: NeilBrown <neilb@xxxxxxx>
Re: filesystem corruption
- From: "Patrick H." <linux-raid@xxxxxxxxxxxx>
Re: dmaengine: fix dma_unmap (was: Re: [PATCH 06/13] DMAENGINE: driver for the ARM PL080/PL081 PrimeCells)
- From: Linus Walleij <linus.ml.walleij@xxxxxxxxx>
Re: RAID for USB flash drives
- From: Iordan Iordanov <iordan@xxxxxxxxxxxxxxx>
Re: Internal bitmap always 1/1
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID for USB flash drives
- From: Steven Haigh <netwiz@xxxxxxxxx>
Re: RAID for USB flash drives
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: Is It Hopeless?
- From: Phillip Susi <psusi@xxxxxxxxxx>
RAID for USB flash drives
- From: Hank Barta <hbarta@xxxxxxxxx>
Re: filesystem corruption
- From: "Patrick H." <linux-raid@xxxxxxxxxxxx>
Re: Internal bitmap always 1/1
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: RAID-10 initial sync is CPU-limited
- From: Jan Kasprzak <kas@xxxxxxxxxx>
Re: RAID-10 initial sync is CPU-limited
- From: Jan Kasprzak <kas@xxxxxxxxxx>
Re: RAID-10 initial sync is CPU-limited
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Internal bitmap always 1/1
- From: Andrea Gelmini <andrea.gelmini@xxxxxxxxx>
Re: RAID-10 initial sync is CPU-limited
- From: Jan Kasprzak <kas@xxxxxxxxxx>
[PATCH] md: fix sync_completed reporting for very large drives (>2TB)
- From: Rémi Rérolle <remi.rerolle@xxxxxxxxx>
Re: New raid level suggestion.
- From: Rogier Wolff <R.E.Wolff@xxxxxxxxxxxx>
[PATCH 3/3] Incremental: move suitable spares to container when subarrays started.
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
PATCH 2/3] move_spare function modified and moved to Manage.c
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
[PATCH 1/3] Use one function chosing spares from container
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
[PATCH 0/3] deal with imsm spares in Incremental
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
Re: RAID-10 initial sync is CPU-limited
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: RAID-10 initial sync is CPU-limited
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
[PATCH 34/34] Raid0: detect reshape on array start
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 33/34] Raid0: Reload disk list on 'next' raid0 array
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 32/34] Raid0: Run 'next' reshapes without meta update
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 31/34] imsm: FIX: do not repair raid4 arrays
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 30/34] Raid0: execute backward takeover
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 29/34] Detect level change
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 28/34] Take in mind takeover during disk add
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 27/34] imsm: Update raid0 metadata for reshape
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 26/34] imsm: Move reshape update processing to function
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 25/34] Add spares to raid0 in mdadm
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 24/34] imsm: Update metadata for second array
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 23/34] Set array size after adding new disks
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 22/34] imsm: update array size information in metadata
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 21/34] FIX: Initialize subarray variable in reshape_array
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 20/34] imsm: FIX: Division by 0
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 19/34] imsm: Finalize reshape in metadata
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 18/34] Finalize reshape after adding disks to array
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 17/34] imsm: FIX: Fill sys_name in container_content()
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 16/34] FIX: Use sysfs to change array parameters
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 15/34] FIX: added disks are not used by reshape process /md/
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 14/34] FIX: change adding disks criteria
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 13/34] FIX: Get array information in reshape_array()
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 12/34] imsm: FIX: support general migration by getinfo_super_imsm_volume
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 10/34] imsm: FIX: update first array in container only
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 11/34] FIX: Arrays cannot be opened exclusively
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 09/34] FIX: get updated information from metadata
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 08/34] imsm: FIX: Do not update anchor directly
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 07/34] imsm: FIX: Perform first metadata update for container operation
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 06/34] imsm: FIX: display error message
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 05/34] imsm: FIX: display correct information for '-E' option
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 04/34] mdadm: second_map enhancement for imsm_get_map()
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 03/34] FIX: Position calculation in mdstat_by_subdev
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 02/34] FIX: Change size condition in imsm_reshape_is_allowed_on_container
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 01/34] Manage reshape process in manage_reshape vector.
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 00/34] OLCE for external metadata (devel3.2)
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 2/2] Assemble: allow to assemble spares on their own
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
[PATCH 1/2] Assemble: we need to read policy to know array domains
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
RE: [PATCH 2/3] Assemble imsm spares in matching domain only
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
Re: [Slightly OT] Cheap 4-port PCI-E SATA card?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
RE: fd partitions gone from 2 discs, md happy with it and reconstructs... bye bye datas
- From: "Philippe PIOLAT" <piolat@xxxxxxxxxxxx>
Re: RAID-10 initial sync is CPU-limited
- From: NeilBrown <neilb@xxxxxxx>
Re: fd partitions gone from 2 discs, md happy with it and reconstructs... bye bye datas
- From: NeilBrown <neilb@xxxxxxx>
fd partitions gone from 2 discs, md happy with it and reconstructs... bye bye datas
- From: "Philippe PIOLAT" <piolat@xxxxxxxxxxxx>
Re: RAID-10 initial sync is CPU-limited
- From: Jan Kasprzak <kas@xxxxxxxxxx>
Re: filesystem corruption
- From: "Patrick H." <linux-raid@xxxxxxxxxxxx>
Re: filesystem corruption
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID-10 initial sync is CPU-limited
- From: NeilBrown <neilb@xxxxxxx>
Re: [Slightly OT] Cheap 4-port PCI-E SATA card?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: dmaengine: fix dma_unmap (was: Re: [PATCH 06/13] DMAENGINE: driver for the ARM PL080/PL081 PrimeCells)
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [Slightly OT] Cheap 4-port PCI-E SATA card?
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: [Slightly OT] Cheap 4-port PCI-E SATA card?
- From: "Sven Eschenberg" <sven@xxxxxxxxxxxxxxxxxxxxx>
Re: dmaengine: fix dma_unmap (was: Re: [PATCH 06/13] DMAENGINE: driver for the ARM PL080/PL081 PrimeCells)
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
dmaengine: fix dma_unmap (was: Re: [PATCH 06/13] DMAENGINE: driver for the ARM PL080/PL081 PrimeCells)
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
RAID-10 initial sync is CPU-limited
- From: Jan Kasprzak <kas@xxxxxxxxxx>
Re: [Slightly OT] Cheap 4-port PCI-E SATA card?
- From: Roman Mamedov <rm@xxxxxxxxxx>
mdadm confusion between whole disk and partition
- From: Andrew Burgess <aab@xxxxxxxxxxx>
Re: [Slightly OT] Cheap 4-port PCI-E SATA card?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: [Slightly OT] Cheap 4-port PCI-E SATA card?
- From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Re: [Slightly OT] Cheap 4-port PCI-E SATA card?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: [Slightly OT] Cheap 4-port PCI-E SATA card?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: [Slightly OT] Cheap 4-port PCI-E SATA card?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
[GIT] dmaengine fixes for 2.6.37-rc8
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [Slightly OT] Cheap 4-port PCI-E SATA card?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: filesystem corruption
- From: "Patrick H." <linux-raid@xxxxxxxxxxxx>
Re: filesystem corruption
- From: Neil Brown <neilb@xxxxxxx>
RE: New raid level suggestion.
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
RE: Mismatches
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
Re: filesystem corruption
- From: Neil Brown <neilb@xxxxxxx>
RE: Mismatches
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
filesystem corruption
- From: "Patrick H." <linux-raid@xxxxxxxxxxxx>
Re: Mismatches
- From: Mark Knecht <markknecht@xxxxxxxxx>
RE: Mismatches
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
Re: Mismatches
- From: Neil Brown <neilb@xxxxxxx>
Re: Mismatches
- From: Mark Knecht <markknecht@xxxxxxxxx>
Mismatches
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
Re: [Slightly OT] Cheap 4-port PCI-E SATA card?
- From: Matt Garman <matthew.garman@xxxxxxxxx>
Re: [Slightly OT] Cheap 4-port PCI-E SATA card?
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: [Slightly OT] Cheap 4-port PCI-E SATA card?
- From: Roman Mamedov <rm@xxxxxxxxxx>
[Slightly OT] Cheap 4-port PCI-E SATA card?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: How To Remove Rogue RAID
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
How To Remove Rogue RAID
- From: Carlos Mennens <carloswill@xxxxxxxxx>
Re: Guidance on how to best assemble new root drive?
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: Guidance on how to best assemble new root drive?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Guidance on how to best assemble new root drive?
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: New raid level suggestion.
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Absymal performance of O_DIRECT write on parity raid
- From: Doug Dumitru <doug@xxxxxxxxxx>
Absymal performance of O_DIRECT write on parity raid
- From: Spelic <spelic@xxxxxxxxxxxxx>
Re: Why won't mdadm start several RAIDs that appear to be fine? SOLVED!
- From: Jim Schatzman <james.schatzman@xxxxxxxxxxxxxxxx>
Re: Why won't mdadm start several RAIDs that appear to be fine? Info from "mdadm -A --verbose"
- From: Jim Schatzman <james.schatzman@xxxxxxxxxxxxxxxx>
Re: read errors corrected
- From: Neil Brown <neilb@xxxxxxx>
RE: read errors corrected
- From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
Re: read errors corrected
- From: James <jtp@xxxxxxxxx>
Re: Why does md3 persist after deleting and recreating the partitions?
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: Why won't mdadm start several RAIDs that appear to be fine?
- From: Neil Brown <neilb@xxxxxxx>
Re: Why does md3 persist after deleting and recreating the partitions?
- From: Neil Brown <neilb@xxxxxxx>
Re: Why does md3 persist after deleting and recreating the partitions?
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: Why does md3 persist after deleting and recreating the partitions?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: Why does md3 persist after deleting and recreating the partitions?
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: Why does md3 persist after deleting and recreating the partitions?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Why does md3 persist after deleting and recreating the partitions?
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: Why won't mdadm start several RAIDs that appear to be fine? (more info)
- From: Jim Schatzman <james.schatzman@xxxxxxxxxxxxxxxx>
Re: Why won't mdadm start several RAIDs that appear to be fine?
- From: Jim Schatzman <james.schatzman@xxxxxxxxxxxxxxxx>
Re: read errors corrected
- From: Neil Brown <neilb@xxxxxxx>
Re: read errors corrected
- From: Richard Scobie <r.scobie@xxxxxxxxxxxx>
Re: Raid/5 optimization for linear writes
- From: Doug Dumitru <doug@xxxxxxxxxx>
Re: New raid level suggestion.
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: read errors corrected
- From: James <jtp@xxxxxxxxx>
Re: read errors corrected
- From: Ryan Wagoner <rswagoner@xxxxxxxxx>
Re: read errors corrected
- From: James <jtp@xxxxxxxxx>
Re: read errors corrected
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: read errors corrected
- From: James <jtp@xxxxxxxxx>
Re: read errors corrected
- From: James <jtp@xxxxxxxxx>
Re: read errors corrected
- From: James <jtp@xxxxxxxxx>
Re: Raid/5 optimization for linear writes
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: New raid level suggestion.
- From: Ryan Wagoner <rswagoner@xxxxxxxxx>
Re: New raid level suggestion.
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: New raid level suggestion.
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: New raid level suggestion.
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: read errors corrected
- From: Giovanni Tessore <giotex@xxxxxxxxxx>
Re: New raid level suggestion.
- From: Neil Brown <neilb@xxxxxxx>
Re: New raid level suggestion.
- From: Rogier Wolff <R.E.Wolff@xxxxxxxxxxxx>
Re: read errors corrected
- From: Neil Brown <neilb@xxxxxxx>
Re: New raid level suggestion.
- From: Steven Haigh <netwiz@xxxxxxxxx>
New raid level suggestion.
- From: Rogier Wolff <R.E.Wolff@xxxxxxxxxxxx>
Re: read errors corrected
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
read errors corrected
- From: James <jtp@xxxxxxxxx>
Considering a complete rework of RAID on my home compute server
- From: Mark Knecht <markknecht@xxxxxxxxx>
[PATCH] Update CONFIG_MD_RAID6_PQ to CONFIG_RAID6_PQ in drivers/dma/iop-adma.c
- From: Wei Yongquan <weiyqlq@xxxxxxxxx>
RE: [PATCH 00/29] OLCE, migrations and raid10 takeover
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH 00/29] OLCE, migrations and raid10 takeover
- From: Neil Brown <neilb@xxxxxxx>
Re: Is It Hopeless?
- From: Roman Mamedov <rm@xxxxxxxxxx>
Raid/5 optimization for linear writes
- From: Doug Dumitru <doug@xxxxxxxxxx>
Re: Is It Hopeless?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Partitions not recognized when auto-assembling array in initramfs
- From: Wolfgang Denk <wd@xxxxxxx>
Re: md-raid and block sizes
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: md-raid and block sizes
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: md-raid and block sizes
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Partitions not recognized when auto-assembling array in initramfs
- From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
Re: md-raid and block sizes
- From: Neil Brown <neilb@xxxxxxx>
Re: md-raid and block sizes
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: md-raid and block sizes
- From: hansbkk@xxxxxxxxx
RE: [PATCH 00/29] OLCE, migrations and raid10 takeover
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: md-raid and block sizes
- From: "D.S. Ljungmark" <spider@xxxxxxxxxx>
Re: Partitions not recognized when auto-assembling array in initramfs
- From: Neil Brown <neilb@xxxxxxx>
Re: Partitions not recognized when auto-assembling array in initramfs
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: Is It Hopeless?
- From: Carl Cook <CACook@xxxxxxxxxxxxxxx>
Re: [PATCH 00/29] OLCE, migrations and raid10 takeover
- From: Neil Brown <neilb@xxxxxxx>
Re: Is It Hopeless?
- From: Berkey B Walker <berk@xxxxxxxxx>
Re: Partitions not recognized when auto-assembling array in initramfs
- From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
Re: Is It Hopeless?
- From: Brad Campbell <brad@xxxxxxxxxxx>
Re: Partitions not recognized when auto-assembling array in initramfs
- From: Neil Brown <neilb@xxxxxxx>
Re: Partitions not recognized when auto-assembling array in initramfs
- From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
Re: Partitions not recognized when auto-assembling array in initramfs
- From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
Re: Partitions not recognized when auto-assembling array in initramfs
- From: Neil Brown <neilb@xxxxxxx>
Re: md-raid and block sizes
- From: Doug Dumitru <doug@xxxxxxxxxx>
Re: Is It Hopeless?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Aliens ate my superblock!
- From: Jean de Largentaye <jean@xxxxxxxxxxxxxx>
Partitions not recognized when auto-assembling array in initramfs
- From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
Re: Is It Hopeless?
- From: Phil Turmel <philip@xxxxxxxxxx>
RE: [PATCH 00/29] OLCE, migrations and raid10 takeover
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: Is It Hopeless?
- From: Carl Cook <CACook@xxxxxxxxxxxxxxx>
md-raid and block sizes
- From: "D.S. Ljungmark" <spider@xxxxxxxxxx>
Re: using poll on /proc/mdstat
- From: Neil Brown <neilb@xxxxxxx>
Re: Is It Hopeless?
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Is It Hopeless?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Re: using poll on /proc/mdstat
- From: "kernel.majianpeng" <kernel.majianpeng@xxxxxxxxx>
Re: Is It Hopeless?
- From: Carl Cook <CACook@xxxxxxxxxxxxxxx>
Re: Is It Hopeless?
- From: Berkey B Walker <berk@xxxxxxxxx>
Re: Is It Hopeless?
- From: Neil Brown <neilb@xxxxxxx>
Re: Is It Hopeless?
- From: CoolCold <coolthecold@xxxxxxxxx>
Re: Is It Hopeless?
- From: Carl Cook <CACook@xxxxxxxxxxxxxxx>
Re: Is It Hopeless?
- From: Neil Brown <neilb@xxxxxxx>
Is It Hopeless?
- From: Carl Cook <CACook@xxxxxxxxxxxxxxx>
Re: using poll on /proc/mdstat
- From: Neil Brown <neilb@xxxxxxx>
Re: [PATCH 0/5] Autorebuild, spare/spare-same-slot fixes
- From: Neil Brown <neilb@xxxxxxx>
Re: [PATCH 1/5] external: get number of failed disks for container
- From: Neil Brown <neilb@xxxxxxx>
Re: [PATCH 2/3] Assemble imsm spares in matching domain only
- From: Neil Brown <neilb@xxxxxxx>
Re: [PATCH] Enable tests for OLCE, takeover, migrations for imsm metadata
- From: Neil Brown <neilb@xxxxxxx>
Re: [PATCH] FIX: Bad block verification during assembling array
- From: Neil Brown <neilb@xxxxxxx>
[no subject]
- From: "kernel.majianpeng" <kernel.majianpeng@xxxxxxxxx>
Re: Aliens ate my superblock!
- From: Spelic <spelic@xxxxxxxxxxxxx>
Aliens ate my superblock!
- From: Jean de Largentaye <jean@xxxxxxxxxxxxxx>
[PATCH 5/5] Consider target only for spare-same-domain
- From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
[PATCH 4/5] Validate size of potential spare disk for external metadata (with containers)
- From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
[PATCH 3/5] Skip domain check for spare-same-slot
- From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
[PATCH 2/5] Added test for array degradation for spare-same-slot
- From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
[PATCH 0/5] Autorebuild, spare/spare-same-slot fixes
- From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
[PATCH 1/5] external: get number of failed disks for container
- From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
RE: Autorebuild, new dynamic udev rules for hot-plugs
- From: "Hawrylewicz Czarnowski, Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
[PATCH 2/3] Assemble imsm spares in matching domain only
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
[PATCH 3/3] Assemble loose imsm spares.
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
[PATCH 1/3] imsm: set imsm spare uuid to 0
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
[PATCH] Enable tests for OLCE, takeover, migrations for imsm metadata
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
Re: [PATCH] mv_xor: fix race in tasklet function
- From: saeed bishara <saeed.bishara@xxxxxxxxx>
Re: reshape changing chunk size won't restart
- From: Andrew Burgess <aab@xxxxxxxxxxx>
Re: reshape changing chunk size won't restart
- From: Neil Brown <neilb@xxxxxxx>
Re: reshape changing chunk size won't restart
- From: Andrew Burgess <aab@xxxxxxxxxxx>
Re: reshape changing chunk size won't restart
- From: Neil Brown <neilb@xxxxxxx>
Re: reshape changing chunk size won't restart
- From: Andrew Burgess <aab@xxxxxxxxxxx>
Re: reshape changing chunk size won't restart
- From: Neil Brown <neilb@xxxxxxx>
Re: best way to try recovering inactive raid6
- From: Bjørn Eikeland <beikeland@xxxxxxxxx>
reshape changing chunk size won't restart
- From: Andrew Burgess <aab@xxxxxxxxxxx>
[PATCH] mv_xor: fix race in tasklet function
- From: Saeed Bishara <saeed@xxxxxxxxxxx>
Re: [PATCH 00/29] OLCE, migrations and raid10 takeover
- From: Neil Brown <neilb@xxxxxxx>
Re: [PATCH v3 0/8] dm-raid (raid456) target
- From: Neil Brown <neilb@xxxxxxx>
[PATCH v3 6/8] dm: per-target unplug callback support
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH v3 8/8] dm raid: add suspend and resume functions
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH v3 7/8] dm raid: add iterate_devices and io_hints functions
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH v3 4/8] dm raid: skeleton raid456 target support
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH v3 5/8] dm: introduce target callbacks and congestion callback
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH v3 3/8] md/raid5: use sysfs_notify_dirent_safe to avoid NULL pointer
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH v3 2/8] md/bitmap: use DIV_ROUND_UP in bitmap_init_from_disk
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH v3 1/8] md/bitmap: revert dm-dirty-log preparation
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH v3 0/8] dm-raid (raid456) target
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 0/2] Fixes for Incremental()
- From: Neil Brown <neilb@xxxxxxx>
Re: [PATCH] Monitor: Check destination array domain early.
- From: Neil Brown <neilb@xxxxxxx>
feature - read balance
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: [PATCH 00/29] OLCE, migrations and raid10 takeover
- From: Neil Brown <neilb@xxxxxxx>
Re: BUG after md/raid10:md0: not enough operational mirrors.
- From: Ilia Mirkin <imirkin@xxxxxxxxxxxx>
RE: [PATCH 00/29] OLCE, migrations and raid10 takeover
- From: "Wojcik, Krzysztof" <krzysztof.wojcik@xxxxxxxxx>
Re: best way to try recovering inactive raid6
- From: Bjørn Eikeland <beikeland@xxxxxxxxx>
Re: best way to try recovering inactive raid6
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
best way to try recovering inactive raid6
- From: Bjørn Eikeland <beikeland@xxxxxxxxx>
Kernel panic with mdadm 3.1.4 on Ubuntu Lucid 64-bit
- From: "fibreraid@xxxxxxxxx" <fibreraid@xxxxxxxxx>
Re: integrity verification on raid-5?
- From: Roman Mamedov <roman@xxxxxxxx>
Re: integrity verification on raid-5?
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
Re: integrity verification on raid-5?
- From: "Patrick H." <linux-raid@xxxxxxxxxxxx>
Re: integrity verification on raid-5?
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: integrity verification on raid-5?
- From: "Patrick H." <linux-raid@xxxxxxxxxxxx>
Re: integrity verification on raid-5?
- From: Neil Brown <neilb@xxxxxxx>
integrity verification on raid-5?
- From: "Patrick H." <linux-raid@xxxxxxxxxxxx>
Re: reproducer for DM on MD flush deadlock? (was: Re: [PULL REQUEST] md bug fixes)
- From: Neil Brown <neilb@xxxxxxx>
reproducer for DM on MD flush deadlock? (was: Re: [PULL REQUEST] md bug fixes)
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH 2/2] fix: incremental for bare disks returns invalid value
- From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
[PATCH 1/2] fix: adding spare via incremental do not trigger recovery
- From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
[PATCH 0/2] Fixes for Incremental()
- From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
Re: training mpath to discern between SCSI errors
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH] Monitor: Check destination array domain early.
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
Re: [PATCH][rfc] md: Close mem leak in userspace_ctr()
- From: Jesper Juhl <jj@xxxxxxxxxxxxx>
Re: training mpath to discern between SCSI errors
- From: Hannes Reinecke <hare@xxxxxxx>
Re: raid0 to raid10 takeover bug
- From: Neil Brown <neilb@xxxxxxx>
raid0 to raid10 takeover bug
- From: "Wojcik, Krzysztof" <krzysztof.wojcik@xxxxxxxxx>
[PATCH] FIX: Bad block verification during assembling array
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
Re: raid1 module is not ready to take IO request
- From: Neil Brown <neilb@xxxxxxx>
Re: [PATCH 00/29] OLCE, migrations and raid10 takeover
- From: Neil Brown <neilb@xxxxxxx>
RE: raid1 module is not ready to take IO request
- From: "Hawrylewicz Czarnowski, Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
Re: [PATCH] imsm: FIX: imsm_add_spare() wrongly tests spares list
- From: Neil Brown <neilb@xxxxxxx>
Re: raid1 module is not ready to take IO request
- From: Neil Brown <neilb@xxxxxxx>
Re: mdadm incremental failed: md device busy
- From: Spelic <spelic@xxxxxxxxxxxxx>
Re: inactive device
- From: Spelic <spelic@xxxxxxxxxxxxx>
mdadm incremental failed: md device busy
- From: Spelic <spelic@xxxxxxxxxxxxx>
raid1 module is not ready to take IO request
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
inactive device
- From: raincatsdogs@xxxxxx
[PATCH] imsm: FIX: do not load migration record from spare disk
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH] imsm: FIX: imsm_add_spare() wrongly tests spares list
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: [PATCH][rfc] md: Close mem leak in userspace_ctr()
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH] fix: Monitor doesn't return after starting daemon
- From: Neil Brown <neilb@xxxxxxx>
RE: [PATCH] Finding spare devices for grow - rework
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH] fix: Monitor doesn't return after starting daemon
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
[PATCH] imsm: FIX: remove update_reshape_set_slots update message
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: Debugging a strange array corruption
- From: Roman Mamedov <roman@xxxxxxxx>
Re: Debugging a strange array corruption
- From: "David W." <darewi@xxxxxxxxx>
Re: Debugging a strange array corruption
- From: Brad Campbell <brad@xxxxxxxxxxx>
Re: Debugging a strange array corruption
- From: Roman Mamedov <roman@xxxxxxxx>
Re: Debugging a strange array corruption
- From: Brad Campbell <brad@xxxxxxxxxxx>
Re: Debugging a strange array corruption
- From: Roman Mamedov <roman@xxxxxxxx>
Debugging a strange array corruption
- From: Brad Campbell <brad@xxxxxxxxxxx>
RE: [PATCH 02/29] imsm: Prepare reshape_update in mdadm
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
[PULL REQUEST] md bug fixes
- From: Neil Brown <neilb@xxxxxxx>
Re: PATCH 1/2] IMSM: Fix problem in mdmon monitor of using removed disk from in imsm container.
- From: Neil Brown <neilb@xxxxxxx>
Re: [PATCH 02/29] imsm: Prepare reshape_update in mdadm
- From: Neil Brown <neilb@xxxxxxx>
[PATCH][rfc] md: Close mem leak in userspace_ctr()
- From: Jesper Juhl <jj@xxxxxxxxxxxxx>
PATCH 2/2] IMSM: do not rebuild the array if a non-redundant sub-array with failed disks is present
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
PATCH 1/2] IMSM: Fix problem in mdmon monitor of using removed disk from in imsm container.
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH] Finding spare devices for grow - rework
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH 16/16] Allow for reshape without backup file
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 15/16] imsm Fix: Core during rebuild on array details read
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 14/16] mdadm: support grow operation for external meta using checkpointing
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 13/16] Add mdadm->mdmon sync_max command message
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 12/16] mdadm: migration restart for external meta
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 11/16] mdadm: support backup operations for imsm
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 10/16] mdadm: support restore_stripes() from the given buffer
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>

[Index of Archives] [Linux RAID Wiki] [ATA RAID] [Linux SCSI Target Infrastructure] [Linux Block] [Linux IDE] [Linux SCSI] [Linux Hams] [Device Mapper] [Kernel] [Linux Admin] [Linux Net] [GFS] [RPM] [git] [Yosemite Forum] [Linux Networking]