Linux RAID Storage Date Index

• Thread Index

• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: with raid-6 any writes access all disks
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: keld@xxxxxxxxxx
• Re: possibly silly question (raid failover)
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• [md PATCH 1/1] add display of hours remaining to finish resync
  • From: Krzysztof Adamski <k@xxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: [PATCH 19/19] make_parts(): Avoid false positive security warning
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• [PATCH 09/19] Detail(): Remember to free 'avail'
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 14/19] Managa_ro(): free() mdi before exiting
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 12/19] Manage_subdevs(): avoid leaking super
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 19/19] make_parts(): Avoid false positive security warning
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 18/19] validate_geometry_imsm_volume(): Avoid NULL pointer dereference
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 17/19] bitmap_fd_read(): fix memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 15/19] Manage_runstop(): Avoid memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 16/19] Monitor(): free allocated memory on exit
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 10/19] Grow_reshape(): Fix another 'sra' leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 06/19] assemble_container_content(): fix memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 13/19] IncrementalScan(): Fix memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 11/19] enough_fd(): remember to free buffer for avail array
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 03/19] Incremental(): Check return value of dev_open() before trying to use it
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 07/19] Grow_restart(): free() offsets after use
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 08/19] Assemble(): don't dup_super() before we need it.
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 02/19] Grow_addbitmap(): don't try to close a file descriptor which failed to open
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 05/19] remove_devices(): readlink returns -1 on error
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 04/19] sysfs_unique_holder(): Check read() return value before using as buffer index
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 00/19] More fixes for resource leaks and warnings
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 01/19] Grow_Add_device(): dev_open() return a negative fd on error
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: possibly silly question (raid failover)
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/3] conf_match(): Remove dead code
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 00/11] Memory/resource leaks and unchecked return fixes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/3] conf_match(): Remove dead code
  • From: NeilBrown <neilb@xxxxxxx>
• possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: raid(1) and block caching
  • From: CoolCold <coolthecold@xxxxxxxxx>
• RE: [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 11/11] mdmon(): Error out if failing to connect to victim monitor
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 10/11] Write_rules(): Avoid stack corruption if using extremely long udev pathname
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 09/11] policy_add(): Add missing va_end()
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 08/11] Avoid memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 07/11] Add missing return in case of trying to grow sub-array
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 06/11] Fix memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 05/11] partition_try_spare() use closedir() to release DIR * returned by opendir()
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 04/11] Fix memory leak of 'st3' in array_try_spare()
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 03/11] Fix memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 02/11] Fix memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 01/11] Fix memory leaks in reshape_array()
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 00/11] Memory/resource leaks and unchecked return fixes
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 3/3] Kill(): Remove redundant check and dead code
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 1/3] conf_match(): Remove dead code
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 2/3] conf_watch(): More dead code removal
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/3] Remove dead code
  • From: Jes.Sorensen@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: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [PATCH 1/2] Avoid use after free
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] Avoid use after free
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Unable to restart reshape
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Unable to restart reshape
  • From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
• Re: Unable to restart reshape
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Unable to restart reshape
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Unable to restart reshape
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Unable to restart reshape
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Unable to restart reshape
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: raid(1) and block caching
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: raid(1) and block caching
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: raid(1) and block caching
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid(1) and block caching
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• raid(1) and block caching
  • From: CoolCold <coolthecold@xxxxxxxxx>
• [PATCH 2/2] Avoid stack overflow if GPT partition entries on disk are > 128 bytes
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 1/2] Avoid use after free
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/2] Misc fixes
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• Re: Lost mdadm RAID6 array and tried everything, hoping for any other suggestions you may have
  • From: Ryan Castellucci <ryan.castellucci+linux-raid@xxxxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: "Peter W. Morreale" <morreale@xxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Auto-assembling RAID6 over RAID0?
  • From: Michał Sawicz <michal@xxxxxxxxxx>
• Auto-assembling RAID6 over RAID0?
  • From: Michał Sawicz <michal@xxxxxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: "Peter W. Morreale" <morreale@xxxxxxx>
• Re: with raid-6 any writes access all disks
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: with raid-6 any writes access all disks
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: with raid-6 any writes access all disks
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [PATCH] GCC compile fix: remove calculation of unused variable 'reservation'
  • From: NeilBrown <neilb@xxxxxxx>
• RE: [PATCH] GCC compile fix: remove calculation of unused variable 'reservation'
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• Re: [PATCH 00/13] Add missing handling of malloc() failure
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH] FIX: Close unused handle in child process during reshape restart
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 00/13] Add missing handling of malloc() failure
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] GCC compile fix: remove calculation of unused variable 'reservation'
  • From: NeilBrown <neilb@xxxxxxx>
• Re: with raid-6 any writes access all disks
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: with raid-6 any writes access all disks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: with raid-6 any writes access all disks
  • From: "Peter W. Morreale" <morreale@xxxxxxx>
