Linux RAID Storage Date Index
[Prev Page][Next Page]
- [RFC PATCH 0/3] Base compatibility support for Intel(R) Smart Response Technology
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
- [RFC PATCH 3/3] md/isrt: write support
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
- [RFC PATCH 2/3] md/isrt: read support
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
- [RFC PATCH 1/3] md/isrt: base infrastructure and metadata loading
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
- Corrupted ext4 filesystem after mdadm manipulation error
- From: "L.M.J" <linuxmasterjedi@xxxxxxx>
- Re: IMSM - problem with reshape+systemd
- From: NeilBrown <neilb@xxxxxxx>
- Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
- Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: Pasi Kärkkäinen <pasik@xxxxxx>
- RE: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
- Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: Pasi Kärkkäinen <pasik@xxxxxx>
- RE: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
- Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: Pasi Kärkkäinen <pasik@xxxxxx>
- RE: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
- Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: Pasi Kärkkäinen <pasik@xxxxxx>
- Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: NeilBrown <neilb@xxxxxxx>
- raid 10 only spares showing
- From: Roland RoLaNd <r_o_l_a_n_d@xxxxxxxxxxx>
- Re: Cry for help before I screw up a raid recovery more...
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
- Re: Cry for help before I screw up a raid recovery more...
- From: Andrew Ryder <tireman@xxxxxxx>
- Re: Cry for help before I screw up a raid recovery more...
- From: Jeff Wiegley <jeffw@xxxxxxxx>
- Re: Cry for help before I screw up a raid recovery more...
- From: Andrew Ryder <tireman@xxxxxxx>
- Cry for help before I screw up a raid recovery more...
- From: Jeff Wiegley <jeffw@xxxxxxxx>
- Re: md disk fault communication code
- From: NeilBrown <neilb@xxxxxxx>
- Re: md disk fault communication code
- From: Sonu a <p10sonu@xxxxxxxxx>
- Re: md disk fault communication code
- From: NeilBrown <neilb@xxxxxxx>
- md disk fault communication code
- From: Sonu a <p10sonu@xxxxxxxxx>
- Re: dmcrypt on top of raid5, or raid5 on top of dmcrypt?
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- [GIT PULL REQUEST] one md BUG-fix for 3.15-rc
- From: NeilBrown <neilb@xxxxxxx>
- Re: dmcrypt on top of raid5, or raid5 on top of dmcrypt?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- [PATCH] Create: don't default to bitmap=internal when it is not supported
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
- Re: Force mdadm to not prompt the user
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: Nvidia Raid5 Failure
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: [patch]raid5: delete another BUG_ON
- From: Shaohua Li <shli@xxxxxxxxxx>
- Re: Force mdadm to not prompt the user
- From: NeilBrown <neilb@xxxxxxx>
- Re: [patch]raid5: delete another BUG_ON
- From: NeilBrown <neilb@xxxxxxx>
- Force mdadm to not prompt the user
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: Nvidia Raid5 Failure
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Nvidia Raid5 Failure
- From: NeilBrown <neilb@xxxxxxx>
- [patch]raid5: delete another BUG_ON
- From: Shaohua Li <shli@xxxxxxxxxx>
- Re: Nvidia Raid5 Failure
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Nvidia Raid5 Failure
- From: Drew <drew.kay@xxxxxxxxx>
- Re: Nvidia Raid5 Failure
- From: peter davidson <merrymeetpete@xxxxxxxxxxx>
- Re: Some info given by 'mdadm --detail --export' are not convenient to use
- From: bobzer <bobzer@xxxxxxxxx>
- Re: cannot re-assmble mdadm array
- From: NeilBrown <neilb@xxxxxxx>
- Re: Guess the size of a RAID{5,6} device
- From: NeilBrown <neilb@xxxxxxx>
- Re: Some info given by 'mdadm --detail --export' are not convenient to use
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: Guess the size of a RAID{5,6} device
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- cannot re-assmble mdadm array
- From: Andrew Ryder <tireman@xxxxxxx>
- Re: Guess the size of a RAID{5,6} device
- From: NeilBrown <neilb@xxxxxxx>
- Re: Some info given by 'mdadm --detail --export' are not convenient to use
- From: NeilBrown <neilb@xxxxxxx>
- [GIT PULL REQUEST] md for 3.15
- From: NeilBrown <neilb@xxxxxxx>
- dmcrypt on top of raid5, or raid5 on top of dmcrypt?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- RE: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
- Some info given by 'mdadm --detail --export' are not convenient to use
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: Hardware advice for software raid
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: [PATCH] Fix race between --create and --incremental
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
- Guess the size of a RAID{5,6} device
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: Nvidia Raid5 Failure
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Nvidia Raid5 Failure
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
- RE: Nvidia Raid5 Failure
- From: peter davidson <merrymeetpete@xxxxxxxxxxx>
- Re: Nvidia Raid5 Failure
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
- Nvidia Raid5 Failure
- From: peter davidson <merrymeetpete@xxxxxxxxxxx>
- Re: Nvidia Raid5 Failure
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- [no subject]
- From: peter davidson <merrymeetpete@xxxxxxxxxxx>
- Nvidia Raid5 Failure
- From: peter davidson <merrymeetpete@xxxxxxxxxxx>
- Re: [PATCH] Fix race between --create and --incremental
- From: NeilBrown <neilb@xxxxxxx>
- Re: Hardware advice for software raid
- From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
- [PATCH] Fix race between --create and --incremental
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
- Re: [patch]raid5: get_active_stripe avoids device_lock
- From: NeilBrown <neilb@xxxxxxx>
- Re: [patch]raid5: make_request does less prepare wait
- From: NeilBrown <neilb@xxxxxxx>
- Re: Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
- Re: [patch]raid5: get_active_stripe avoids device_lock
- From: Shaohua Li <shli@xxxxxxxxxx>
- Re: [patch]raid5: make_request does less prepare wait
- From: Shaohua Li <shli@xxxxxxxxxx>
- Re: [patch]raid5: get_active_stripe avoids device_lock
- From: NeilBrown <neilb@xxxxxxx>
- Re: [patch]raid5: make_request does less prepare wait
- From: NeilBrown <neilb@xxxxxxx>
- Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Assistance needed with a failed RAID-5 array
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- [patch]raid5: get_active_stripe avoids device_lock
- From: Shaohua Li <shli@xxxxxxxxxx>
- [patch]raid5: make_request does less prepare wait
- From: Shaohua Li <shli@xxxxxxxxxx>
- Re: Hardware advice for software raid
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Hardware advice for software raid
- From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
- Assistance needed with a failed RAID-5 array
- From: Alan Worstell <aworstell@xxxxxxxxxxxxxxx>
- Re: Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
- RE: Problem Syncing raid1
- From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
- RE: Problem Syncing raid1
- From: Christian Schmitz <schnet@xxxxxxxxxxx>
- Re: Problem Syncing raid1
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: Problem Syncing raid1
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
- Re: Problem Syncing raid1
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: Problem Syncing raid1
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
- Re: Problem Syncing raid1
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
- RE: Problem Syncing raid1
- From: Christian Schmitz <schnet@xxxxxxxxxxx>
- Re: Recent 3.x kernels: Memory leak causing OOMs
- From: NeilBrown <neilb@xxxxxxx>
- RE: Problem Syncing raid1
- From: Christian Schmitz <schnet@xxxxxxxxxxx>
- Re: Problem Syncing raid1
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
- RE: Problem Syncing raid1
- From: Christian Schmitz <schnet@xxxxxxxxxxx>
- Re: Problem Syncing raid1
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
- Re: Problem Syncing raid1
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
- Problem Syncing raid1
- From: Christian Schmitz <schnet@xxxxxxxxxxx>
- Re: Can't grow IMSM RAID5
- From: "nixbugz" <nixbugz@xxxxxxxxxxx>
- [LVM/RAID BUG DATA DESTRUCTION] 3.12.14 raid1 initialisation + --write-mostly destroys LV
- From: David Lamparter <equinox@xxxxxxxxxx>
- Re: [linux-lvm] [LVM/RAID BUG DATA DESTRUCTION] 3.12.14 raid1 initialisation + --write-mostly destroys LV
- From: David Lamparter <equinox@xxxxxxxxxx>
- RE: Can't grow IMSM RAID5
- From: "Paszkiewicz, Artur" <artur.paszkiewicz@xxxxxxxxx>
- Re: Hardware advice for software raid
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Can't grow IMSM RAID5
- From: "nixbugz" <nixbugz@xxxxxxxxxxx>
- Re: strange status raid 5
- From: bobzer <bobzer@xxxxxxxxx>
- Re: strange status raid 5
- From: NeilBrown <neilb@xxxxxxx>
- Re: Hardware advice for software raid
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
- Re: Hardware advice for software raid
- From: Matt Garman <matthew.garman@xxxxxxxxx>
- Hardware advice for software raid
- From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
- Re: Can't grow IMSM RAID5
- From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
- Re: Can't grow IMSM RAID5
- From: "nixbugz" <nixbugz@xxxxxxxxxxx>
- Re: Can't grow IMSM RAID5
- From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
- Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Catalin Marinas <catalin.marinas@xxxxxxx>
- Can't grow IMSM RAID5
- From: "nixbugz" <nixbugz@xxxxxxxxxxx>
- Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: RAIS5 Rebuild Help - Possible Data Offset
- From: Yorik <yoriks13@xxxxxxxxxxxxxx>
- Re: strange status raid 5
- From: bobzer <bobzer@xxxxxxxxx>
- Re: strange status raid 5
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- strange status raid 5
- From: bobzer <bobzer@xxxxxxxxx>
- Re: Raid10 to Raid0 conversion
- From: Marcin Wanat <mwanat@xxxxxxxxx>
- Re: RAIS5 Rebuild Help - Possible Data Offset
- From: NeilBrown <neilb@xxxxxxx>
- Re: RAIS5 Rebuild Help - Possible Data Offset
- From: Yorik <yoriks13@xxxxxxxxxxxxxx>
- Re: RAIS5 Rebuild Help - Possible Data Offset
- From: NeilBrown <neilb@xxxxxxx>
- Re: RAIS5 Rebuild Help - Possible Data Offset
- From: Yorik <yoriks13@xxxxxxxxxxxxxx>
- Re: Raid10 to Raid0 conversion
- From: NeilBrown <neilb@xxxxxxx>
- Re: RAIS5 Rebuild Help - Possible Data Offset
- From: NeilBrown <neilb@xxxxxxx>
- Re: Check/repair command?
- From: NeilBrown <neilb@xxxxxxx>
- Re: raid6check.c patches
- From: NeilBrown <neilb@xxxxxxx>
- [PATCH 3.2 108/200] md/raid5: Fix CPU hotplug callback registration
- From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
- Re: raid resync speed
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Tide <lovetide@xxxxxx>
- Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: raid resync speed
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
- Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
- Re: Array created by mdadm 3.2 & 3.3 have different array size
- From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
- Re: Array created by mdadm 3.2 & 3.3 have different array size
- From: Tide <lovetide@xxxxxx>
- Re: Array created by mdadm 3.2 & 3.3 have different array size
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Array created by mdadm 3.2 & 3.3 have different array size
- From: Tide <lovetide@xxxxxx>
- Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Tide <lovetide@xxxxxx>
- Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Tide <lovetide@xxxxxx>
- Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- raid6check.c patches
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Larry Fenske <LFenske@xxxxxxx>
- Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: "Tide" <lovetide@xxxxxx>
- [PATCH] dm cache: remove unused function too_many_discard_blocks
- From: SeongJae Park <sj38.park@xxxxxxxxx>
- Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- [PATCH] fix write-mostly logic
- From: "Vladimir B. Savkin" <master@xxxxxxxxxxxxxx>
- Re: Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
- Re: Missing superblocks from almost all my drives
- From: Caspar Smit <c.smit@xxxxxxxxxx>
- Re: Missing superblocks from almost all my drives
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Missing superblocks from almost all my drives
- From: Mark Munoz <mark.munoz@xxxxxxxxxxxxxxxxxxx>
- Check/repair command?
- From: Phillip Susi <psusi@xxxxxxxxxx>
- RE: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
- [PATCH] drivers/md: Use RCU_INIT_POINTER(x, NULL) in dm.c
- From: Monam Agarwal <monamagarwal123@xxxxxxxxx>
- Re: Raid10 to Raid0 conversion
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Raid10 to Raid0 conversion
- From: Marcin Wanat <mwanat@xxxxxxxxx>
- patch: raid5: avoid release list until last reference
- From: Eivind Sarto <eivindsarto@xxxxxxxxx>
- Re: raid resync speed
- From: Jeff Allison <jeff.allison@xxxxxxxxxxxxxxx>
- Re: raid resync speed
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: raid resync speed
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
- Re: raid resync speed
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
- Re: raid resync speed
- From: Eivind Sarto <eivindsarto@xxxxxxxxx>
- Re: raid resync speed
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
- Re: raid resync speed
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
- Re: raid resync speed
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- RE: raid6 - data intefrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
- Re: Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
- raid resync speed
- From: Jeff Allison <jeff.allison@xxxxxxxxxxxxxxx>
- Re: [PATCH 2/2] md: fix deadlock while suspending RAID array
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH 1/1] Work around architectures having statfs.f_type defined as long
- From: NeilBrown <neilb@xxxxxxx>
- Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/1] Work around architectures having statfs.f_type defined as long
- From: Arnd Bergmann <arnd@xxxxxxxx>
- [PATCH 0/1] Work around systems defining statfs.f_type as long
- From: Jes.Sorensen@xxxxxxxxxx
- [PATCH 1/1] Work around architectures having statfs.f_type defined as long
- From: Jes.Sorensen@xxxxxxxxxx
- Re: Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 0/2] md: fix fix deadlock while suspending RAID array
- From: Simon Guinot <simon.guinot@xxxxxxxxxxxx>
- Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 2/2] md: Add support for RAID-1 consistency check feature
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH 1/2] md: Add configurability for consistency check feature
- From: NeilBrown <neilb@xxxxxxx>
- Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Catalin Marinas <catalin.marinas@xxxxxxx>
- [PATCH 1/2] md: Add configurability for consistency check feature
- From: Ralph Mueck <linux-kernel@xxxxxxxxx>
- [PATCH 2/2] md: Add support for RAID-1 consistency check feature
- From: Ralph Mueck <linux-kernel@xxxxxxxxx>
- [PATCH 0/2] md: Add consistency check feature for level-1 RAID
- From: Ralph Mueck <linux-kernel@xxxxxxxxx>
- [PATCH] md: Fixed issue in raid1 that may lead to data corruption
- From: Ralph Mueck <linux-kernel@xxxxxxxxx>
- Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: Recent 3.x kernels: Memory leak causing OOMs
- From: NeilBrown <neilb@xxxxxxx>
- Re: Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
- "Free swap" drops during raid data-check
- From: Rolf Fokkens <rolf@xxxxxxxxxxxxxx>
- Re: raid5 write latency is 10x the drive latency
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
- Re: Raid stalls during --replace and other disk activity...
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: Raid stalls during --replace and other disk activity...
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
- Re: Raid stalls during --replace and other disk activity...
- From: Phil Turmel <philip@xxxxxxxxxx>
- [PATCH] raid6check.c: move manual repair code to separate function
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- [PATCH] raid6check.c: move autorepair code to separate function
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- [PATCH] raid6check.c: lock the stripe until necessary
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Raid stalls during --replace and other disk activity...
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
- Re: mapping disk sectors to files
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: mapping disk sectors to files
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- mapping disk sectors to files
- From: Thorsten von Eicken <tve@xxxxxxxxxxxxx>
- Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
- From: "Samer, Michael (I/ET-83, extern)" <extern.michael.samer@xxxxxxx>
- Re: calculating optimal chunk size for Linux software-RAID
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Replace RAID devices without resorting to degraded mode?
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: NeilBrown <neilb@xxxxxxx>
- Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
- Re: Replace RAID devices without resorting to degraded mode?
- From: NeilBrown <neilb@xxxxxxx>
- Re: Linux software-RAID and bootloader
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Linux software-RAID and bootloader
- From: Martin T <m4rtntns@xxxxxxxxx>
- Re: Replace RAID devices without resorting to degraded mode?
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
- Re: calculating optimal chunk size for Linux software-RAID
- From: Martin T <m4rtntns@xxxxxxxxx>
- Re: Replace RAID devices without resorting to degraded mode?
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Replace RAID devices without resorting to degraded mode?
- From: Raul Dias <raul@xxxxxxxxxxx>
- Re: Replace RAID devices without resorting to degraded mode?
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: Replace RAID devices without resorting to degraded mode?
- From: David Brown <david.brown@xxxxxxxxxxxx>
- RE: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
- Re: [PATCH] poll/wait/md: allow module to safely support 'poll' on /proc files
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH] poll/wait/md: allow module to safely support 'poll' on /proc files
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] poll/wait/md: allow module to safely support 'poll' on /proc files
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH] poll/wait/md: allow module to safely support 'poll' on /proc files
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- [PATCH] poll/wait/md: allow module to safely support 'poll' on /proc files
- From: NeilBrown <neilb@xxxxxxx>
- Re: Replace RAID devices without resorting to degraded mode?
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
- Re: Replace RAID devices without resorting to degraded mode?
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
- [PATCH 1/2] md: move up mddev locking functions
- From: Simon Guinot <simon.guinot@xxxxxxxxxxxx>
- [PATCH 2/2] md: fix deadlock while suspending RAID array
- From: Simon Guinot <simon.guinot@xxxxxxxxxxxx>
- [PATCH 0/2] md: fix fix deadlock while suspending RAID array
- From: Simon Guinot <simon.guinot@xxxxxxxxxxxx>
- Replace RAID devices without resorting to degraded mode?
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
- Re: calculating optimal chunk size for Linux software-RAID
- From: Bill Davidsen <davidsen@xxxxxxx>
- Re: [PATCH] mdmon@.service: Change type of process start-up to 'forking'.
- From: NeilBrown <neilb@xxxxxxx>
- Re: raid6 - data intefrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: NeilBrown <neilb@xxxxxxx>
- Re: grub and mdadm
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: grub and mdadm
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: I've made a bit of a mess in my raid setup
- From: NeilBrown <neilb@xxxxxxx>
- grub and mdadm
- From: AdsGroup <AdsGroup@xxxxxxx>
- Re: Linux software-RAID and bootloader
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: I've made a bit of a mess in my raid setup
- From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Re: I've made a bit of a mess in my raid setup
- From: Federico Foschini <undicizeri@xxxxxxxxx>
- Re: I've made a bit of a mess in my raid setup
- From: Federico Foschini <undicizeri@xxxxxxxxx>
- Re: I've made a bit of a mess in my raid setup
- From: Can Jeuleers <can.jeuleers@xxxxxxxxx>
- Re: Linux software-RAID and bootloader
- From: Raul Dias <raul@xxxxxxxxxxx>
- Re: Linux software-RAID and bootloader
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: I've made a bit of a mess in my raid setup
- From: Federico Foschini <undicizeri@xxxxxxxxx>
- Re: I've made a bit of a mess in my raid setup
- From: Can Jeuleers <can.jeuleers@xxxxxxxxx>
- Re: I've made a bit of a mess in my raid setup
- From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Re: I've made a bit of a mess in my raid setup
- From: Federico Foschini <undicizeri@xxxxxxxxx>
- Re: I've made a bit of a mess in my raid setup
- From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Re: I've made a bit of a mess in my raid setup
- From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Re: I've made a bit of a mess in my raid setup
- From: Federico Foschini <undicizeri@xxxxxxxxx>
- I've made a bit of a mess in my raid setup
- From: Federico Foschini <undicizeri@xxxxxxxxx>
- Re: calculating optimal chunk size for Linux software-RAID
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Linux software-RAID and bootloader
- From: Martin T <m4rtntns@xxxxxxxxx>
- Re: calculating optimal chunk size for Linux software-RAID
- From: Martin T <m4rtntns@xxxxxxxxx>
- Re: Is mdadm.conf needed?
- From: Martin T <m4rtntns@xxxxxxxxx>
- Re: calculating optimal chunk size for Linux software-RAID
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Is mdadm.conf needed?
- From: Joe Landman <joe.landman@xxxxxxxxx>
- Re: Is mdadm.conf needed?
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Linux software-RAID and bootloader
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Is mdadm.conf needed?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
- Re: Linux software-RAID and bootloader
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
- Re: randconfig build error with next-20140307, in drivers/md/dm-era-target.c
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
- Linux software-RAID and bootloader
- From: Martin T <m4rtntns@xxxxxxxxx>
- Is mdadm.conf needed?
- From: Martin T <m4rtntns@xxxxxxxxx>
- calculating optimal chunk size for Linux software-RAID
- From: Martin T <m4rtntns@xxxxxxxxx>
- Re: Grow on RAID 6 failed can I revert back to previous total drives?
- From: Jared Raddigan <jraddigan@xxxxxxx>
- [PATCH] mdmon@.service: Change type of process start-up to 'forking'.
- From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
- Re: RAID 10 problems, two disks marked as spare
- From: Jim Bauwens <jim@xxxxxxx>
- Grow on RAID 6 failed can I revert back to previous total drives?
- From: Jared Raddigan <jraddigan@xxxxxxx>
- Re: RAID5 hard freeze
- From: Denis Golovan <denis.golovan@xxxxxxxxx>
- Re: raid5 write latency is 10x the drive latency
- From: NeilBrown <neilb@xxxxxxx>
- Re: raid5 write latency is 10x the drive latency
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
- Re: raid5 write latency is 10x the drive latency
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
- Re: RAID5 hard freeze
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
- Re: raid5 write latency is 10x the drive latency
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
- Re: raid5 write latency is 10x the drive latency
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
- Re: External USB-SATA bridge rewriting logical block sizes
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: raid5 write latency is 10x the drive latency
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
- Re: raid5 write latency is 10x the drive latency
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
- [PATCH 3.8 59/67] md/raid5: Fix CPU hotplug callback registration
- From: Kamal Mostafa <kamal@xxxxxxxxxxxxx>
- Re: External USB-SATA bridge rewriting logical block sizes
- From: Jan Kundrát <jkt@xxxxxxxxxx>
- Re: External USB-SATA bridge rewriting logical block sizes
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- raid5 write latency is 10x the drive latency
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
- External USB-SATA bridge rewriting logical block sizes
- From: Jan Kundrát <jkt@xxxxxxxxxx>
- Re: [PATCH] md / procfs: avoid Oops if md-mod removed while /proc/mdstat is being polled.
- From: NeilBrown <neilb@xxxxxxx>
- Re: how to handle bad sectors in md control areas?
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Re: how to handle bad sectors in md control areas?
- From: NeilBrown <neilb@xxxxxxx>
- Re: how to handle bad sectors in md control areas?
- From: NeilBrown <neilb@xxxxxxx>
- Re: how to handle bad sectors in md control areas?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
- Re: Problem with patch: "reject a re-add request that cannot be honoured" (commit bedd86b7773fd97f0d708cc0c371c8963ba7ba9a)
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
- Raid 5 events not updates after resync
- From: John <linux_mailing@xxxxxxxxxxxxxxxx>
- Re: how to handle bad sectors in md control areas?
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Re: [md PATCH 00/10] md patches for 3.5: RAID10 reshape
- From: Phillip Susi <psusi@xxxxxxxxxx>
- Re: RAID5 hard freeze
- From: Denis Golovan <denis.golovan@xxxxxxxxx>
- Re: [dm-devel] [PATCH] dm-raid: check events in super_validate
- From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
- Re: [md PATCH 00/10] md patches for 3.5: RAID10 reshape
- From: NeilBrown <neilb@xxxxxxx>
- Re: [md PATCH 00/10] md patches for 3.5: RAID10 reshape
- From: Phillip Susi <psusi@xxxxxxxxxx>
- Re: [dm-devel] [PATCH] dm-raid: check events in super_validate
- From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
- RAID 10 problems, two disks marked as spare
- Re: how to handle bad sectors in md control areas?
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Re: how to handle bad sectors in md control areas?
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- [PATCH 2/2] imsm: improved platform capabilities checking
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
- [PATCH 1/2] imsm: support for second AHCI controller in EFI mode
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
- [PATCH 0/2] imsm: fixes for platform capabilities checking
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
- Re: how to handle bad sectors in md control areas?
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Re: [PATCH] md / procfs: avoid Oops if md-mod removed while /proc/mdstat is being polled.
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] md / procfs: avoid Oops if md-mod removed while /proc/mdstat is being polled.
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH] md / procfs: avoid Oops if md-mod removed while /proc/mdstat is being polled.
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] md / procfs: avoid Oops if md-mod removed while /proc/mdstat is being polled.
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH] md / procfs: avoid Oops if md-mod removed while /proc/mdstat is being polled.
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Re: Recovering RAID-6 from a Failed Grow
- From: Jakob Unterwurzacher <jakobunt@xxxxxxxxx>
- [PATCH] md / procfs: avoid Oops if md-mod removed while /proc/mdstat is being polled.
- From: NeilBrown <neilb@xxxxxxx>
- Re: Problem with patch: "reject a re-add request that cannot be honoured" (commit bedd86b7773fd97f0d708cc0c371c8963ba7ba9a)
- From: NeilBrown <neilb@xxxxxxx>
- Re: [dm-devel] [PATCH] dm-raid: check events in super_validate
- From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
- Re: [dm-devel] [PATCH] dm-raid: check events in super_validate
- From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
- Re: RAID5 hard freeze
- From: Denis Golovan <denis.golovan@xxxxxxxxx>
- Re: Problem with patch: "reject a re-add request that cannot be honoured" (commit bedd86b7773fd97f0d708cc0c371c8963ba7ba9a)
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
- Re: md raid6: slow resync if fs is mounted rw
- From: Jakob Unterwurzacher <jakobunt@xxxxxxxxx>
- how to handle bad sectors in md control areas?
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Re: Reshape RAID10 -> RAID1
- From: Charles Polisher <cpolish@xxxxxxxxxxxx>
- Recovering RAID-6 from a Failed Grow
- From: Karl Wilbur <karl@xxxxxxxxxxxxxx>
- Re: Reshape RAID10 -> RAID1
- From: NeilBrown <neilb@xxxxxxx>
- Reshape RAID10 -> RAID1
- From: Charles Polisher <cpolish@xxxxxxxxxxxx>
- Re: Cannot assemble DDF raid
- From: NeilBrown <neilb@xxxxxxx>
- Re: md raid6: slow resync if fs is mounted rw
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
- Re: md raid6: slow resync if fs is mounted rw
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH] dm-raid: check events in super_validate
- From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
- md raid6: slow resync if fs is mounted rw
- From: Jakob Unterwurzacher <jakobunt@xxxxxxxxx>
- Re: [PATCH] dm-raid: check events in super_validate
- From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
- Re: [PATCH] dm-raid: check events in super_validate
- From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
- Re: dm thin: inverted down_trylock() test
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Re: mdadm won't remove drive from array
- From: Caspar Smit <c.smit@xxxxxxxxxx>
- [patch] dm thin: inverted down_trylock() test
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: NeilBrown <neilb@xxxxxxx>
- Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Questions regarding bad block management
- From: NeilBrown <neilb@xxxxxxx>
- Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Re: [PATCH] dm-raid: check events in super_validate
- From: NeilBrown <neilb@xxxxxxx>
- Re: non-persistent superblocks? [WORKAROUND]
- From: NeilBrown <neilb@xxxxxxx>
- Re: feature re-quest for "re-write"
- From: NeilBrown <neilb@xxxxxxx>
- Re: RAID5 hard freeze
- From: NeilBrown <neilb@xxxxxxx>
- Re: feature re-quest for "re-write"
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: NeilBrown <neilb@xxxxxxx>
- Re: request help with RAID1 array that endlessly attempts to sync
- From: Julie Ashworth <ashworth@xxxxxxxxxxxx>
- RAID5 hard freeze
- From: Denis Golovan <denis.golovan@xxxxxxxxx>
- Re: mdadm won't remove drive from array
- From: NeilBrown <neilb@xxxxxxx>
- Re: Data Offset
- From: NeilBrown <neilb@xxxxxxx>
- [PATCH v5 2/3] fs: btrfs: Adds new par3456 modes to support up to six parities
- From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
- [PATCH v5 3/3] btrfs-progs: Adds new par3456 modes to support up to six parities
- From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
- [PATCH v5 0/3] New RAID library supporting up to six parities
- From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
- Re: raid 'check' does not provoke expected i/o error
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- [3.8.y.z extended stable] Patch "md/raid5: Fix CPU hotplug callback registration" has been added to staging queue
- From: Kamal Mostafa <kamal@xxxxxxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
- Re: mdadm won't remove drive from array
- From: Caspar Smit <c.smit@xxxxxxxxxx>
- AW: AW: AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
- From: "Samer, Michael (I/ET-83, extern)" <extern.michael.samer@xxxxxxx>
- Re: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: Data Offset
- From: wiebittewas <wiebittewas@xxxxxxxxxxxxxx>
- Re: mdadm won't remove drive from array
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- mdadm won't remove drive from array
- From: Caspar Smit <c.smit@xxxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: What is the sector size in /sys/block/md*/md items?
- From: NeilBrown <neilb@xxxxxxx>
- Re: feature re-quest for "re-write"
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Re: feature re-quest for "re-write"
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
- What is the sector size in /sys/block/md*/md items?
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- mdadm may fail to assemble clean raid5 array with failed drive
- From: Eivind Sarto <eivindsarto@xxxxxxxxx>
- feature re-quest for "re-write"
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: raid 'check' does not provoke expected i/o error
- From: Larry Fenske <LFenske@xxxxxxx>
- [PATCH 3.5 54/60] md/raid5: Fix CPU hotplug callback registration
- From: Luis Henriques <luis.henriques@xxxxxxxxxxxxx>
- [3.5.y.z extended stable] Patch "md/raid5: Fix CPU hotplug callback registration" has been added to staging queue
- From: Luis Henriques <luis.henriques@xxxxxxxxxxxxx>
- [PATCH 3.11 102/121] md/raid5: Fix CPU hotplug callback registration
- From: Luis Henriques <luis.henriques@xxxxxxxxxxxxx>
- [3.11.y.z extended stable] Patch "md/raid5: Fix CPU hotplug callback registration" has been added to staging queue
- From: Luis Henriques <luis.henriques@xxxxxxxxxxxxx>
- Re: AW: raid 'check' does not provoke expected i/o error
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- AW: raid 'check' does not provoke expected i/o error
- From: "Samer, Michael (I/ET-83, extern)" <extern.michael.samer@xxxxxxx>
- raid 'check' does not provoke expected i/o error
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
- Cannot assemble DDF raid
- From: Christian Iversen <ci@xxxxxxxxxx>
- [PATCH 3.4 21/25] md/raid5: Fix CPU hotplug callback registration
- From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
- [PATCH 3.10 58/66] md/raid5: Fix CPU hotplug callback registration
- From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
- [PATCH 3.12 73/82] md/raid5: Fix CPU hotplug callback registration
- From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
- [PATCH 3.13 90/99] md/raid5: Fix CPU hotplug callback registration
- From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] bcache: fix NULL pointer deref in blk_add_request_payload
- From: Lars Ellenberg <lars@xxxxxxxxxx>
- [PATCH] bcache: fix NULL pointer deref in blk_add_request_payload
- From: Lars Ellenberg <lars@xxxxxxxxxx>
- Re: Problem with patch: "reject a re-add request that cannot be honoured" (commit bedd86b7773fd97f0d708cc0c371c8963ba7ba9a)
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
- Re: Need Advice regarding chunk size of RAID6 regarding HFS+
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Need Advice regarding chunk size of RAID6 regarding HFS+
- From: Florian Lampel <florian.lampel@xxxxxxxxx>
- Re: raid5 replace ignored error?
- From: Bill <billstuff2001@xxxxxxxxxxxxx>
- Re: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
- From: Phil Turmel <philip@xxxxxxxxxx>
- AW: AW: AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
- From: "Samer, Michael (I/ET-83, extern)" <extern.michael.samer@xxxxxxx>
- Re: raid5 replace ignored error?
- From: NeilBrown <neilb@xxxxxxx>
- Re: AW: AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
- From: Phil Turmel <philip@xxxxxxxxxx>
- AW: AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
- From: "Samer, Michael (I/ET-83, extern)" <extern.michael.samer@xxxxxxx>
- Re: AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
- From: Phil Turmel <philip@xxxxxxxxxx>
- AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
- From: "Samer, Michael (I/ET-83, extern)" <extern.michael.samer@xxxxxxx>
- mdadm assemble bug?
- From: Eivind Sarto <eivindsarto@xxxxxxxxx>
- Re: RAID6 dead on the water after Controller failure
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: RAID6 dead on the water after Controller failure
- From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
- Re: RAID6 dead on the water after Controller failure
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: RAID6 dead on the water after Controller failure
- From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
- Re: RAID6 dead on the water after Controller failure
- From: "Bakk. Florian Lampel" <florian.lampel@xxxxxxxxx>
- Re: RAID6 dead on the water after Controller failure
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: RAID6 dead on the water after Controller failure
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: RAID6 dead on the water after Controller failure
- From: Florian Lampel <florian.lampel@xxxxxxxxx>
- Re: RAID6 dead on the water after Controller failure
- From: Florian Lampel <florian.lampel@xxxxxxxxx>
- Re: RAID6 dead on the water after Controller failure
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: RAID6 dead on the water after Controller failure
- From: Florian Lampel <florian.lampel@xxxxxxxxx>
- Re: Automatically drop caches after mdadm fails a drive out of an array?
- From: Andrew Martin <amartin@xxxxxxxxxxx>
- Re: RAID6 dead on the water after Controller failure
- From: Phil Turmel <philip@xxxxxxxxxx>
- RAID6 dead on the water after Controller failure
- From: Florian Lampel <florian.lampel@xxxxxxxxx>
- Re: Automatically drop caches after mdadm fails a drive out of an array?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Automatically drop caches after mdadm fails a drive out of an array?
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: Automatically drop caches after mdadm fails a drive out of an array?
- From: Andrew Martin <amartin@xxxxxxxxxxx>
- Re: Automatically drop caches after mdadm fails a drive out of an array?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Z87 vs ASMedia
- From: Raul Dias <raul@xxxxxxxxxxx>
- Re: Automatically drop caches after mdadm fails a drive out of an array?
- From: Andrew Martin <amartin@xxxxxxxxxxx>
- Re: Automatically drop caches after mdadm fails a drive out of an array?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Automatically drop caches after mdadm fails a drive out of an array?
- From: Andrew Martin <amartin@xxxxxxxxxxx>
- Re: Automatically drop caches after mdadm fails a drive out of an array?
- From: NeilBrown <neilb@xxxxxxx>
- sector mapping
- From: Larry Fenske <LFenske@xxxxxxx>
- Re: Raid 6 rebuild
- From: Chris Murphy <chris@xxxxxxxxxxxxxxxxx>
- Raid 6 rebuild
- From: "Gallas, William N" <william.n.gallas@xxxxxxxxx>
- Automatically drop caches after mdadm fails a drive out of an array?
- From: Andrew Martin <amartin@xxxxxxxxxxx>
- Re: [PATCH 1/1] md/raid5: allow resync-rebuild requests to run multi-threaded
- From: NeilBrown <neilb@xxxxxxx>
- [PATCH 1/1] md/raid5: allow resync-rebuild requests to run multi-threaded
- From: Eivind Sarto <eivindsarto@xxxxxxxxx>
- Re: Reassemble Raid 6
- From: Phil Turmel <philip@xxxxxxxxxx>
- md/raid5.c and STRIPE_IO_STARTED
- From: Eivind Sarto <eivindsarto@xxxxxxxxx>
- Re[2]: Reassemble Raid 6
- From: "Justin Stephenson" <justin@xxxxxxxxxxxxxxxxx>
- Re: Reassemble Raid 6
- From: Phil Turmel <philip@xxxxxxxxxx>
- Reassemble Raid 6
- From: "Justin Stephenson" <justin@xxxxxxxxxxxxxxxxx>
- Re: Bug#737951: mdadm: udev rules files ignores raid=noautodetect kernel parameter
- From: Michael Prokop <mika@xxxxxxxxxx>
- Re: Storage system
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Storage system
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Storage system
- From: Robert L Mathews <lists@xxxxxxxxxxxxx>
- Re: raid6 caught in rebuild loop
- From: Benedikt Fraunhofer <benedikt.fraunhofer.lists.mdadm.67B-ACM@xxxxxxxxxx>
- Re: Storage system
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Storage system
- From: Can Jeuleers <can.jeuleers@xxxxxxxxx>
- Re: Storage system
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Storage system
- From: Roberto Spadim <rspadim@xxxxxxxxx>
- Re: Storage system
- From: Roman Mamedov <rm@xxxxxxxxxxx>
- Re: Storage system
- From: Matt Garman <matthew.garman@xxxxxxxxx>
- Re: Storage system
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: Bug#737951: mdadm: udev rules files ignores raid=noautodetect kernel parameter
- From: Michael Tokarev <mjt@xxxxxxxxxx>
- Re: Intent Bitmap size and performance
- From: NeilBrown <neilb@xxxxxxx>
- Re: Storage system
- From: Joe Landman <joe.landman@xxxxxxxxx>
- Re: Intent Bitmap size and performance
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: [PATCH 45/51] md, raid5: Fix CPU hotplug callback registration
- From: Oleg Nesterov <oleg@xxxxxxxxxx>
- Storage system
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- Re: raid1 repair does not repair errors?
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
- From: "Samer, Michael (I/ET-83, extern)" <extern.michael.samer@xxxxxxx>
- Re: [PATCH 45/51] md, raid5: Fix CPU hotplug callback registration
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH 45/51] md, raid5: Fix CPU hotplug callback registration
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH] raid6check.c: reduce verbosity
- From: NeilBrown <neilb@xxxxxxx>
- [PATCH 45/51] md, raid5: Fix CPU hotplug callback registration
- From: "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] raid6check.c: reduce verbosity
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Phillip Susi <psusi@xxxxxxxxxx>
- Re: raid1 repair does not repair errors?
- From: NeilBrown <neilb@xxxxxxx>
- mdadm, raid 6 best options if any?
- From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Phillip Susi <psusi@xxxxxxxxxx>
- Re: raid1 repair does not repair errors?
- From: Michael Tokarev <mjt@xxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Phillip Susi <psusi@xxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Phillip Susi <psusi@xxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Larry Fenske <LFenske@xxxxxxx>
- Re: Soft RAID and EFI systems
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: sequential versus random I/O
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: David Brown <david.brown@xxxxxxxxxxxx>
- raid5 replace ignored error?
- From: Bill <billstuff2001@xxxxxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: [PATCH] raid6check.c: reduce verbosity
- From: NeilBrown <neilb@xxxxxxx>
- Re: raid1 repair does not repair errors?
- From: NeilBrown <neilb@xxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: [PATCH] block devices: validate block device capacity
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- Re: sequential versus random I/O
- From: Matt Garman <matthew.garman@xxxxxxxxx>
- Re: [PATCH resend 1/2] bcache: Use %zi to format size_t
- From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
- Re: raid1 repair does not repair errors?
- From: Michael Tokarev <mjt@xxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Phillip Susi <psusi@xxxxxxxxxx>
- [PATCH v2 2/2] bcache: Drop L-suffix when comparing ssize_t with 0
- From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
- [PATCH resend 1/2] bcache: Use %zi to format size_t
- From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: [PATCH] block devices: validate block device capacity
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- Re: raid1 repair does not repair errors?
- From: Michael Tokarev <mjt@xxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Martin Wilck <mwilck@xxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: raid1 repair does not repair errors?
- From: NeilBrown <neilb@xxxxxxx>
- SOLVED - Re: md raid0 with overwritten superblock on 1/4 disks
- From: travis+ml-linux-raid@xxxxxxxxxxxxxxxxx
- md raid0 with overwritten superblock on 1/4 disks
- From: travis+ml-linux-raid@xxxxxxxxxxxxxxxxx
- Re: raid1 repair does not repair errors?
- From: NeilBrown <neilb@xxxxxxx>
- Re: Soft RAID and EFI systems
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Martin Wilck <mwilck@xxxxxxxx>
- Re: raid1 repair does not repair errors?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
- Re: Soft RAID and EFI systems
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Phillip Susi <psusi@xxxxxxxxxx>
- Re: raid1 repair does not repair errors?
- From: Michael Tokarev <mjt@xxxxxxxxxx>
- Re: Intent Bitmap size and performance
- From: NeilBrown <neilb@xxxxxxx>
- Re: Intent Bitmap size and performance
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Intent Bitmap size and performance
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Soft RAID and EFI systems
- From: Martin Wilck <mwilck@xxxxxxxx>
- [PATCH] raid6check.c: add O_SYNC to open
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- [PATCH] raid6check.c: fix Q parity generation
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- Re: sequential versus random I/O
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- [PATCH] raid6check.c: fix position printout
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- [PATCH] raid6check.c: reduce verbosity
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- [PATCH] dm-raid: check events in super_validate
- From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
- Re: RAIS5 Rebuild Help - Possible Data Offset
- From: Yorik <yoriks13@xxxxxxxxxxxxxx>
- Soft RAID and EFI systems
- From: Francis Moreau <francis.moro@xxxxxxxxx>
- Re: RAIS5 Rebuild Help - Possible Data Offset
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
- Re: Boot fails from one of the drives cos it's not an ext4 filesystem.
- From: Richard Gomes <rgomes.info@xxxxxxxxx>
- Re: Boot fails from one of the drives cos it's not an ext4 filesystem.
- From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
- Re: [PATCH] block devices: validate block device capacity
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- Re: md hang on updating bitmap
- From: Marcus <shadowsor@xxxxxxxxx>
- Re: [PATCH] block devices: validate block device capacity
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] block devices: validate block device capacity
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- Re: [PATCH] block devices: validate block device capacity
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
- Re: Boot fails from one of the drives cos it's not an ext4 filesystem.
- From: Robert L Mathews <lists@xxxxxxxxxxxxx>
- Re: [PATCH] block devices: validate block device capacity
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- Re: [PATCH] block devices: validate block device capacity
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] block devices: validate block device capacity
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- Re: [PATCH] block devices: validate block device capacity
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
- Re: [HELP] Recover a RAID5 with 8 drives
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Boot fails from one of the drives cos it's not an ext4 filesystem.
- From: Richard Gomes <rgomes.info@xxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Phillip Susi <psusi@xxxxxxxxxx>
- [PATCH] block devices: validate block device capacity
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Phillip Susi <psusi@xxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Phillip Susi <psusi@xxxxxxxxxx>
- Re: Why are reads not balanced across my RAID-1?
- From: Phillip Susi <psusi@xxxxxxxxxx>
- raid6 caught in rebuild loop
- From: Benedikt Fraunhofer <benedikt.fraunhofer.lists.mdadm.67B-ACM@xxxxxxxxxx>
- Re: non-persistent superblocks? [WORKAROUND]
- From: Chris Schanzle <mdadm@xxxxxxxxxxxxxxxxx>
- Re: sequential versus random I/O
- From: Matt Garman <matthew.garman@xxxxxxxxx>
- RAIS5 Rebuild Help - Possible Data Offset
- From: Yorik <yoriks13@xxxxxxxxxxxxxx>
- RAID6 Rebuild Issue - Data Offset possibly
- From: Yorik <yoriks13@xxxxxxxxxxxxxx>
- AW: AW: [HELP] Recover a RAID5 with 8 drives
- From: "Samer, Michael (I/ET-83, extern)" <extern.michael.samer@xxxxxxx>
- AW: AW: [HELP] Recover a RAID5 with 8 drives
- From: "Samer, Michael (I/ET-83, extern)" <extern.michael.samer@xxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: sequential versus random I/O
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: non-persistent superblocks?
- From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
- Re: AW: [HELP] Recover a RAID5 with 8 drives
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
- non-persistent superblocks?
- From: Chris Schanzle <mdadm@xxxxxxxxxxxxxxxxx>
- Re: sequential versus random I/O
- From: Roberto Spadim <rspadim@xxxxxxxxx>
- Re: sequential versus random I/O
- From: Matt Garman <matthew.garman@xxxxxxxxx>
- Re: sequential versus random I/O
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: sequential versus random I/O
- From: Roberto Spadim <rspadim@xxxxxxxxx>
- Re: sequential versus random I/O
- From: Roberto Spadim <rspadim@xxxxxxxxx>
- Re: sequential versus random I/O
- From: Roberto Spadim <rspadim@xxxxxxxxx>
- Re: sequential versus random I/O
- From: Roberto Spadim <rspadim@xxxxxxxxx>
- Re: sequential versus random I/O
- From: Roberto Spadim <rspadim@xxxxxxxxx>
- Re: sequential versus random I/O
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
- sequential versus random I/O
- From: Matt Garman <matthew.garman@xxxxxxxxx>
- Re: AW: [HELP] Recover a RAID5 with 8 drives
- From: Maurizio De Santis <m.desantis@xxxxxxxxxxxxx>
- Re: Raid recovery - raid5 - one active, two spares
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Raid recovery - raid5 - one active, two spares
- From: Mariusz Zalewski <mariusz@xxxxxxxxxxx>
- AW: [HELP] Recover a RAID5 with 8 drives
- From: "Samer, Michael (I/ET-83, extern)" <extern.michael.samer@xxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- [HELP] Recover a RAID5 with 8 drives
- From: Maurizio De Santis <m.desantis@xxxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Questions regarding bad block management
- From: Clemens Eisserer <linuxhippy@xxxxxxxxx>
- Re: Why are reads not balanced across my RAID-1?
- From: Robert L Mathews <lists@xxxxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Phil Turmel <philip@xxxxxxxxxx>
- md hang on updating bitmap
- From: admin <admin@xxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Dag Nygren <dag@xxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- [RFC v4 3/3] crypto: async_tx: Extends crypto/async_tx to support up to six parities
- From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
- [RFC v4 2/3] fs: btrfs: Extends btrfs/raid56 to support up to six parities
- From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
- [RFC v4 0/3] lib: raid: New RAID library supporting up to six parities
- From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
- Re: Why are reads not balanced across my RAID-1?
- Re: Why are reads not balanced across my RAID-1?
- From: "George Spelvin" <linux@xxxxxxxxxxx>
- Re: looking for advice on raid0+raid5 array recovery with mdadm and sector offset
- From: den Hoog <speedyden@xxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Why are reads not balanced across my RAID-1?
- From: Roberto Spadim <rspadim@xxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Why are reads not balanced across my RAID-1?
- Re: Questions about bitrot and RAID 5/6
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: Why are reads not balanced across my RAID-1?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Why are reads not balanced across my RAID-1?
- From: Matt Garman <matthew.garman@xxxxxxxxx>
- Re: Why are reads not balanced across my RAID-1?
- From: "George Spelvin" <linux@xxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: Why are reads not balanced across my RAID-1?
- Why are reads not balanced across my RAID-1?
- From: "George Spelvin" <linux@xxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: NeilBrown <neilb@xxxxxxx>
- [GIT PULL REQUEST] md updates for 3.14
- From: NeilBrown <neilb@xxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Phil Turmel <philip@xxxxxxxxxx>
- [PATCH] raid6check.c: remove legacy code
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- Re: [PATCH] raid6check.c add page size check and repair
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: "John Stoffel" <john@xxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Why 4k native drives haven't arrived
- From: Phillip Susi <psusi@xxxxxxxxxx>
- Re: [PATCH] raid6check.c add page size check and repair
- From: NeilBrown <neilb@xxxxxxx>
- LVM raid1 mirror: interrupted resync isn't handled well
- From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: [BUG] at drivers/md/raid5.c:291! kernel 3.13-rc8
- From: Ian Kumlien <ian.kumlien@xxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: MDADM 3.3 broken?
- From: "David F." <df7729@xxxxxxxxx>
- Re: Opal 2.0 SEDs on linux, was: Very long raid5 init/rebuild times
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Looking for some advice on best way to identify drives / recover from issues
- From: Dylan Distasio <interzone@xxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: [BUG] at drivers/md/raid5.c:291! kernel 3.13-rc8
- From: NeilBrown <neilb@xxxxxxx>
- Re: Disappointing performance: 5-disk RAID6, 3.11.6
- From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
- Re: Manually reconstruct a RAID10 from adaptec 3805
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Disappointing performance: 5-disk RAID6, 3.11.6
- From: NeilBrown <neilb@xxxxxxx>
- Re: Disappointing performance: 5-disk RAID6, 3.11.6
- From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: [PATCH] Allow to check mdadm with clangs static checker (scan-build)
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: Mason Loring Bliss <mason@xxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Mark Knecht <markknecht@xxxxxxxxx>
- Re: Disappointing performance: 5-disk RAID6, 3.11.6
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
- Disappointing performance: 5-disk RAID6, 3.11.6
- From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
- Re: Very long raid5 init/rebuild times
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: request help with RAID1 array that endlessly attempts to sync
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Manually reconstruct a RAID10 from adaptec 3805
- From: Raul Dias <raul@xxxxxxxxxxx>
- Re: If separate md for /boot, OS, and /srv, must 'create' on disks with 3 partns?
- From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
- Very long raid5 init/rebuild times
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: Manually reconstruct a RAID10 from adaptec 3805
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: request help with RAID1 array that endlessly attempts to sync
- From: Julie Ashworth <ashworth@xxxxxxxxxxxx>
- Re: [PATCH] md/raid5: Add compensation in sysfs for raid456.
- From: NeilBrown <neilb@xxxxxxx>
- Re: MDADM 3.3 broken?
- From: "David F." <df7729@xxxxxxxxx>
- Re: [PATCH] Allow to check mdadm with clangs static checker (scan-build)
- From: NeilBrown <neilb@xxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
- Re: looking for advice on raid0+raid5 array recovery with mdadm and sector offset
- From: NeilBrown <neilb@xxxxxxx>
- Re: looking for advice on raid0+raid5 array recovery with mdadm and sector offset
- From: NeilBrown <neilb@xxxxxxx>
- Re: MDADM 3.3 broken?
- From: Martin Wilck <mwilck@xxxxxxxx>
- Re: Questions about bitrot and RAID 5/6
- From: NeilBrown <neilb@xxxxxxx>
- Re: looking for advice on raid0+raid5 array recovery with mdadm and sector offset
- From: den Hoog <speedyden@xxxxxxxxx>
- Questions about bitrot and RAID 5/6
- From: Mason Loring Bliss <mason@xxxxxxxxxxx>
- Manually reconstruct a RAID10 from adaptec 3805
- From: Raul Dias <raul@xxxxxxxxxxx>
- Re: [PATCH] raid6check.c add page size check and repair
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] raid6check.c add page size check and repair
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- Re: If separate md for /boot, OS, and /srv, must 'create' on disks with 3 partns?
- From: Ron Leach <ronleach@xxxxxxxxx>
- Re: If separate md for /boot, OS, and /srv, must 'create' on disks with 3 partns?
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: [BUG] at drivers/md/raid5.c:291! kernel 3.13-rc8
- From: Ian Kumlien <ian.kumlien@xxxxxxxxx>
- Re: [PATCH] raid6check.c add page size check and repair
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- Re: If separate md for /boot, OS, and /srv, must 'create' on disks with 3 partns?
- From: Ron Leach <ronleach@xxxxxxxxx>
- [PATCH] Allow to check mdadm with clangs static checker (scan-build)
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
- Re: [PATCH] raid6check.c add page size check and repair
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
- Re: [BUG] at drivers/md/raid5.c:291! kernel 3.13-rc8
- From: Ian Kumlien <ian.kumlien@xxxxxxxxx>
- Re: looking for advice on raid0+raid5 array recovery with mdadm and sector offset
- From: NeilBrown <neilb@xxxxxxx>
- Re: MDADM 3.3 broken?
- From: NeilBrown <neilb@xxxxxxx>
- Re: [BUG] at drivers/md/raid5.c:291! kernel 3.13-rc8
- From: NeilBrown <neilb@xxxxxxx>
- Re: [BUG] at drivers/md/raid5.c:291! kernel 3.13-rc8
- From: Ian Kumlien <ian.kumlien@xxxxxxxxx>
- Re: [BUG] at drivers/md/raid5.c:291! kernel 3.13-rc8
- From: NeilBrown <neilb@xxxxxxx>
- Re: [BUG] at drivers/md/raid5.c:291! kernel 3.13-rc8
- From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
- [BUG] at drivers/md/raid5.c:291! kernel 3.13-rc8
- From: Ian Kumlien <ian.kumlien@xxxxxxxxx>
- Re: If separate md for /boot, OS, and /srv, must 'create' on disks with 3 partns?
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: If separate md for /boot, OS, and /srv, must 'create' on disks with 3 partns?
- From: Phil Turmel <philip@xxxxxxxxxx>
- If separate md for /boot, OS, and /srv, must 'create' on disks with 3 partns?
- From: Ron Leach <ronleach@xxxxxxxxx>
- Re: Raid recovery - raid5 - one active, two spares
- From: Mariusz Zalewski <mariusz@xxxxxxxxxxx>
- Re: problems with block sizes in raid 5
- From: Martin Bruse <zondolfin@xxxxxxxxx>
- [PATCH] raid6check.c add page size check and repair
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- problems with block sizes in raid 5
- From: Martin Bruse <zondolfin@xxxxxxxxx>
- Re: Raid recovery - raid5 - one active, two spares
- From: Phil Turmel <philip@xxxxxxxxxx>
- Raid recovery - raid5 - one active, two spares
- From: Mariusz Zalewski <mariusz@xxxxxxxxxxx>
- Re: looking for advice on raid0+raid5 array recovery with mdadm and sector offset
- From: den Hoog <speedyden@xxxxxxxxx>
- Re: read errors not corrected when doing check on RAID6
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: read errors not corrected when doing check on RAID6
- From: NeilBrown <neilb@xxxxxxx>
- Re: Bitmap does not account for write errors prior to kicking?
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH] md: check command validity early in md_ioctl().
- From: NeilBrown <neilb@xxxxxxx>
- Re: Bitmap does not account for write errors prior to kicking?
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
- Re: Bitmap does not account for write errors prior to kicking?
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- [PATCH] md: check command validity early in md_ioctl().
- From: Nicolas Schichan <nschichan@xxxxxxxxxx>
- Bitmap does not account for write errors prior to kicking?
- From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
[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]