Linux RAID Storage Date Index

Thread Index

Re: [PATCH] fix: Monitor sometimes crashes
- From: NeilBrown <neilb@xxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID10 only using 2/4 drives
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: Gilbert Kowarzyk <kowarzyk@xxxxxxxxxxxxxx>
RAID10 only using 2/4 drives
- From: Josh Reynolds <josh.reynolds@xxxxxxxxxxxxxxxxxx>
[PATCH] fix: Monitor sometimes crashes
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
Re: [PATCH][RFC] RAID5/DMA/memcpy: zero copy the bio page when possible
- From: NeilBrown <neilb@xxxxxxx>
RE: [PATCH][RFC] RAID5/DMA/memcpy: zero copy the bio page when possible
- From: Shi Xuelin-B29237 <B29237@xxxxxxxxxxxxx>
[PATCH][RFC] RAID5/DMA/memcpy: zero copy the bio page when possible
- From: <b29237@xxxxxxxxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: NeilBrown <neilb@xxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: Gilbert Kowarzyk <kowarzyk@xxxxxxxxxxxxxx>
Re: Renaming MD devices (metadata=1.1) [SOLVED]
- From: Gilbert Kowarzyk <kowarzyk@xxxxxxxxxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: NeilBrown <neilb@xxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: Gilbert Kowarzyk <kowarzyk@xxxxxxxxxxxxxx>
Re: raid array with 3T disks and GPT partition
- From: Phillip Susi <psusi@xxxxxxxxxx>
RE: Meaning of "Used Dev Space" in "mdadm --detail" output for a 6 disk RAID10 array
- From: Bobby Kent <bpkent@xxxxxxxxxxxxxxxxxxxx>
[PULL REQUEST] two bugfixes for md.
- From: NeilBrown <neilb@xxxxxxx>
Re: Meaning of "Used Dev Space" in "mdadm --detail" output for a 6 disk RAID10 array
- From: NeilBrown <neilb@xxxxxxx>
RE: Meaning of "Used Dev Space" in "mdadm --detail" output for a 6 disk RAID10 array
- From: Bobby Kent <bpkent@xxxxxxxxxxxxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: polling mdX/md/degraded in sysfs
- From: Mikhail Balabin <mbalabin@xxxxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: Michal Soltys <soltys@xxxxxxxx>
Renaming MD devices (metadata=1.1)
- From: Gilbert Kowarzyk <kowarzyk@xxxxxxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Meaning of "Used Dev Space" in "mdadm --detail" output for a 6 disk RAID10 array
- From: NeilBrown <neilb@xxxxxxx>
Meaning of "Used Dev Space" in "mdadm --detail" output for a 6 disk RAID10 array
- From: Bobby Kent <bpkent@xxxxxxxxxxxxxxxxxxxx>
Re: "md_raid5: page allocation failure" when resyncing on 3.2
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Giving top priority to a rebuild instead of serving userland?
- From: Anssi Hannula <anssi.hannula@xxxxxx>
Re: "md_raid5: page allocation failure" when resyncing on 3.2
- From: Konstantinos Skarlatos <k.skarlatos@xxxxxxxxx>
Re: Giving top priority to a rebuild instead of serving userland?
- From: Martin Cracauer <cracauer@xxxxxxxx>
Re: Giving top priority to a rebuild instead of serving userland?
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: raid1d crash at boot
- From: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
Re: SMART, RAID and real world experience of failures.
- From: pg@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: "md_raid5: page allocation failure" when resyncing on 3.2
- From: Roman Mamedov <rm@xxxxxxxxxx>
"md_raid5: page allocation failure" when resyncing on 3.2
- From: Konstantinos Skarlatos <k.skarlatos@xxxxxxxxx>
Re: SMART, RAID and real world experience of failures.
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: SMART, RAID and real world experience of failures.
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: SMART, RAID and real world experience of failures.
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Giving top priority to a rebuild instead of serving userland?
- From: Martin Cracauer <cracauer@xxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: raid 1 bug with write-mostly and administrative failed disk
- From: Art -kwaak- van Breemen <ard@xxxxxxxxxxxxxxx>
Re: polling mdX/md/degraded in sysfs
- From: Mikhail Balabin <mbalabin@xxxxxxxxx>
Wiki problems
- From: Sven Hartrumpf <hartrumpf@xxxxxxx>
Re: recovery from multiple failures
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: recovery from multiple failures
- From: NeilBrown <neilb@xxxxxxx>
Re: recovery from multiple failures
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: recovery from multiple failures
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: recovery from multiple failures
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: raid1d crash at boot
- From: NeilBrown <neilb@xxxxxxx>
Re: raid 1 bug with write-mostly and administrative failed disk
- From: NeilBrown <neilb@xxxxxxx>
Re: recovery from multiple failures
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: polling mdX/md/degraded in sysfs
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid5 device hangs in active state
- From: NeilBrown <neilb@xxxxxxx>
Re: recovery from multiple failures
- From: Phil Turmel <philip@xxxxxxxxxx>
Raid5 device hangs in active state
- From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
Re: [PULL REQUEST] md for 3.3
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Re: [PULL REQUEST] md for 3.3
- From: NeilBrown <neilb@xxxxxxx>
Re: [PULL REQUEST] md for 3.3
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
recovery from multiple failures
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: polling mdX/md/degraded in sysfs
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: polling mdX/md/degraded in sysfs
- From: Mikhail Balabin <mbalabin@xxxxxxxxx>
Re: polling mdX/md/degraded in sysfs
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Install grub2 to /dev/md126 fails
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: What just happened to my disks/RAID5 array?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: raid1d crash at boot
- From: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: raid 1 bug with write-mostly and administrative failed disk
- From: Art -kwaak- van Breemen <ard@xxxxxxxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Jan Kasprzak <kas@xxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Jan Kasprzak <kas@xxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: [PATCH 2/3] Don't tell sysfs to launch the container as we are doing it ourselves
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: Install grub2 to /dev/md126 fails
- From: jlcenter@xxxxxxxxxxx
Re: What just happened to my disks/RAID5 array?
- From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Jan Kasprzak <kas@xxxxxxxxxx>
Re: What just happened to my disks/RAID5 array?
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: What just happened to my disks/RAID5 array?
- From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
Re: SMART, RAID and real world experience of failures.
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: What just happened to my disks/RAID5 array?
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: SMART, RAID and real world experience of failures.
- From: Steven Haigh <netwiz@xxxxxxxxx>
Re: implications of partitioning and raid
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: SMART, RAID and real world experience of failures.
- From: pg@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: What just happened to my disks/RAID5 array?
- From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
Re: Install grub2 to /dev/md126 fails
- From: jlcenter@xxxxxxxxxxx
Re: SMART, RAID and real world experience of failures.
- From: Roman Mamedov <rm@xxxxxxxxxx>
SMART, RAID and real world experience of failures.
- From: Steven Haigh <netwiz@xxxxxxxxx>
Re: raid 1 bug with write-mostly and administrative failed disk
- From: Art -kwaak- van Breemen <ard@xxxxxxxxxxxxxxx>
raid 1 bug with write-mostly and administrative failed disk
- From: Art -kwaak- van Breemen <ard@xxxxxxxxxxxxxxx>
Re: implications of partitioning and raid
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
implications of partitioning and raid
- From: "Peter W. Morreale" <morreale@xxxxxxx>
RE: [PATCH] imsm: fix: correct calculation of UUID
- From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
[PATCH 1/1] Work around gcc-4.7's strict aliasing checks
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 0/1] gcc-4.7 build fix
- From: Jes.Sorensen@xxxxxxxxxx
polling mdX/md/degraded in sysfs
- From: Mikhail Balabin <mbalabin@xxxxxxxxx>
[PULL REQUEST] md for 3.3
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID1 fail did not work properly with SSDs
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID1 fail did not work properly with SSDs
- From: "Cal Leeming [Simplicity Media Ltd]" <cal.leeming@xxxxxxxxxxxxxxxxxxxxxxxx>
Re: RAID1 fail did not work properly with SSDs
- From: "Cal Leeming [Simplicity Media Ltd]" <cal.leeming@xxxxxxxxxxxxxxxxxxxxxxxx>
Re: RAID1 fail did not work properly with SSDs
- From: NeilBrown <neilb@xxxxxxx>
RAID1 fail did not work properly with SSDs
- From: "Cal Leeming [Simplicity Media Ltd]" <cal.leeming@xxxxxxxxxxxxxxxxxxxxxxxx>
Re: [PATCH] imsm: fix: correct calculation of UUID
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
RE: [PATCH] imsm: fix: correct calculation of UUID
- From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
Spinned down raid drives sometimes not recognized anymore
- From: John Hendrikx <hjohn@xxxxxxxxx>
Re: [PATCH] imsm: fix: correct calculation of UUID
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[PATCH] imsm: fix: correct calculation of UUID
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
Re: [PATCH 2/3] Don't tell sysfs to launch the container as we are doing it ourselves
- From: NeilBrown <neilb@xxxxxxx>
Re: Install grub2 to /dev/md126 fails
- From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
Re: Install grub2 to /dev/md126 fails
- From: jlcenter@xxxxxxxxxxx
Re: [PATCH 2/3] Don't tell sysfs to launch the container as we are doing it ourselves
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: Is this RAID recoverable???
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Is this RAID recoverable???
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Is this RAID recoverable???
- From: Paul Richter <iamcomcy@xxxxxxxxx>
Re: Is this RAID recoverable???
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: Is this RAID recoverable???
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Install grub2 to /dev/md126 fails
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 2/3] Don't tell sysfs to launch the container as we are doing it ourselves
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: Is this RAID recoverable???
- From: Roman Mamedov <rm@xxxxxxxxxx>
Is this RAID recoverable???
- From: Paul Richter <iamcomcy@xxxxxxxxx>
Re: [PATCH] FIX: Cannot remove failed disk from container
- From: NeilBrown <neilb@xxxxxxx>
Re: Install grub2 to /dev/md126 fails
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] FIX: Cannot remove failed disk from container
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH][RFC] RAID5/DMA/memcpy: zero copy the bio page when possible
- From: NeilBrown <neilb@xxxxxxx>
Re: dirty chunks on bitmap not clearing (RAID1)
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID0 partition set to spare
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: RAID0 partition set to spare
- From: Steve Carlson <stevengcarlson@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: RAID0 partition set to spare
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Install grub2 to /dev/md126 fails
- From: jlcenter@xxxxxxxxxxx
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: RAID0 partition set to spare
- From: Steve Carlson <stevengcarlson@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Zdenek Kaspar <zkaspar82@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Michele Codutti <codutti@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Krzysztof Adamski <k@xxxxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Mattias Wadenstein <maswan@xxxxxxxxxx>
Re: RAID0 partition set to spare
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
RAID0 partition set to spare
- From: Steve Carlson <stevengcarlson@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Jeremy Thompson <jeremythompson82@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Zdenek Kaspar <zkaspar82@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Jeremy Thompson <jeremythompson82@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Michele Codutti <codutti@xxxxxxxxx>
[PATCH] FIX: Cannot remove failed disk from container
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Gordon Henderson <gordon@xxxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Jeremy Thompson <jeremythompson82@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Asdo <asdo@xxxxxxxxxxxxx>
Re: Btrfs: blocked for more than 120 seconds, made worse by 3.2 rc7
- From: Konstantinos Skarlatos <k.skarlatos@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Jeremy Thompson <jeremythompson82@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Asdo <asdo@xxxxxxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Gordon Henderson <gordon@xxxxxxxxxx>
It is safe to stop Raid being reshaped
- From: Jeremy Thompson <jeremythompson82@xxxxxxxxx>
[PATCH][RFC] RAID5/DMA/memcpy: zero copy the bio page when possible
- From: <b29237@xxxxxxxxxxxxx>
Re: dirty chunks on bitmap not clearing (RAID1)
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Philip Hands <phil@xxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Philip Hands <phil@xxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Philip Hands <phil@xxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Philip Hands <phil@xxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Philip Hands <phil@xxxxxxxxx>
Subject: ANNOUNCE: mdadm 3.2.3 - A tool for managing Soft RAID under Linux
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/3] Don't tell sysfs to launch the container as we are doing it ourselves
- From: NeilBrown <neilb@xxxxxxx>
[PULL REQUEST] md bug fixes for 3.2
- From: NeilBrown <neilb@xxxxxxx>
Re: dirty chunks on bitmap not clearing (RAID1)
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
- From: NeilBrown <neilb@xxxxxxx>
Re: mdadm --monitor as non-root ?
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
- From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
Re: [PATCH] FIX: Verify if array name doesn't exist already
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] FIX: Verify if array name doesn't exist already
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: Adding a new disk after disk failure on raid6 volume
- From: BERTRAND Joël <joel.bertrand@xxxxxxxxxxx>
Re: Adding a new disk after disk failure on raid6 volume
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: Adding a new disk after disk failure on raid6 volume
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Adding a new disk after disk failure on raid6 volume
- From: BERTRAND Joël <joel.bertrand@xxxxxxxxxxx>
RE: [PATCH 3/3] imsm: FIX: UT '08imsm-overlap' fails
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID50, despite chunk setting, does everything in 4KB blocks
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID50, despite chunk setting, does everything in 4KB blocks
- From: Chris Worley <worleys@xxxxxxxxx>
Re: [PATCH 3/3] imsm: FIX: UT '08imsm-overlap' fails
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: make messages more understandable
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID50, despite chunk setting, does everything in 4KB blocks
- From: NeilBrown <neilb@xxxxxxx>
RAID50, despite chunk setting, does everything in 4KB blocks
- From: Chris Worley <worleys@xxxxxxxxx>
RE: [PATCH] imsm: make messages more understandable
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[33/45] md/raid5: fix bug that could result in reads from a failed device.
- From: Greg KH <gregkh@xxxxxxx>
Re: [PATCH] imsm: make messages more understandable
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
RE: BUG_ON triggered in worker_enter_idle, after power failure caused potential RAID corruption (kernel 2.6.39.4)
- From: Bruce Stenning <b.stenning@xxxxxxxxxxxxxxxx>
Re: Split-Brain Protection for MD arrays
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
[PATCH] imsm: make messages more understandable
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
Re: Split-Brain Protection for MD arrays
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Mount Linux Raid Array on new install
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
RE: [PATCH 3/3] imsm: FIX: UT '08imsm-overlap' fails
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH 3/3] imsm: FIX: UT '08imsm-overlap' fails
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
Re: ''force'' continutation of a rebuild?
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: ''force'' continutation of a rebuild?
- From: NeilBrown <neilb@xxxxxxx>
''force'' continutation of a rebuild?
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: Split-Brain Protection for MD arrays
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/3] imsm: FIX: 'UT 09imsm-assemble' fails
- From: NeilBrown <neilb@xxxxxxx>
RE: [PATCH 2/3] imsm: FIX: 'UT 09imsm-assemble' fails
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: RAID5: failing an active component during spare rebuild - arrays hangs
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: Split-Brain Protection for MD arrays
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: [PATCH 2/3] imsm: FIX: 'UT 09imsm-assemble' fails
- From: NeilBrown <neilb@xxxxxxx>
RE: [PATCH 2/3] imsm: FIX: 'UT 09imsm-assemble' fails
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: Data scribbling for raid6 is wrong?
- From: David Brown <david@xxxxxxxxxxxxxxx>
RE: [PATCH 3/3] imsm: FIX: UT '08imsm-overlap' fails
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
Re: ext4 data=writeback performs worse than data=ordered now
- From: Wu Fengguang <fengguang.wu@xxxxxxxxx>
Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
- From: NeilBrown <neilb@xxxxxxx>
Re: Data scribbling for raid6 is wrong?
- From: Tao Guo <glorioustao@xxxxxxxxx>
Re: Data scribbling for raid6 is wrong?
- From: NeilBrown <neilb@xxxxxxx>
Last call for mdadm-3.2.3.
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 3/3] imsm: FIX: UT '08imsm-overlap' fails
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/3] imsm: FIX: Chunk size migration is not possible
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/3] imsm: FIX: 'UT 09imsm-assemble' fails
- From: NeilBrown <neilb@xxxxxxx>
Data scribbling for raid6 is wrong?
- From: Tao Guo <glorioustao@xxxxxxxxx>
Re: Split-Brain Protection for MD arrays
- From: NeilBrown <neilb@xxxxxxx>
Re: ext4 data=writeback performs worse than data=ordered now
- From: Wu Fengguang <fengguang.wu@xxxxxxxxx>
Re: ext4 data=writeback performs worse than data=ordered now
- From: NeilBrown <neilb@xxxxxxx>
Re: ext4 data=writeback performs worse than data=ordered now
- From: Wu Fengguang <fengguang.wu@xxxxxxxxx>
Patch "md/raid5: fix bug that could result in reads from a failed device." has been added to the 3.0-stable tree
- From: <gregkh@xxxxxxx>
Re: [PATCH] md/raid5: fix bug that could result in reads from a failed device.
- From: Greg KH <greg@xxxxxxxxx>
[PATCH] md/raid5: fix bug that could result in reads from a failed device.
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: RAID-6 disk superblock issue
- From: Troy Telford <ttelford.groups@xxxxxxxxx>
Re: RAID-6 disk superblock issue
- From: Troy Telford <ttelford.groups@xxxxxxxxx>
Re: RAID-6 disk superblock issue
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID-6 disk superblock issue
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: RAID-6 disk superblock issue
- From: Troy Telford <ttelford.groups@xxxxxxxxx>
Re: RAID-6 disk superblock issue
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: [PATCH 3/3] imsm: FIX: UT '08imsm-overlap' fails
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
Re: [PATCH 1/3] Create: Allow to create two volumes of different sizes within one container
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [PATCH 2/3] imsm: FIX: 'UT 09imsm-assemble' fails
- From: "Peter W. Morreale" <morreale@xxxxxxx>
[PATCH 2/3] imsm: FIX: 'UT 09imsm-assemble' fails
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 3/3] imsm: FIX: UT '08imsm-overlap' fails
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 1/3] imsm: FIX: Chunk size migration is not possible
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 0/3] Enable mdadm UT execution for imsm
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
RE: Raid0 expansion problem in md
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: RAID5: failing an active component during spare rebuild - arrays hangs
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID5: failing an active component during spare rebuild - arrays hangs
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
[PATCH] FIX: Do not allow for multiple reshape_array() execution during reshape_container() call
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH] FIX: Do not allow for multiple reshape_array() execution during reshape_container() call
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH] FIX: Do not allow for multiple reshape_array() execution during reshape_container() call
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
RE: [PATCH 1/3] FIX: Do not allow for multiple reshape_array() execution during reshape_container() call
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH 1/3] FIX: Do not allow for multiple reshape_array() execution during reshape_container() call
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid0 expansion problem in md
- From: NeilBrown <neilb@xxxxxxx>
RAID-6 disk superblock issue
- From: Troy Telford <ttelford.groups@xxxxxxxxx>
Mount Linux Raid Array on new install
- From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
Raid0 expansion problem in md
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
[PATCH 3/3] imsm: FIX: return correct status from load_imsm_migr_rec()
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 2/3] FIX: Add error message in container_reshape()
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 1/3] FIX: Do not allow for multiple reshape_array() execution during reshape_container() call
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: Split-Brain Protection for MD arrays
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
RE: [PATCH 2/2] imsm: FIX: Use first map only in migration record disk operations
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH 2/2] imsm: FIX: Use first map only in migration record disk operations
- From: NeilBrown <neilb@xxxxxxx>
Re: meta: should i chase this down?
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: Split-Brain Protection for MD arrays
- From: Vincent Pelletier <plr.vincent@xxxxxxxxx>
Split-Brain Protection for MD arrays
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
RAID-10 explicitly defined drive pairs?
- From: Jan Kasprzak <kas@xxxxxxxxxx>
Re: failed reshape!
- From: Gavin Peters (蓋文彼德斯) <gavin@xxxxxx>
[PATCH 2/2] imsm: FIX: Use first map only in migration record disk operations
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 1/2] imsm: FIX: Limit migration record operation by disk slot not by index
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
RE: [PATCH] imsm: FIX: Use first map only in migration record disk operations
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
RE: [PATCH] imsm: FIX: Use first map only in migration record disk operations
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
RE: [PATCH] imsm: FIX: Limit migration record operation by disk slot not by index
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: raid6 rebuild not starting
- From: Anssi Hannula <anssi.hannula@xxxxxx>
Re: raid6 rebuild not starting
- From: NeilBrown <neilb@xxxxxxx>
Re: raid6 rebuild not starting
- From: Anssi Hannula <anssi.hannula@xxxxxx>
Re: raid6 rebuild not starting
- From: NeilBrown <neilb@xxxxxxx>
Re: raid6 rebuild not starting
- From: Anssi Hannula <anssi.hannula@xxxxxx>
Re: raid6 rebuild not starting
- From: NeilBrown <neilb@xxxxxxx>
Re: raid6 rebuild not starting
- From: Anssi Hannula <anssi.hannula@xxxxxx>
Re: [PATCH] imsm: FIX: Use first map only in migration record disk operations
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: FIX: Limit migration record operation by disk slot not by index
- From: NeilBrown <neilb@xxxxxxx>
Re: failed reshape!
- From: NeilBrown <neilb@xxxxxxx>
Re: raid6 rebuild not starting
- From: NeilBrown <neilb@xxxxxxx>
raid6 rebuild not starting
- From: Anssi Hannula <anssi.hannula@xxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: wilsonjonathan <piercing_male@xxxxxxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: wilsonjonathan <piercing_male@xxxxxxxxxxx>
Raid10 write storm
- From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: Eli Morris <ermorris@xxxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: Eli Morris <ermorris@xxxxxxxx>
Reasons why mdmon is not starting?
- From: Joachim Achtzehnter <joachima@xxxxxxxxxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: Asdo <asdo@xxxxxxxxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: "John Stoffel" <john@xxxxxxxxxxx>
failed reshape!
- From: Gavin Peters (蓋文彼德斯) <gavin@xxxxxx>
[PATCH] imsm: FIX: Use first map only in migration record disk operations
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: Eli Morris <ermorris@xxxxxxxx>
Re: [PATCH] md: Add ability for disable bad block management
- From: NeilBrown <neilb@xxxxxxx>
[PULL REQUEST] md updates for 3.2-rc
- From: NeilBrown <neilb@xxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: NeilBrown <neilb@xxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: Eli Morris <ermorris@xxxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: NeilBrown <neilb@xxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: Eli Morris <ermorris@xxxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: NeilBrown <neilb@xxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: Eli Morris <ermorris@xxxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: NeilBrown <neilb@xxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: Eli Morris <ermorris@xxxxxxxx>
Re: system startup hangs
- From: "Richard B. Pyne" <rpyne@xxxxxxxxxxx>
RE: [PATCH] md: Add ability for disable bad block management
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
[PATCH] imsm: FIX: Correct make everything and variable initialization
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: system startup hangs
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
[PATCH] imsm: FIX: Use definitions for migration record disk operations
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH] imsm: FIX: Limit migration record operation by disk slot not by index
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: Raid10 and page cache
- From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
Re: [PATCH] md: Add ability for disable bad block management
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 0/9] Array degradation during reshape and rebuild (cont.)
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid10 and page cache
- From: NeilBrown <neilb@xxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: Eli Morris <ermorris@xxxxxxxx>
Re: Raid10 and page cache
- From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
Re: system startup hangs
- From: "Richard B. Pyne" <rpyne@xxxxxxxxxxx>
Re: system startup hangs
- From: "Richard B. Pyne" <rpyne@xxxxxxxxxxx>
Re: system startup hangs
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: system startup hangs
- From: NeilBrown <neilb@xxxxxxx>
system startup hangs
- From: "Richard B. Pyne" <rpyne@xxxxxxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: NeilBrown <neilb@xxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: Eli Morris <ermorris@xxxxxxxx>
Fwd: 4 out of 16 drives show up as 'removed'
- From: Eli Morris <ermorris@xxxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: NeilBrown <neilb@xxxxxxx>
Re: 4 out of 16 drives show up as 'removed'
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
4 out of 16 drives show up as 'removed'
- From: Eli Morris <ermorris@xxxxxxxx>
[PATCH 9/9] imsm: FIX: Use defines for device map access
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 8/9] imsm: FIX: Check correct slots on disk failure
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 7/9] imsm: FIX: Finish rebuild and initialization when missing drive is handled
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 6/9] imsm: FIX: Mark failure for rebuild
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 5/9] imsm: FIX: Add array map state transition for failures during initialization
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 4/9] imsm: FIX: Do not allow spare activation during rebuild
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 3/9] imsm: Function imsm_set_disk() rework
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 2/9] imsm: FIX: Correct ords merging in end_migration()
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 1/9] imsm: FIX: Remove longer map request
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 0/9] Array degradation during reshape and rebuild (cont.)
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
RE: [PATCH] md: Add ability for disable bad block management
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: Raid10 and page cache
- From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
Re: Raid10 and page cache
- From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
Re: Raid10 and page cache
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid10 and page cache
- From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
Re: meta: should i chase this down?
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: Raid10 and page cache
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid10 and page cache
- From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
Re: [PATCH] md: Add ability for disable bad block management
- From: NeilBrown <neilb@xxxxxxx>
Re: need a little help rebuilding a raid 10
- From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
Re: [PATCH] imsm: fix: does not allow to use invalid chunk size
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid10 and page cache
- From: NeilBrown <neilb@xxxxxxx>
Re: meta: should i chase this down?
- From: NeilBrown <neilb@xxxxxxx>
meta: should i chase this down?
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: Raid10 and page cache
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: Raid10 and page cache
- From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
Re: Raid10 and page cache
- From: NeilBrown <neilb@xxxxxxx>
Raid10 and page cache
- From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
Re: RAID5: failing an active component during spare rebuild - arrays hangs
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID5: failing an active component during spare rebuild - arrays hangs
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
RE: [PATCH] imsm: fix: does not allow to use invalid chunk size
- From: "Hawrylewicz Czarnowski, Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
Re: need a little help rebuilding a raid 10
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: need a little help rebuilding a raid 10
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: need a little help rebuilding a raid 10
- From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
RE: [PATCH] md: Add ability for disable bad block management
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
RE: [PATCH] imsm: do not fail load_container when first 2 disks are missing
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
Re: Spin down
- From: Vincent Pelletier <plr.vincent@xxxxxxxxx>
RE: [PATCH 00/11] Degradation during reshape
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH] md: Add ability for disable bad block management
- From: NeilBrown <neilb@xxxxxxx>
Re: Possible changes to bio cloning and some related stuff
- From: NeilBrown <neilb@xxxxxxx>
Possible changes to bio cloning and some related stuff
- From: Kent Overstreet <koverstreet@xxxxxxxxxx>
Re: mdadm, bitmap and split-brain
- From: NeilBrown <neilb@xxxxxxx>
Re: Spin down
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID5: failing an active component during spare rebuild - arrays hangs
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: fix: correct checking newly missing disks
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: fix: correct checking newly missing disks
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
need a little help rebuilding a raid 10
- From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
Re: [PATCH] imsm: fix: correct checking newly missing disks
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] FIX: resolve make everything compilation error
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: FIX: Just created redundant array is not in uninitialized state
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: fix: does not allow to use invalid chunk size
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 00/11] Degradation during reshape
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: do not fail load_container when first 2 disks are missing
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] FIX: resolve make everything compilation error
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: RAID1 round robin read support in md?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
[PATCH] imsm: FIX: Just created redundant array is not in uninitialized state
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
RE: Is this stupid?
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
Re: Spin down
- From: Vincent Pelletier <plr.vincent@xxxxxxxxx>
RE: Is this stupid?
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
Re: Is this stupid?
- From: Doug Dumitru <doug@xxxxxxxxxx>
Re: RAID6 - repeated hot-pulls issue
- From: NeilBrown <neilb@xxxxxxx>
Re: Spin down
- From: NeilBrown <neilb@xxxxxxx>
Re: Is this stupid?
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID1 round robin read support in md?
- From: Doug Dumitru <doug@xxxxxxxxxx>
Re: RAID1 round robin read support in md?
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID1 round robin read support in md?
- From: Borg Onion <borg.onion@xxxxxxxxx>
Re: md metadata nightmare
- From: Kenneth Emerson <kenneth.emerson@xxxxxxxxx>
Re: RAID1 round robin read support in md?
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
RAID1 round robin read support in md?
- From: Borg Onion <borg.onion@xxxxxxxxx>
Is this stupid?
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
Re: md metadata nightmare
- From: NeilBrown <neilb@xxxxxxx>
Re: md metadata nightmare
- From: wilsonjonathan <piercing_male@xxxxxxxxxxx>
Re: md metadata nightmare
- From: Kenneth Emerson <kenneth.emerson@xxxxxxxxx>
md metadata nightmare
- From: Kenneth Emerson <kenneth.emerson@xxxxxxxxx>
Spin down
- From: Vincent Pelletier <plr.vincent@xxxxxxxxx>
RAID6 - repeated hot-pulls issue
- From: John Gehring <john.gehring@xxxxxxxxx>
RE: [PATCH] imsm: fix: correct checking newly missing disks
- From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
RE: [PATCH] imsm: fix: correct checking newly missing disks
- From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
RE: [PATCH 01/11] imsm: FIX: Return longer map for failure setting
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: quick question about write-intent bitmap
- From: NeilBrown <neilb@xxxxxxx>
quick question about write-intent bitmap
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: [PATCH 01/11] imsm: FIX: Return longer map for failure setting
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
Re: mdadm 3.2.2: Behavioral change when adding back a previously faulted device
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
mdadm 3.2.2: Behavioral change when adding back a previously faulted device
- From: Martin Steigerwald <ms@xxxxxxxxx>
RE: [PATCH] md: Add ability for disable bad block management
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
RE: [PATCH 01/11] imsm: FIX: Return longer map for failure setting
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH] imsm: fix: correct checking newly missing disks
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [PATCH 01/11] imsm: FIX: Return longer map for failure setting
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [PATCH] md: Add ability for disable bad block management
- From: NeilBrown <neilb@xxxxxxx>
Re: linear raid, is partial recovery possible?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: linear raid, is partial recovery possible?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: linear raid, is partial recovery possible?
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: linear raid, is partial recovery possible?
- From: NeilBrown <neilb@xxxxxxx>
linear raid, is partial recovery possible?
- From: wilsonjonathan <piercing_male@xxxxxxxxxxx>
Re: Ubuntu mdadm Raid and EFI
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: Ubuntu mdadm Raid and EFI
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
[UPDATED PATCH 57/62] dm: remove the second argument of k[un]map_atomic()
- From: Cong Wang <amwang@xxxxxxxxxx>
[UPDATED PATCH 17/62] md: remove the second argument of k[un]map_atomic()
- From: Cong Wang <amwang@xxxxxxxxxx>
Re: [dm-devel] [PATCH 17/62] md: remove the second argument of k[un]map_atomic()
- From: Cong Wang <amwang@xxxxxxxxxx>
Re: [dm-devel] [PATCH 17/62] md: remove the second argument of k[un]map_atomic()
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: RAID5: failing an active component during spare rebuild - arrays hangs
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: [PATCH 17/62] md: remove the second argument of k[un]map_atomic()
- From: NeilBrown <neilb@xxxxxxx>
[PATCH 57/62] md: remove the second argument of k[un]map_atomic()
- From: Cong Wang <amwang@xxxxxxxxxx>
[PATCH 17/62] md: remove the second argument of k[un]map_atomic()
- From: Cong Wang <amwang@xxxxxxxxxx>
mdadm, bitmap and split-brain
- From: Ronal Andadinata <randadinata@xxxxxxxxx>
Online RAID1 -> RAID10 migration?
- From: Bart Kus <me@xxxxxxxx>
[PATCH] imsm: fix: does not allow to use invalid chunk size
- From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
Re: Ubuntu mdadm Raid and EFI
- From: Dominique <dcouot@xxxxxxxxxxx>
Re: Is it possible to change the wait time before a drive is concidered failed?
- From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
Ubuntu mdadm Raid and EFI
- From: Dominique <dcouot@xxxxxxxxxxx>
Re: partition based raid1 and multi boot Ubuntu/Xubuntu
- From: Gavin Whitehead <gavin@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
RE: [PATCH] md: Add ability for disable bad block management
- From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
RE: [PATCH] md: Add ability for disable bad block management
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH] md: Add ability for disable bad block management
- From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
[PATCH] md: Add ability for disable bad block management
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 11/11] Disable BBM when it is not supported
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 10/11] imsm: FIX: Check maximum allowed degradation level in recover_backup_imsm()
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 09/11] imsm: FIX: Check maximum allowed degradation level in open_backup_targets()
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 08/11] imsm: FIX: Function rework - imsm_count_failed()
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 07/11] imsm: FIX: Manage second map state on array degradation
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 06/11] imsm: FIX: Restore critical section on degraded array
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 05/11] imsm: FIX: Remove single map state limitation in getinfo
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 04/11] imsm: FIX: Finalize degraded migration
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 03/11] imsm: FIX: Do not end migration when missing drive is handled
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 02/11] imsm: FIX: Mark both maps on degradation while migrating
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 01/11] imsm: FIX: Return longer map for failure setting
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 00/11] Degradation during reshape
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: partition based raid1 and multi boot Ubuntu/Xubuntu
- From: Gordon Henderson <gordon@xxxxxxxxxx>
[PATCH] imsm: do not fail load_container when first 2 disks are missing
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
Re: [PATCH] imsm: fix, check all volumes state in Grow_continue function
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: incorrect incremental behavior because of wrong index used
- From: NeilBrown <neilb@xxxxxxx>
md metadata nightmare
- From: Kenneth Emerson <kenneth.emerson@xxxxxxxxx>
Re: md metadata nightmare
- From: NeilBrown <neilb@xxxxxxx>
Re: partition based raid1 and multi boot Ubuntu/Xubuntu
- From: Gavin Whitehead <gavin@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: md device io request split
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: incorrect incremental behavior because of wrong index used
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
[PATCH] imsm: incorrect incremental behavior because of wrong index used
- From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
Re: md metadata nightmare
- From: CoolCold <coolthecold@xxxxxxxxx>
[PATCH] imsm: fix, check all volumes state in Grow_continue function
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
Re: md device io request split
- From: "Ramon Schönborn" <RSchoenborn@xxxxxxx>
Re: [OT] Re: Disk identity crisis on RAID10 recovery (3.1.0)
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: [OT] Re: Disk identity crisis on RAID10 recovery (3.1.0)
- From: NeilBrown <neilb@xxxxxxx>
[OT] Re: Disk identity crisis on RAID10 recovery (3.1.0)
- From: Konrad Rzepecki <krzepecki@xxxxxxxxxxx>
Re: md metadata nightmare
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: md device io request split
- From: NeilBrown <neilb@xxxxxxx>
Re: md metadata nightmare
- From: NeilBrown <neilb@xxxxxxx>
md metadata nightmare
- From: Kenneth Emerson <kenneth.emerson@xxxxxxxxx>
Re: partition based raid1 and multi boot Ubuntu/Xubuntu
- From: NeilBrown <neilb@xxxxxxx>
partition based raid1 and multi boot Ubuntu/Xubuntu
- From: Gavin Whitehead <gavin@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: Disk identity crisis on RAID10 recovery (3.1.0)
- From: NeilBrown <neilb@xxxxxxx>
Re: Is it possible to change the wait time before a drive is concidered failed?
- From: wilsonjonathan <piercing_male@xxxxxxxxxxx>
Re: Disk identity crisis on RAID10 recovery (3.1.0)
- From: Konrad Rzepecki <krzepecki@xxxxxxxxxxx>
Re: Disk identity crisis on RAID10 recovery (3.1.0)
- From: Konrad Rzepecki <krzepecki@xxxxxxxxxxx>
Re: raid1d crash at boot
- From: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
Re: raid1d crash at boot
- From: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
Re: Disk identity crisis on RAID10 recovery (3.1.0)
- From: NeilBrown <neilb@xxxxxxx>
Disk identity crisis on RAID10 recovery (3.1.0)
- From: Konrad Rzepecki <krzepecki@xxxxxxxxxxx>
Re: raid1d crash at boot
- From: NeilBrown <neilb@xxxxxxx>
md device io request split
- From: "Ramon Schönborn" <RSchoenborn@xxxxxxx>
Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: Question about raid 10 and raid 1+0 setup
- From: Holger Kiehl <Holger.Kiehl@xxxxxx>
Re: raid1d crash at boot
- From: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
Re: possible bug - bitmap dirty pages status
- From: linbloke <linbloke@xxxxxxxxxxx>
Question about raid 10 and raid 1+0 setup
- From: Holger Kiehl <Holger.Kiehl@xxxxxx>
RE: BUG_ON triggered in worker_enter_idle, after power failure caused potential RAID corruption (kernel 2.6.39.4)
- From: Bruce Stenning <b.stenning@xxxxxxxxxxxxxxxx>
Re: raid1d crash at boot
- From: NeilBrown <neilb@xxxxxxx>
Re: raid1d crash at boot
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Re: [PATCH] fix: correct metadata's update communication
- From: NeilBrown <neilb@xxxxxxx>
Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
- From: NeilBrown <neilb@xxxxxxx>
Re: Is it possible to change the wait time before a drive is concidered failed?
- From: NeilBrown <neilb@xxxxxxx>
Re: raid1d crash at boot
- From: NeilBrown <neilb@xxxxxxx>
Is it possible to change the wait time before a drive is concidered failed?
- From: wilsonjonathan <piercing_male@xxxxxxxxxxx>
[PATCH] fix: correct metadata's update communication
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
[PATCH] imsm: fix: correct printing value of blocks per migration unit
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
Re: MD RAID1 weirdness *SOLVED*
- From: Danilo Godec <danilo.godec@xxxxxxxxx>
MD RAID1 weirdness
- From: Danilo Godec <danilo.godec@xxxxxxxxx>
Re: Reshape 3-drive RAID1 into 3-drive RAID-5
- From: NeilBrown <neilb@xxxxxxx>
Re: Reshape 3-drive RAID1 into 3-drive RAID-5
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: Idea: Dynamic growth of the md array
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Idea: Dynamic growth of the md array
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Idea: Dynamic growth of the md array
- From: Terrance Hutchinson <Terrance.Hutchinson@xxxxxxxxxxx>
BUG_ON triggered in worker_enter_idle, after power failure caused potential RAID corruption (kernel 2.6.39.4)
- From: Bruce Stenning <b.stenning@xxxxxxxxxxxxxxxx>
[PATCH] mdadm trivial: Print more detailed error messages on re-add failure
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: [PATCH] imsm: platform capabilities are not validated during level migration
- From: NeilBrown <neilb@xxxxxxx>
Re: possible bug - bitmap dirty pages status
- From: CoolCold <coolthecold@xxxxxxxxx>
Re: raid startup on a live CD?
- From: Hank Barta <hbarta@xxxxxxxxx>
Re: possible bug - bitmap dirty pages status
- From: NeilBrown <neilb@xxxxxxx>
Re: possible bug - bitmap dirty pages status
- From: NeilBrown <neilb@xxxxxxx>
Re: Reshape 3-drive RAID1 into 3-drive RAID-5
- From: NeilBrown <neilb@xxxxxxx>
Re: raid startup on a live CD?
- From: NeilBrown <neilb@xxxxxxx>
Re: Reshape 3-drive RAID1 into 3-drive RAID-5
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: raid startup on a live CD?
- From: Hank Barta <hbarta@xxxxxxxxx>
Rebuilding Raid 1 set up
- From: William Colls <william.colls@xxxxxxxxxx>
Reshape 3-drive RAID1 into 3-drive RAID-5
- From: Mark Knecht <markknecht@xxxxxxxxx>
[PATCH] imsm: platform capabilities are not validated during level migration
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
Re: md/raid10: handle recovery of replacement devices.
- From: NeilBrown <neilb@xxxxxxx>
re: md/raid10: handle recovery of replacement devices.
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Re: raid startup on a live CD?
- From: NeilBrown <neilb@xxxxxxx>
raid startup on a live CD?
- From: Hank Barta <hbarta@xxxxxxxxx>
Re: [PATCH] imsm: fix: correct checking newly missing disks
- From: NeilBrown <neilb@xxxxxxx>
Re: possible bug - bitmap dirty pages status
- From: linbloke <linbloke@xxxxxxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: William Colls <william.colls@xxxxxxxxxx>
[PATCH] imsm: fix: correct checking newly missing disks
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
Re: raid 5 to raid 6 reshape gone bad
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: fix: Allowed to create 2 volumes with total size less then maximum.
- From: NeilBrown <neilb@xxxxxxx>
Re: raid 5 to raid 6 reshape gone bad
- From: Travis Brown <teb@xxxxxxxxxx>
Re: raid 5 to raid 6 reshape gone bad
- From: Travis Brown <teb@xxxxxxxxxx>
Re: raid 5 to raid 6 reshape gone bad
- From: Travis Brown <teb@xxxxxxxxxx>
Re: raid 5 to raid 6 reshape gone bad
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: raid 5 to raid 6 reshape gone bad
- From: NeilBrown <neilb@xxxxxxx>
Re: raid 5 to raid 6 reshape gone bad
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: raid 5 to raid 6 reshape gone bad
- From: NeilBrown <neilb@xxxxxxx>
raid 5 to raid 6 reshape gone bad
- From: Travis Brown <teb@xxxxxxxxxx>
Re: unable to recover RAID 5 due to bad block [solved]
- From: Chris Purves <chris@xxxxxxxxxxxx>
Re: unable to recover RAID 5 due to bad block
- From: NeilBrown <neilb@xxxxxxx>
Re: unable to recover RAID 5 due to bad block
- From: NeilBrown <neilb@xxxxxxx>
Re: unable to recover RAID 5 due to bad block
- From: Chris Purves <chris@xxxxxxxxxxxx>
Re: unable to recover RAID 5 due to bad block
- From: Chris Purves <chris@xxxxxxxxxxxx>
Re: unable to recover RAID 5 due to bad block
- From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
Re: unable to recover RAID 5 due to bad block
- From: Chris Purves <chris@xxxxxxxxxxxx>
Re: unable to recover RAID 5 due to bad block
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: unable to recover RAID 5 due to bad block
- From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: John Robinson <john.robinson@xxxxxxxxxxx>
Re: unable to recover RAID 5 due to bad block
- From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
unable to recover RAID 5 due to bad block
- From: Chris Purves <chris@xxxxxxxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: William Colls <william.colls@xxxxxxxxxx>
RE: [PATCH] imsm: fix: Allowed to create 2 volumes with total size less then maximum.
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
Re: [PATCH] imsm: control number of active imsm volumes in the system
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH] imsm: fix: Allowed to create 2 volumes with total size less then maximum.
- From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
Re: Intel RAID problems
- From: NeilBrown <neilb@xxxxxxx>
RE: [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: William Colls <william.colls@xxxxxxxxxx>
Intel RAID problems
- From: Blair Strater <me@xxxxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: mini change of raid5.c
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: control number of active imsm volumes in the system
- From: NeilBrown <neilb@xxxxxxx>
Re: mdraid write performance in different kernels up to 3.0, 3.0 shows huge improvement
- From: NeilBrown <neilb@xxxxxxx>
Re: All kinds of things on RAID/mdadm
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: William Colls <william.colls@xxxxxxxxxx>
Re: All kinds of things on RAID/mdadm
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: William Colls <william.colls@xxxxxxxxxx>
Re: Raid Problem - Unknown File System Type
- From: Gordon Henderson <gordon@xxxxxxxxxx>
Raid Problem - Unknown File System Type
- From: William Colls <william.colls@xxxxxxxxxx>
[PATCH] imsm: control number of active imsm volumes in the system
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
mini change of raid5.c
- From: "Hardy Flor" <Flor@xxxxxxxxxxxx>
PULL REQUEST - md bugfixes for 3.2-rc
- From: NeilBrown <neilb@xxxxxxx>
Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
- From: NeilBrown <neilb@xxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Michal Soltys <soltys@xxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Michal Soltys <soltys@xxxxxxxx>
Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
Re: Auto-assembling RAID6 over RAID0?
- From: Michał Sawicz <michal@xxxxxxxxxx>
mdraid write performance in different kernels up to 3.0, 3.0 shows huge improvement
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Michal Soltys <soltys@xxxxxxxx>
Re: Impending failure?
- From: Peter Zieba <pzieba@xxxxxxxxxxxxxxxxx>
Re: Impending failure?
- From: Alex <mysqlstudent@xxxxxxxxx>
Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
- From: Witold Baryluk <baryluk@xxxxxxxxxxxxxxxx>
Re: Working TRIM for md RAID
- From: Alex Besogonov <alex.besogonov@xxxxxxxxx>
Re: Working TRIM for md RAID
- From: David Rees <drees76@xxxxxxxxx>
Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
Re: Special drives for Linux Raid?
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Special drives for Linux Raid?
- From: Beolach <beolach@xxxxxxxxx>
Re: documentation for echo check > /dev/mdX, etc.
- From: Beolach <beolach@xxxxxxxxx>
Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
- From: Witold Baryluk <baryluk@xxxxxxxxxxxxxxxx>
Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
- From: Witold Baryluk <baryluk@xxxxxxxxxxxxxxxx>
Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: Special drives for Linux Raid?
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: Special drives for Linux Raid?
- From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Special drives for Linux Raid?
- From: Danilo Godec <danilo.godec@xxxxxxxxx>
Re: All kinds of things on RAID/mdadm
- From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
All kinds of things on RAID/mdadm
- From: Martijn <mailinglist@xxxxxxxxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
RE: [PATCH] fix: Allowed to assemble 2 volumes with the same names from config file.
- From: "Orlowski, Lukasz" <lukasz.orlowski@xxxxxxxxx>
Error when compiling drivers/md/dm-bufio.c
- From: Witold Baryluk <baryluk@xxxxxxxxxxxxxxxx>
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: Kay Sievers <kay.sievers@xxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] md/raid5: STRIPE_ACTIVE has lock semantics, add barriers
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: fix: add support for OLCE and migration to imsm_count_failed
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] fix: Allowed to assemble 2 volumes with the same names from config file.
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/2] FIX: Do not continue container reshape when mdmon is absent
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/2] FIX: mdmon doesn't start
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] dm-ioctl: Don't leak memory in target_message() if 'argc' is NULL
- From: Jesper Juhl <jj@xxxxxxxxxxxxx>
Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
- From: NeilBrown <neilb@xxxxxxx>
Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
- From: NeilBrown <neilb@xxxxxxx>
Re: potentially lost largeish raid5 array..
- From: NeilBrown <neilb@xxxxxxx>
Re: potentially lost largeish raid5 array..
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
- From: Manish Katiyar <mkatiyar@xxxxxxxxx>
Re: Impending failure?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
documentation for echo check > /dev/mdX, etc.
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: Impending failure?
- From: Peter Zieba <pzieba@xxxxxxxxxxxxxxxxx>
Re: Impending failure?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: Impending failure?
- From: Alex <mysqlstudent@xxxxxxxxx>
Re: Impending failure?
- From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
Re: Impending failure?
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Impending failure?
- From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
Re: Impending failure?
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
[PATCH] imsm: fix: add support for OLCE and migration to imsm_count_failed
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
Re: Impending failure?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Impending failure?
- From: Alex <mysqlstudent@xxxxxxxxx>
[PATCH] fix: Allowed to assemble 2 volumes with the same names from config file.
- From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
RE: [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH 2/2] FIX: Do not continue container reshape when mdmon is absent
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 1/2] FIX: mdmon doesn't start
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: [PATCH 00/12] More leak and NULL pointer dereference fixes
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: "Williams, Dan J" <dan.j.williams@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: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
Re: [PATCH 00/19] More fixes for resource leaks and warnings
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: [PATCH 00/12] More leak and NULL pointer dereference fixes
- From: NeilBrown <neilb@xxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Kay Sievers <kay.sievers@xxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Kay Sievers <kay.sievers@xxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: "Williams, Dan J" <dan.j.williams@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: Kay Sievers <kay.sievers@xxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
[PATCH 12/12] match_metadata_desc(): Fix memory leak
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 11/12] fd2devname(): Don't dereference NULL pointer
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 10/12] Manage_ro(): Check pointer rather than dereferencing it
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 07/12] close_aa(): Verify file descriptors are valid before trying to close them
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 09/12] unblock_monitor(): Check sra is valid before dereferencing
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 08/12] ahci_enumerate_ports(): Don't close fd that failed to open
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 06/12] disk_init_and_add(): Fail if opening sysfs file descriptors fail
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 05/12] array_try_spare(): open_dev() returns -1 on error, not zero
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 04/12] get_component_size(): Check read() return value for error before using it
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 03/12] mdstat_read(): Check return value of dup() before using file descriptor
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 02/12] ping_monitor(): check file descriptor is valid before using and closing it
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 01/12] mdadm: add missing break for UpdateSubarray
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 00/12] More leak and NULL pointer dereference fixes
- From: Jes.Sorensen@xxxxxxxxxx
Re: [PATCH 00/19] More fixes for resource leaks and warnings
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Kay Sievers <kay.sievers@xxxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
Re: possibly silly question (raid failover)
- From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
Re: possibly silly question (raid failover)
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: possibly silly question (raid failover)
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: possibly silly question (raid failover)
- From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
Re: possibly silly question (raid failover)
- From: keld@xxxxxxxxxx
Re: possibly silly question (raid failover)
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
[md PATCH 17/17] md/raid1: Mark device replaceable when we see a write error.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 16/17] md/raid1: If there is a spare and a replaceable device, start replacement.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 15/17] md/raid1: recognise replacements when assembling arrays.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 14/17] md/raid1: handle activation of replacement device when recovery completes.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 13/17] md/raid1: Allow a failed replacement device to be removed.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 12/17] md/raid1: Allocate spare to store replacement devices and their bios.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 11/17] md/raid1: Replace use of mddev->raid_disks with conf->raid_disks.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 10/17] md/raid10: If there is a spare and a replaceable device, start replacement.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 09/17] md/raid10: recognise replacements when assembling array.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 08/17] md/raid10: Allow replacement device to be replace old drive.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 07/17] md/raid10: handle recovery of replacement devices.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 06/17] md/raid10: Handle replacement devices during resync.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 05/17] md/raid10: writes should get directed to replacement as well as original.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 04/17] md/raid10: allow removal of failed replacement devices.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 03/17] md/raid10: preferentially read from replacement device if possible.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 02/17] md/raid10: change read_balance to return an rdev
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 01/17] md/raid10: prepare data structures for handling replacement.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 00/17] hot-replace support for RAID1 and RAID10
- From: NeilBrown <neilb@xxxxxxx>
Re: [systemd-devel] systemd kills mdmon if it was started manually by user
- From: NeilBrown <neilb@xxxxxxx>
Re: possibly silly question (raid failover)
- From: NeilBrown <neilb@xxxxxxx>
Re: possibly silly question (raid failover)
- From: keld@xxxxxxxxxx
Re: possibly silly question (raid failover)
- From: keld@xxxxxxxxxx
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: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 00/19] More fixes for resource leaks and warnings
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 1/1] add display of hours remaining to finish resync
- From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
Re: [md PATCH 1/1] add display of hours remaining to finish resync
- From: NeilBrown <neilb@xxxxxxx>

[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]