• with raid-6 any writes access all disks
  • From: Chris Pearson <kermit4@xxxxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• [PATCH 07/13] Fix malloc() failure handling in Monitor.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 05/13] Handle malloc() failure in Examine.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 13/13] Catch malloc() failure
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 10/13] Handle malloc() failure in Grow.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 12/13] Handle malloc() failure in mdstat.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 11/13] Handle malloc() failure in mdopen.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 09/13] Fix malloc handling in dlink.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 08/13] Handle malloc() failures in devline()
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 06/13] Handle malloc() errors in Manage.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 04/13] Attempt to catch malloc() failure in Detail.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 03/13] Try to catch malloc() failures in Assemble.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 02/13] Catch malloc() failures
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 01/13] count_active() catch malloc() failure
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 00/13] Add missing handling of malloc() failure
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH] FIX: Close unused handle in child process during reshape restart
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: "Peter W. Morreale" <morreale@xxxxxxx>
• Re: [PATCH] GCC compile fix: remove calculation of unused variable 'reservation'
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• [md PATCH 16/16] md/raid5: Mark device replaceable when we see a write error.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 15/16] md/raid5: If there is a spare and a replaceable device, start replacement.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 14/16] md/raid5: recognise replacements when assembling array.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 13/16] md/raid5: handle activation of replacement device when recovery completes.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 12/16] md/raid5: detect and handle replacements during recovery.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 11/16] md/raid5: writes should get directed to replacement as well as original.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 10/16] md/raid5: allow removal for failed replacement devices.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 09/16] md/raid5: preferentially read from replacement device if possible.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 08/16] md/raid5: remove redundant bio initialisations.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 07/16] md/raid5: raid5.h cleanup
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 06/16] md/raid5: allow each slot to have an extra replacement device
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 05/16] md: create externally visible flags for supporting hot-replace.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 04/16] md: change hot_remove_disk to take an rdev rather than a number.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 03/16] md: remove test for duplicate device when setting slot number.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 02/16] md: take after reference to mddev during sysfs access.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 01/16] md: refine interpretation of "hold_active == UNTIL_IOCTL".
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: NeilBrown <neilb@xxxxxxx>
• PULL REQUEST md updates for 3.2
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] util.c: two typos fixed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Rotating RAID 1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm r/w operations without TEMP_FAILURE_RETRY()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm r/w operations without TEMP_FAILURE_RETRY()
  • From: Michal Soltys <soltys@xxxxxxxx>
• [PATCH] util.c: two typos fixed
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: Rotating RAID 1
  • From: linbloke <linbloke@xxxxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bad block management - which mdadm?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: NeilBrown <neilb@xxxxxxx>
• Bad block management - which mdadm?
  • From: Arkadiusz Miśkiewicz <a.miskiewicz@xxxxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Converting from Raid 5 to 6
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Advice on build a RAID6
  • From: Krzysztof Adamski <k@xxxxxxxxxxx>
• Re: Advice on build a RAID6
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [PATCH 1/3] Remove race for starting container devices.
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 0/2] Fixes metadata while migrating from Raid 0 to Raid 10
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/3] Remove race for starting container devices.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: How to free devices held captive by failed arrays
  • From: Harry Mangalam <hjm@xxxxxxxxxxxxxxx>
• Re: How to free devices held captive by failed arrays
  • From: NeilBrown <neilb@xxxxxxx>
• Re: How to free devices held captive by failed arrays
  • From: Harry Mangalam <hjm@xxxxxxxxxxxxxxx>
• Re: How to free devices held captive by failed arrays
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm "Used Dev Size" on 3TB drives
  • From: NeilBrown <neilb@xxxxxxx>
• Advice on build a RAID6
  • From: Krzysztof Adamski <k@xxxxxxxxxxx>
• How to free devices held captive by failed arrays
  • From: Harry Mangalam <hjm@xxxxxxxxxxxxxxx>
• [PATCH 1/1] Incremental() lock error handling
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/1] Incremental() additional locking fixes
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 1/2] Create() don't leave the lock hanging on error
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 2/2] Create() check malloc() return value
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH] array_try_spare(): missing map_unlock()
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 3/3] Hold the map lock while performing Assemble to avoid races with udev
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 2/3] Don't tell sysfs to launch the container as we are doing it ourselves
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 1/3] Remove race for starting container devices.
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH v2 0/3] Fix mdadm vs udev race in Incremental and Assemble
  • From: Jes.Sorensen@xxxxxxxxxx
• mdadm "Used Dev Size" on 3TB drives
  • From: Andrew <andyukguy@xxxxxxxxx>
• [PATCH 2/2] imsm: fix: Fixes metadata after migration from Raid 0 to Raid 10
  • From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
• [PATCH 1/2] imsm: Moves metadata update code for spare activation to separate function
  • From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
• [PATCH 0/2] Fixes metadata while migrating from Raid 0 to Raid 10
  • From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
• [PATCH 1/3] Remove race for starting container devices.
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 3/3] Hold the map lock while performing Assemble to avoid races with udev
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/3] Fix mdadm vs udev race in Incremental and Assemble
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 2/3] Don't tell sysfs to launch the container as we are doing it ourselves
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: mdadm help
  • From: Yathindra <ydev@xxxxxxxxxxx>
• Re: mdadm help
  • From: NeilBrown <neilb@xxxxxxx>
• mdadm help
  • From: Yathindra <ydev@xxxxxxxxxxx>
• Re: [PATCH] imsm: fix: prevent segfault in mark_failure
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] lib/raid6: Fix filename emitted in generated code
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] imsm: fix: correct debug printing of the volume's name
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• [PATCH] imsm: fix: prevent segfault in mark_failure
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: [PATCH] md.c: trivial comment fix
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md.c: trivial comment fix
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• Re: [PATCH] MD: Allow restarting an interrupted incremental recovery.
  • From: Andrei Warkentin <awarkentin@xxxxxxxxxx>
• Re: [PATCH] MD: Allow restarting an interrupted incremental recovery.
  • From: NeilBrown <neilb@xxxxxxx>
• Working TRIM for md RAID
  • From: Alex Besogonov <alex.besogonov@xxxxxxxxx>
• Re: [PATCH] MD: Allow restarting an interrupted incremental recovery.
  • From: Andrei Warkentin <awarkentin@xxxxxxxxxx>
• Re: [PATCH] MD: Allow restarting an interrupted incremental recovery.
  • From: Andrei Warkentin <awarkentin@xxxxxxxxxx>
• Re: [PATCH] MD: Allow restarting an interrupted incremental recovery.
  • From: Andrei Warkentin <awarkentin@xxxxxxxxxx>
• RE: [PATCH] fix: imsm: prevent segfault in mark_failure
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: mdadm r/w operations without TEMP_FAILURE_RETRY()
  • From: NeilBrown <neilb@xxxxxxx>
• FW: mdadm r/w operations without TEMP_FAILURE_RETRY()
  • From: "Orlowski, Lukasz" <lukasz.orlowski@xxxxxxxxx>
• [PATCH] fix: imsm: prevent segfault in mark_failure
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: [PATCH 0/1] IMSM do not assume prev + current map in same state means reshape
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• RE: [PATCH 0/1] IMSM do not assume prev + current map in same state means reshape
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: [PATCH] MD: Allow restarting an interrupted incremental recovery.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] MD: Allow restarting an interrupted incremental recovery.
  • From: Andrei Warkentin <andreiw@xxxxxxxxxx>
• Re: [RFC] MD: Allow restarting an interrupted incremental recovery.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 1/1] IMSM only run reshape if number of disks has changed
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/1] IMSM do not assume prev + current map in same state means reshape
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH] lib/raid6: Fix filename emitted in generated code
  • From: Dan McGee <dpmcgee@xxxxxxxxx>
• Re: [RFC] MD: Allow restarting an interrupted incremental recovery.
  • From: Andrei Warkentin <awarkentin@xxxxxxxxxx>
• Potential data rollback/corruption after drive failure and re-appearance
  • From: "Moshe Melnikov" <moshe@xxxxxxxxxxxxxxxxx>
• Re: [RFC] MD: Allow restarting an interrupted incremental recovery.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [mdadm PATCH 2/2] Fix unterminated buffer after readlink() call
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Data recovery from linear array (Intel SS4000-E)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Data recovery from linear array (Intel SS4000-E)
  • From: Johannes Moos <jmoos@xxxxxx>
• Re: Data recovery from linear array (Intel SS4000-E)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Data recovery from linear array (Intel SS4000-E)
  • From: Johannes Moos <jmoos@xxxxxx>
• Re: Data recovery from linear array (Intel SS4000-E)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Data recovery from linear array (Intel SS4000-E)
  • From: Johannes Moos <jmoos@xxxxxx>
• 2 drive RAID10 rebuild issue
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: [RFC] MD: Allow restarting an interrupted incremental recovery.
  • From: "Andrei E. Warkentin" <andrey.warkentin@xxxxxxxxx>
• Re: [RFC] MD: Restart an interrupted incremental recovery.
  • From: "Andrei E. Warkentin" <andrey.warkentin@xxxxxxxxx>
• Re: Data recovery from linear array (Intel SS4000-E)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Data recovery from linear array (Intel SS4000-E)
  • From: Johannes Moos <jmoos@xxxxxx>
• [mdadm PATCH 2/2] Fix unterminated buffer after readlink() call
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• [mdadm PATCH 1/2] Fix off-by-one in readlink() buffer size handling
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• mdadm --grow on raid1 returns nonzero
  • From: Kevin W Monroe <kwmonroe@xxxxxxxxxxxxxxxxxx>
• [RFC] MD: Allow restarting an interrupted incremental recovery.
  • From: Andrei Warkentin <andreiw@xxxxxxxxxx>
• Re: [RFC] MD: Restart an interrupted incremental recovery.
  • From: "Andrei E. Warkentin" <andrey.warkentin@xxxxxxxxx>
• Re: Odd booting problem
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: Odd booting problem
  • From: maurice <mhilarius@xxxxxxxxx>
• [RFC] MD: Restart an interrupted incremental recovery.
  • From: Andrei Warkentin <andreiw@xxxxxxxxxx>
• Re: some general md raid questions
  • From: "Peter W. Morreale" <morreale@xxxxxxx>
• Re: some general md raid questions
  • From: Keith Keller <kkeller-usenet@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: 1.X metadata: Resuming an interrupted incremental recovery for RAID1.
  • From: "Andrei E. Warkentin" <andrey.warkentin@xxxxxxxxx>
• Re: Raid5 to another raid level??
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• some general md raid questions
  • From: "Peter W. Morreale" <morreale@xxxxxxx>
• Re: Raid5 to another raid level??
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 to another raid level??
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: 1.X metadata: Resuming an interrupted incremental recovery for RAID1.
  • From: "Andrei E. Warkentin" <andrey.warkentin@xxxxxxxxx>
• Re: Raid5 to another raid level??
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 1.X metadata: Resuming an interrupted incremental recovery for RAID1.
  • From: NeilBrown <neilb@xxxxxxx>
• 1.X metadata: Resuming an interrupted incremental recovery for RAID1.
  • From: "Andrei E. Warkentin" <andrey.warkentin@xxxxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Odd booting problem
  • From: maurice <mhilarius@xxxxxxxxx>
• Re: md RAID10 questions
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: md RAID10 questions
  • From: keld@xxxxxxxxxx
• Re: Raid5 to another raid level??
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• md RAID10 questions
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: Odd booting problem
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: Odd booting problem
  • From: Jim Schatzman <james.schatzman@xxxxxxxxxxxxxxxx>
• Re: Odd booting problem
  • From: maurice <mhilarius@xxxxxxxxx>
• configuration questions & advice
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: Thought about delayed sync
  • From: NeilBrown <neilb@xxxxxxx>
• BUG: spinlock lockup while performing FS operations and detected stalls on CPUs / tasks.
  • From: Валерий <paramonov@xxxxxxxxx>
• Re: Thought about delayed sync
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: Thought about delayed sync
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Thought about delayed sync
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: Thought about delayed sync
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: Thought about delayed sync
  • From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
• Re: Thought about delayed sync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Thought about delayed sync
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Thought about delayed sync
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: BUG: spinlock lockup while performing FS operations and detected stalls on CPUs / tasks.
  • From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
• BUG: spinlock lockup while performing FS operations and detected stalls on CPUs / tasks.
  • From: Валерий <paramonov@xxxxxxxxx>
• Odd booting problem
  • From: maurice <mhilarius@xxxxxxxxx>
• Re: BUG: spinlock lockup while performing FS operations
  • From: NeilBrown <neilb@xxxxxxx>
• Re: BUG: spinlock lockup while performing FS operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Clarification behind md 1.0 superblock resync_offset and recovery_offset?
  • From: NeilBrown <neilb@xxxxxxx>
• Clarification behind md 1.0 superblock resync_offset and recovery_offset?
  • From: "Andrei E. Warkentin" <andrey.warkentin@xxxxxxxxx>
• [PATCH] GCC compile fix: remove calculation of unused variable 'reservation'
  • From: Jes.Sorensen@xxxxxxxxxx
• BUG: spinlock lockup while performing FS operations
  • From: Валерий <paramonov@xxxxxxxxx>
• [PATCH] Always run Grow_continue() for started array.
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PULLREQUEST] md bugfix for 3.1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/3] Always run Grow_continue() for started array.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: always use set_migr_type to set type of migration
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Creating an md with 3TB drives.
  • From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
• Re: Creating an md with 3TB drives.
  • From: Sebastian Muniz <sjmuniz@xxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• RE: Does Linux support Intel Smart Response Technology?
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH] imsm: always use set_migr_type to set type of migration
  • From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• RE: [PATCH 1/3] Always run Grow_continue() for started array.
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Does Linux support Intel Smart Response Technology?
  • From: "linux-raid" <linux-raid@xxxxxxxxxxxxxxxx>
• Appropriate kernel group for IDE/ATA/SAS/SATA issues?
  • From: Jim Schatzman <james.schatzman@xxxxxxxxxxxxxxxx>
• Re: Does Linux support Intel Smart Response Technology?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Does Linux support Intel Smart Response Technology?
  • From: "Guy Watkins" <Guy@xxxxxxxxxxxxxxxx>
• Re: [PATCH] imsm: fix: correct adding and activation of spare disks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/3] Set correct reshape restart position
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/3] Monitor reshaped array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/3] Always run Grow_continue() for started array.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/4] Fix freezing multiple arrays in container during assembly (2)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/4] FIX: restore_backup() throws core dump
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: NeilBrown <neilb@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: NeilBrown <neilb@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm - level change from raid 1 to raid 5
  • From: NeilBrown <neilb@xxxxxxx>
• RE: MD sets failing under heavy load in a DRBD/Pacemaker Cluster (115893302)
  • From: Support <support@xxxxxxx>
• Re: MD sets failing under heavy load in a DRBD/Pacemaker Cluster
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• RE: MD sets failing under heavy load in a DRBD/Pacemaker Cluster
  • From: "Thakkar, Vishal" <Vishal.Thakkar@xxxxxxx>
• [PATCH] imsm: fix: correct adding and activation of spare disks
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• [PATCH 3/3] Set correct reshape restart position
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/3] Monitor reshaped array
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/3] Reshape restart after file system pivot (missing part)
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/3] Always run Grow_continue() for started array.
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: MD sets failing under heavy load in a DRBD/Pacemaker Cluster
  • From: CoolCold <coolthecold@xxxxxxxxx>
• MD sets failing under heavy load in a DRBD/Pacemaker Cluster
  • From: Caspar Smit <c.smit@xxxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: maurice <mhilarius@xxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• [PATCH 4/4] Remove freeze() call from Grow_continue()
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 3/4] imsm: Fill recovery_blocked field present in mdinfo
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/4] Add recovery blocked field to mdinfo
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/4] FIX: restore_backup() throws core dump
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/4] Fix freezing multiple arrays in container during assembly (2)
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• How to stress test an RAID 6 array?
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: mdadm - level change from raid 1 to raid 5
  • From: Dominique <dcouot@xxxxxxxxxxx>
• Re: mdadm - level change from raid 1 to raid 5
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: mdadm - level change from raid 1 to raid 5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm - level change from raid 1 to raid 5
  • From: Dominique <dcouot@xxxxxxxxxxx>
• Re: [PATCH 3/3] FIX: Remove error message during reshape restart (v2)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/3] FIX: Block array monitoring if any array is under reshape in container
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/3] Move code to check_mdmon_version() function
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] imsm: Do not mark resync during reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] imsm: FIX: Do not allow for spare disk activation during reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 8/8] Manual update for --continue option
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 6/8] Verify reshape restart position
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 5/8] Move code to get_data_disks() function
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 4/8] Set correct reshape restart position
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/8] Do not restart reshape if it is started already
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/8] Add continue option to grow command
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/8] Do not continue reshape during initrd phase
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] fix: correct unlocking of map file
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [mdadm PATCH] Fix small memory leak
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm - level change from raid 1 to raid 5
  • From: NeilBrown <neilb@xxxxxxx>
• [mdadm PATCH] Fix small memory leak
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• Re: Linux raid autodetect partition disappears after RAID degrade
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Aapo Laine <aapo.laine@xxxxxxxxxxxxx>
• Re: mdadm - level change from raid 1 to raid 5
  • From: Dominique <dcouot@xxxxxxxxxxx>
• Linux raid autodetect partition disappears after RAID degrade
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Aapo Laine <aapo.laine@xxxxxxxxxxxxx>
• Re: Safely swapping a disk in a RAID456
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: Safely swapping a disk in a RAID456
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Safely swapping a disk in a RAID456
  • From: Asdo <asdo@xxxxxxxxxxxxx>
• Re: Safely swapping a disk in a RAID456
  • From: Danny Rawlins <monster.romster@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: mdadm - level change from raid 1 to raid 5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• mdadm - level change from raid 1 to raid 5
  • From: Dominique <dcouot@xxxxxxxxxxx>
• Re: Safely swapping a disk in a RAID456
  • From: John Robinson <john.robinson@xxxxxxxxxxx>
• Re: Safely swapping a disk in a RAID456
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: Safely swapping a disk in a RAID456
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: Safely swapping a disk in a RAID456
  • From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Safely swapping a disk in a RAID456
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Re: RAID1 question
  • From: William Thompson <wt@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID1 question
  • From: William Thompson <wt@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID1 question
  • From: Kai Stian Olstad <kai.stian.olstad@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID1 question
  • From: Robin Hill <robin.hill47@xxxxxxxxxxxx>
• Re: RAID1 question
  • From: William Thompson <wt@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID1 question
  • From: Robin Hill <robin.hill47@xxxxxxxxxxxx>
• RAID1 question
  • From: William Thompson <wt@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PATCH 3/3] FIX: Remove error message during reshape restart (v2)
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/3] FIX: Block array monitoring if any array is under reshape in container
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/3] Move code to check_mdmon_version() function
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/3] Fix freezing multiple array in container during assembly
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/2] imsm: Do not mark resync during reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/2] imsm: FIX: Do not allow for spare disk activation during reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/2] Do not allow for resync during reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: Creating an md with 3TB drives.
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Creating an md with 3TB drives.
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Creating an md with 3TB drives.
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• [PATCH] fix: correct unlocking of map file
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: error injection
  • From: NeilBrown <neilb@xxxxxxx>
• Re: error injection
  • From: Jojy Varghese <jojy.varghese@xxxxxxxxx>
• Re: error injection
  • From: NeilBrown <neilb@xxxxxxx>
• Re: error injection
  • From: Jojy Varghese <jojy.varghese@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: NeilBrown <neilb@xxxxxxx>
• Re: error injection
  • From: NeilBrown <neilb@xxxxxxx>
• error injection
  • From: Jojy Varghese <jojy.varghese@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Creating an md with 3TB drives.
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: Creating an md with 3TB drives.
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Creating an md with 3TB drives.
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Creating an md with 3TB drives.
  • From: NeilBrown <neilb@xxxxxxx>
• Creating an md with 3TB drives.
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: RAID6 issues
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: RAID6 issues
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: RAID6 issues
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID6 issues
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 issues
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: RAID6 issues
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: RAID6 issues
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• [PATCH 6/8] Verify reshape restart position
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 8/8] Manual update for --continue option
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 7/8] Manual update for --continue option
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 5/8] Move code to get_data_disks() function
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 4/8] Set correct reshape restart position
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 3/8] Do not restart reshape if it is started already
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/8] Add continue option to grow command
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/8] Do not continue reshape during initrd phase
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/8] Reshape restart after filesystem pivot
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: Recovering from a Bad Resilver / Rebuild
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Best strategy to incrementally replace smaller HDDs [success story]
  • From: Michał Sawicz <michal@xxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Recovering from a Bad Resilver / Rebuild
  • From: "Kenn" <kenn@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Krzysztof Adamski <k@xxxxxxxxxxx>
• Re:
  • From: "Kenn" <kenn@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re:
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re:
  • From: "Kenn" <kenn@xxxxxxx>
• Re: Green drives and RAID arrays with partity
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PATCH] imsm: fix: stopped resync does not continue after auto-assemblation
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• [PATCH] remove unused variable
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: NeilBrown <neilb@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: examining the layout of an existing raid device?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: examining the layout of an existing raid device?
  • From: NeilBrown <neilb@xxxxxxx>
• examining the layout of an existing raid device?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: NeilBrown <neilb@xxxxxxx>
• Re:
  • From: NeilBrown <neilb@xxxxxxx>
• Re:
  • From: "Kenn" <kenn@xxxxxxx>
• Re:
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Recovering from a Bad Resilver?
  • From: "Kenn" <kenn@xxxxxxx>
• Re:
  • From: NeilBrown <neilb@xxxxxxx>
• [no subject]
  • From: "Kenn" <kenn@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Krzysztof Adamski <k@xxxxxxxxxxx>
• Re: Green drives and RAID arrays with partity
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Green drives and RAID arrays with partity
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Green drives and RAID arrays with partity
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: NeilBrown <neilb@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Green drives and RAID arrays with partity
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Green drives and RAID arrays with partity
  • From: Joe Landman <landman@xxxxxxxxxxxxxxxxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Green drives and RAID arrays with partity
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Green drives and RAID arrays with partity
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Green drives and RAID arrays with partity
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Green drives and RAID arrays with partity
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: NeilBrown <neilb@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: NeilBrown <neilb@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Kristleifur Daðason <kristleifur@xxxxxxxxx>
• Re: Recovery of failed RAID 6 and LVM
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Recovery of failed RAID 6 and LVM
  • From: "Marcin M. Jessa" <lists@xxxxxxxxx>
• Re: Can reading a raid drive trigger all the other drives in that set?
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: Recovering failed array
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Aapo Laine <aapo.laine@xxxxxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] md: don't delay reboot by 1 second if no MD devices exist
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md: don't delay reboot by 1 second if no MD devices exist
  • From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: NeilBrown <neilb@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: NeilBrown <neilb@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Lost mdadm RAID6 array and tried everything, hoping for any other suggestions you may have
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID1 with MBR and GPT fails to auto-assemble during boot - repost
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovering failed array
  • From: NeilBrown <neilb@xxxxxxx>
• potentially lost largeish raid5 array..
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: Recovering failed array
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Lost mdadm RAID6 array and tried everything, hoping for any other suggestions you may have
  • From: Eduard Rozenberg <eduardr@xxxxxxxxx>
• Re: RAID1 with MBR and GPT fails to auto-assemble during boot - repost
  • From: Jim Schatzman <james.schatzman@xxxxxxxxxxxxxxxx>
• Re: Recovering failed array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Recovering failed array
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: Changed the SATA ports of two disks in RAID10 and raid disappeared
  • From: Piotr Legiecki <piotrlg@xxxxxxxxxx>
• [PATCH] FIX: restore_backup() throws core dump
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: Changed the SATA ports of two disks in RAID10 and raid disappeared
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Changed the SATA ports of two disks in RAID10 and raid disappeared
  • From: Piotr Legiecki <piotrlg@xxxxxxxxxx>
• RE: [PATCH] FIX: Remove error message during reshape restart
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: [PATCH] FIX: Remove error message during reshape restart
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 13/14] Check if md allows to control reshape
  • From: NeilBrown <neilb@xxxxxxx>
• RE: [PATCH 04/14] Add continue option to grow command
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• RE: [PATCH 08/14] Check if reshape can be restarted
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• RE: [PATCH 10/14] Perform restore backup for reshape continuation
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• RE: [PATCH 12/14] Early reshape backup verification
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• RE: [PATCH 13/14] Check if md allows to control reshape
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: making a hot spare ... hot
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• RE: [PATCH] FIX: Remove error message during reshape restart
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: making a hot spare ... hot
  • From: Brendan Hide <brendan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] Create: Allow to create two volumes of different sizes within one container
  • From: NeilBrown <neilb@xxxxxxx>
• 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] imsm: FIX: Spare disk has wrong serial after takeover
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: Kernel OOPs after RAID10 assemble
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm/Monitor.c - never removes MD devices from statelist
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 5/9] imsm: fix reserved sectors for spares
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Fixed: Part of output missing during RAID creation
  • From: NeilBrown <neilb@xxxxxxx>
• Re: making a hot spare ... hot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/3] Create: Incorrect message when creating a volume with explicit md dev name
  • From: NeilBrown <neilb@xxxxxxx>
• making a hot spare ... hot
  • From: Brendan Hide <brendan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] Create: Unnecessary prompt about device being busy
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/3] Create: Allow to create two volumes of different sizes within one container
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] FIX: Remove error message during reshape restart
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 13/14] Check if md allows to control reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 12/14] Early reshape backup verification
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 10/14] Perform restore backup for reshape continuation
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 09/14] Move restore backup code to function
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 08/14] Check if reshape can be restarted
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 07/14] FIX: Memory leak during Assembly
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 04/14] Add continue option to grow command
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 03/14] FIX: Do not unblock array accidentally
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] Fixed: Part of output missing during RAID creation
  • From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
• [PATCH] Fixed: Part of output missing during RAID creation
  • From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
• Re: RAID showing all devices as spares after partial unplug
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID1 with MBR and GPT fails to auto-assemble during boot
  • From: Jim Schatzman <james.schatzman@xxxxxxxxxxxxxxxx>
• Re: [Patch mdadm-3.2.2] Fix readding of a readwrite drive into a writemostly array
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• [PATCH 3/3] Create: Incorrect message when creating a volume with explicit md dev name
  • From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
• [PATCH 2/3] Create: Unnecessary prompt about device being busy
  • From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
• [PATCH 1/3] Create: Allow to create two volumes of different sizes within one container
  • From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
• [PATCH 0/3] Series short description
  • From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
• Changed the SATA ports of two disks in RAID10 and raid disappeared
  • From: Piotr Legiecki <piotrlg@xxxxxxxxxx>
• RE: [PATCH 5/9] imsm: fix reserved sectors for spares
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• RE: [PATCH 01/14] Stop array reshape when mounted initramfs is detected
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: [PATCH 01/14] Stop array reshape when mounted initramfs is detected
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] udev rules: use $tempnode, check for supported types, comments
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: [PATCH] FIX: Cannot continue reshape if incremental assembly is used
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Fix serious memory leak
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: FIX: Spare disk has wrong serial after takeover
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] udev rules: use $tempnode, check for supported types, comments
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [Patch mdadm-3.2.2] Fix readding of a readwrite drive into a writemostly array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [Patch mdadm-3.2.2] Fix the fix for the readd bug
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Need pointers to shrinking an array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID showing all devices as spares after partial unplug
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID showing all devices as spares after partial unplug
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID showing all devices as spares after partial unplug
  • From: Mike Hartman <mike@xxxxxxxxxxxxxxxxxxxx>
• Need pointers to shrinking an array
  • From: Michał Sawicz <michal@xxxxxxxxxx>
• Re: RAID showing all devices as spares after partial unplug
  • From: Phil Turmel <philip@xxxxxxxxxx>
• RE: RAID showing all devices as spares after partial unplug
  • From: Mike Hartman <mike@xxxxxxxxxxxxxxxxxxxx>
• Re: RAID showing all devices as spares after partial unplug
  • From: Mike Hartman <mike@xxxxxxxxxxxxxxxxxxxx>
• Re: RAID showing all devices as spares after partial unplug
  • From: Jim Schatzman <james.schatzman@xxxxxxxxxxxxxxxx>
• Re: RAID showing all devices as spares after partial unplug
  • From: Mike Hartman <mike@xxxxxxxxxxxxxxxxxxxx>
• Re: RAID showing all devices as spares after partial unplug
  • From: Jim Schatzman <james.schatzman@xxxxxxxxxxxxxxxx>
• Re: RAID showing all devices as spares after partial unplug
  • From: Mike Hartman <mike@xxxxxxxxxxxxxxxxxxxx>
• RAID showing all devices as spares after partial unplug
  • From: Mike Hartman <mike@xxxxxxxxxxxxxxxxxxxx>
• Re: additional feature for linear
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: additional feature for linear
  • From: Henti Smith <henti@xxxxxxxxxxxxxx>
• Re: additional feature for linear
  • From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
• Re: additional feature for linear
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• additional feature for linear
  • From: Henti Smith <henti@xxxxxxxxxxxxxx>
• Re: Converting RAID1 to RAID5
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Converting RAID1 to RAID5
  • From: Alex <mysqlstudent@xxxxxxxxx>
• [PATCH] FIX: Remove error message during reshape restart
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH] Fix serious memory leak
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• [PATCH 14/14] Manual update for --continue option
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 13/14] Check if md allows to control reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 12/14] Early reshape backup verification
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 11/14] Add possibility to restart reshape for native metadata
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 10/14] Perform restore backup for reshape continuation
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 09/14] Move restore backup code to function
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 08/14] Check if reshape can be restarted
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 07/14] FIX: Memory leak during Assembly
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 06/14] Check and run mdmon
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 05/14] Add Grow_continue_command
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 04/14] Add continue option to grow command
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 03/14] FIX: Do not unblock array accidentally
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 02/14] Stop container reshape while using initramfs
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 01/14] Stop array reshape when mounted initramfs is detected
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 00/14] Series short description
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: Converting RAID1 to RAID5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Converting RAID1 to RAID5
  • From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
• Re: Converting RAID1 to RAID5
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: Bootable Raid-1
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• [PATCH] imsm: FIX: Spare disk has wrong serial after takeover
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: [PATCH 3/2] block: refactor generic_make_request
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 3/2] block: refactor generic_make_request
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] block: export __make_request
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: [TuxOnIce-users] Repeatable md OOPS on suspend, 2.6.39.4 and 3.0.3
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [TuxOnIce-users] Repeatable md OOPS on suspend, 2.6.39.4 and 3.0.3
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [TuxOnIce-users] Repeatable md OOPS on suspend, 2.6.39.4 and 3.0.3
  • From: Nigel Cunningham <nigel@xxxxxxxxxxxx>
• Re: [TuxOnIce-users] Repeatable md OOPS on suspend, 2.6.39.4 and 3.0.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [TuxOnIce-users] Repeatable md OOPS on suspend, 2.6.39.4 and 3.0.3
  • From: Nigel Cunningham <nigel@xxxxxxxxxxxx>
• Re: [PATCH 1/2] block: export __make_request
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: [PATCH 1/2] block: export __make_request
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] block: export __make_request
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: [PATCH 1/2] block: export __make_request
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: What just happened to my disks/RAID5 array?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH 1/2] block: export __make_request
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: What just happened to my disks/RAID5 array?
  • From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] block: export __make_request
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: [PATCH 1/2] block: export __make_request
  • From: Boaz Harrosh <bharrosh@xxxxxxxxxxx>
• Re: What just happened to my disks/RAID5 array?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH 1/2] block: export __make_request
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: What just happened to my disks/RAID5 array?
  • From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
• Re: RAID6 issues
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 issues
  • From: Andriano <chief000@xxxxxxxxx>
• Re: What just happened to my disks/RAID5 array?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID6 issues
  • From: Andriano <chief000@xxxxxxxxx>
• Re: RAID6 issues
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: RAID6 issues
  • From: Andriano <chief000@xxxxxxxxx>
• Re: RAID6 issues
  • From: Andriano <chief000@xxxxxxxxx>
• Re: RAID6 issues
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• What just happened to my disks/RAID5 array?
  • From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
• Re: RAID6 issues
  • From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
• Re: RAID6 issues
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 issues
  • From: Andriano <chief000@xxxxxxxxx>
• Re: RAID6 issues
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 issues
  • From: Andriano <chief000@xxxxxxxxx>
• Re: RAID6 issues
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 issues
  • From: Andriano <chief000@xxxxxxxxx>
• Re: RAID6 issues
  • From: NeilBrown <neilb@xxxxxxx>
• RAID6 issues
  • From: Andriano <chief000@xxxxxxxxx>
• Re: Raid failing, which command to remove the bad drive?
  • From: "Timothy D. Lenz" <tlenz@xxxxxxxxxx>
• Re: [PATCH 1/2] block: export __make_request
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 3/2] block: refactor generic_make_request
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 3/2] block: refactor generic_make_request
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: Rotating RAID 1
  • From: Bill Davidsen <davidsen@xxxxxxx>
• [PATCH 3/2] block: refactor generic_make_request
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] block: export __make_request
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] block: export __make_request
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 2/2] block: remove support for bio remapping from ->make_request
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 2/2] block: remove support for bio remapping from ->make_request
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] block: export __make_request
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] block: remove support for bio remapping from ->make_request
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/2] block: export __make_request
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: mdadm/Monitor.c - never removes MD devices from statelist
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Kernel OOPs after RAID10 assemble
  • From: "Moshe Melnikov" <moshe@xxxxxxxxxxxxxxxxx>
• Re: Kernel OOPs after RAID10 assemble
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm/Monitor.c - never removes MD devices from statelist
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] block: remove support for bio remapping from ->make_request
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Rotating RAID 1
  • From: Pavel Hofman <pavel.hofman@xxxxxxxxxxx>
• mdadm/Monitor.c - never removes MD devices from statelist
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Speeding inode access
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid array with 3T disks and GPT partition
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Converting RAID1 to RAID5
  • From: Alex <mysqlstudent@xxxxxxxxx>
• [PATCH 2/2] block: remove support for bio remapping from ->make_request
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>