Linux RAID Storage Date Index

• Thread Index

• Re: quickest way for complex operation?
  • From: "Jens-U. Mozdzen" <jmozdzen@xxxxxx>
• Re: [PATCH] md/raid5: fix locking in handle_stripe_clean_event()
  • From: Roman Gushchin <klamm@xxxxxxxxxxxxxx>
• Advice requested
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• [GIT PULL REQUEST] last minute bug fixes for md.
  • From: Neil Brown <neilb@xxxxxxxx>
• Re: [PATCH] drivers/md/md.c: ignore recovery_offset if bitmap exists
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md/raid5: fix locking in handle_stripe_clean_event()
  • From: Neil Brown <neilb@xxxxxxx>
• Accidentally added as spare
  • From: Ian Radford <ian.c.radford@xxxxxxxxx>
• Re: Reconstruct a RAID 6 that has failed in a non typical manner
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: raid1 - mismatches after resuming interrupted recovery
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: raid1 - mismatches after resuming interrupted recovery
  • From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
• Re: [PATCH] md/raid5: fix locking in handle_stripe_clean_event()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: raid1 - mismatches after resuming interrupted recovery
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH] md/raid5: fix locking in handle_stripe_clean_event()
  • From: Roman Gushchin <klamm@xxxxxxxxxxxxxx>
• quickest way for complex operation?
  • From: "Jens-U. Mozdzen" <jmozdzen@xxxxxx>
• Re: [PATCH] drivers/md/md.c: ignore recovery_offset if bitmap exists
  • From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
• Re: Raid array name by mdadm
  • From: Anugraha Sinha <asinha.mailinglist@xxxxxxxxx>
• Re: [PATCH] [mdadm] add crc32c and use it for r5l checksum
  • From: Neil Brown <neilb@xxxxxxxx>
• Re: [PATCH] raid5-cache: use crc32c checksum
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] drivers/md/md.c: ignore recovery_offset if bitmap exists
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md/raid5: fix locking in handle_stripe_clean_event()
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md/raid5: fix locking in handle_stripe_clean_event()
  • From: Greg KH <greg@xxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Andras Tantos <andras@xxxxxxxxxxxxxxxx>
• Reconstruct a RAID 6 that has failed in a non typical manner
  • From: Clement Parisot <clement.parisot@xxxxxxxx>
• Re: [PATCH] md/raid5: fix locking in handle_stripe_clean_event()
  • From: Roman Gushchin <klamm@xxxxxxxxxxxxxx>
• Re: 2nd Faulty drive while rebuilding array on RAID5
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH] md/raid5: fix locking in handle_stripe_clean_event()
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] raid5-cache: use crc32c checksum
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: Raid array name by mdadm
  • From: Sheng Yang <sheng@xxxxxxxxxx>
• Re: Raid array name by mdadm
  • From: Sheng Yang <sheng@xxxxxxxxxx>
• Re: 2nd Faulty drive while rebuilding array on RAID5
  • From: Guillaume ALLEE <guillaume.allee@xxxxxxxxx>
• Re: Raid array name by mdadm
  • From: Dragan Milivojević <galileo@xxxxxxxxxxx>
• [PATCH] [mdadm] add crc32c and use it for r5l checksum
  • From: Song Liu <songliubraving@xxxxxx>
• Raid array name by mdadm
  • From: Sheng Yang <sheng@xxxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Andras Tantos <andras@xxxxxxxxxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Andras Tantos <andras@xxxxxxxxxxxxxxxx>
• Re: [PATCH] raid5-cache: use crc32c checksum
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: Replacing a RAID1 drive that has not failed.
  • From: Doug Herr <gmane@xxxxxxxxxxx>
• Re: [PATCH] raid5-cache: use crc32c checksum
  • From: Shaohua Li <shli@xxxxxx>
• Re: Converting 4 disk RAID10 to RAID5
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH] md/raid5: fix locking in handle_stripe_clean_event()
  • From: Roman Gushchin <klamm@xxxxxxxxxxxxxx>
• Re: Replacing a RAID1 drive that has not failed.
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Converting 4 disk RAID10 to RAID5
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• [PATCH] raid5-cache: use crc32c checksum
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH] md-cluster: Only one thread should request DLM lock
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: Replacing a RAID1 drive that has not failed.
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH] md-cluster: Only one thread should request DLM lock
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Replacing a RAID1 drive that has not failed.
  • From: Doug Herr <gmane@xxxxxxxxxxx>
• Re: [UU_] Won't go away
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [UU_] Won't go away
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: [UU_] Won't go away
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [UU_] Won't go away
  • From: Michael Munger <michael@xxxxxxxxxxxxxxxxxxx>
• Re: Converting 4 disk RAID10 to RAID5
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Converting 4 disk RAID10 to RAID5
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mdadm: Check bitmap first when reshape raid1 to raid0
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Converting 4 disk RAID10 to RAID5
  • From: Anugraha Sinha <asinha.mailinglist@xxxxxxxxx>
• Fwd: Replacing a RAID1 drive that has not failed.
  • From: Edward Kuns <eddie.kuns@xxxxxxxxx>
• Re: Converting 4 disk RAID10 to RAID5
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mdadm: Check bitmap first when reshape raid1 to raid0
  • From: Neil Brown <neilb@xxxxxxx>
• Replacing a RAID1 drive that has not failed.
  • From: Doug Herr <gmane@xxxxxxxxxxx>
• Re: Remove inactive array created by open
  • From: Neil Brown <neilb@xxxxxxxx>
• Re: Remove inactive array created by open
  • From: Simon Guinot <simon.guinot@xxxxxxxxxxxx>
• Re: Fwd: mdadm format for manual destriping
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Fwd: mdadm format for manual destriping
  • From: Marek <mlf.conv@xxxxxxxxx>
• Re: Converting 4 disk RAID10 to RAID5
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Converting 4 disk RAID10 to RAID5
  • From: Anugraha Sinha <asinha.mailinglist@xxxxxxxxx>
• Re: [PATCH] mdadm: Check bitmap first when reshape raid1 to raid0
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [GIT PULL REQUEST] md fixes for 4.3-rc
  • From: Neil Brown <neil@xxxxxxxxxx>
• Converting 4 disk RAID10 to RAID5
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: 2nd Faulty drive while rebuilding array on RAID5
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Fwd: manually destriping a 4 drive raid5 with one missing drive
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: performance issue (was: Re: kernel: BUG: soft lockup - CPU#1 stuck for 60s!)
  • From: Neil Brown <neilb@xxxxxxxx>
• Re: performance issue (was: Re: kernel: BUG: soft lockup - CPU#1 stuck for 60s!)
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• Re: Fwd: [PATCH] mdadm: Check bitmap first when reshape raid1 to raid0
  • From: Neil Brown <neilb@xxxxxxx>
• Re: performance issue (was: Re: kernel: BUG: soft lockup - CPU#1 stuck for 60s!)
  • From: Neil Brown <neilb@xxxxxxxx>
• Re: performance issue (was: Re: kernel: BUG: soft lockup - CPU#1 stuck for 60s!)
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: andras@xxxxxxxxxxxxxxxx
• Fwd: [PATCH] mdadm: Check bitmap first when reshape raid1 to raid0
  • From: Xiao Ni <xni@xxxxxxxxxx>
• 2nd Faulty drive while rebuilding array on RAID5
  • From: Guillaume ALLEE <guillaume.allee@xxxxxxxxx>
• mdadm format for manual destriping
  • From: Marek <mlf.conv@xxxxxxxxx>
• Re: performance issue (was: Re: kernel: BUG: soft lockup - CPU#1 stuck for 60s!)
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• performance issue (was: Re: kernel: BUG: soft lockup - CPU#1 stuck for 60s!)
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• Re: [PATCH 0/2] raid1/10: Handle write errors correctly in narrow_write_error()
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Fwd: manually destriping a 4 drive raid5 with one missing drive
  • From: Dragan Milivojević <galileo@xxxxxxxxxxx>
• Re: Fwd: manually destriping a 4 drive raid5 with one missing drive
  • From: Marek <mlf.conv@xxxxxxxxx>
• Re: [PATCH] mdadm: Check bitmap first when reshape raid1 to raid0
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH v2 01/12] block: Move integrity kobject to struct gendisk
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: [PATCH 0/2] raid1/10: Handle write errors correctly in narrow_write_error()
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Fwd: manually destriping a 4 drive raid5 with one missing drive
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Fwd: manually destriping a 4 drive raid5 with one missing drive
  • From: Marek <mlf.conv@xxxxxxxxx>
• Re: manually destriping a 4 drive raid5 with one missing drive
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: [PATCH 0/2] raid1/10: Handle write errors correctly in narrow_write_error()
  • From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
• Re: manually destriping a 4 drive raid5 with one missing drive
  • From: Alexander Afonyashin <a.afonyashin@xxxxxxxxxxxxxx>
• Re: [PATCH] md-cluster: Only one thread should request DLM lock
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Fwd: manually destriping a 4 drive raid5 with one missing drive
  • From: Marek <mlf.conv@xxxxxxxxx>
• Re: RAID6 grow unexpected results
  • From: Neil Brown <nfbrown@xxxxxxxxxx>
• Re: RAID6 grow unexpected results
  • From: Liwei <xieliwei@xxxxxxxxx>
• Re: Hung RAID5 array with discard
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Hung RAID5 array with discard
  • From: Peter Kieser <peter@xxxxxxxxx>
• Re: Hung RAID5 array with discard
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md-cluster: Only one thread should request DLM lock
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 0/2] raid1/10: Handle write errors correctly in narrow_write_error()
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Remove inactive array created by open
  • From: Neil Brown <neilb@xxxxxxxx>
• Re: RAID6 grow unexpected results
  • From: Neil Brown <nfbrown@xxxxxxxxxx>
• Re: [PATCH 0/2] raid1/10: Handle write errors correctly in narrow_write_error()
  • From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
• Re: [PATCH 0/2] raid1/10: Handle write errors correctly in narrow_write_error()
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Remove inactive array created by open
  • From: Neil Brown <neilb@xxxxxxxx>
• RAID6 grow unexpected results
  • From: Liwei <xieliwei@xxxxxxxxx>
• Remove inactive array created by open
  • From: Simon Guinot <simon.guinot@xxxxxxxxxxxx>
• Re: Hung RAID5 array with discard
  • From: Peter Kieser <peter@xxxxxxxxx>
• [PATCH 2/2] md/raid10: Do not clear bitmap bit if submit_bio_wait() fails
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 1/2] md/raid1: Do not clear bitmap bit if submit_bio_wait() fails
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: [PATCH 0/2] raid1/10: Handle write errors correctly in narrow_write_error()
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• [PATCH] md-cluster: Call update_raid_disks() if another node --grow's raid_disks
  • From: rgoldwyn@xxxxxxx
• [PATCH] md-cluster: Only one thread should request DLM lock
  • From: rgoldwyn@xxxxxxx
• Re: [PATCH 0/3] improve mdadm support of write journal
  • From: Neil Brown <neilb@xxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Neil Brown <nfbrown@xxxxxxxxxx>
• [PATCH 2/3] mdadm: Add description of write journal to md.4
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 0/3] improve mdadm support of write journal
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 3/3] mdadm: add test script for raid456 journal
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 1/3] mdadm: refactor write journal code in Assemble and Incremental
  • From: Song Liu <songliubraving@xxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [dm-devel] Possible bug in DM-RAID.
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: Possible bug in DM-RAID.
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: Possible bug in DM-RAID.
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• looking for good reference on storage configuration
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: andras@xxxxxxxxxxxxxxxx
• Re: How to recover after md crash during reshape?
  • From: andras@xxxxxxxxxxxxxxxx
• Re: Possible bug in DM-RAID.
  • From: Neil Brown <nfbrown@xxxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Neil Brown <nfbrown@xxxxxxxxxx>
• Re: [PATCH 0/2] raid1/10: Handle write errors correctly in narrow_write_error()
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Anugraha Sinha <asinha.mailinglist@xxxxxxxxx>
• Re: [PATCH 0/2] raid1/10: Handle write errors correctly in narrow_write_error()
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH 1/2] md/raid1: submit_bio_wait() returns 0 on success
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 2/2] md/raid10: submit_bio_wait() returns 0 on success
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/2] raid1/10: Handle write errors correctly in narrow_write_error()
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: How to recover after md crash during reshape?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Possible bug in DM-RAID.
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Anugraha Sinha <asinha.mailinglist@xxxxxxxxx>
• Re: How to recover after md crash during reshape?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• How to recover after md crash during reshape?
  • From: andras@xxxxxxxxxxxxxxxx
• Re: [PATCH v2 10/12] block: move blk_integrity to request_queue
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• RE: [PATCH 3/6] Enable create array with write journal (--write-journal DEVICE).
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 5/6] Check write journal in incremental
  • From: Neil Brown <neilb@xxxxxxx>
• RE: [PATCH v2 0/6] mdadm support for journal device of RAID-4/5/6
  • From: Neil Brown <neilb@xxxxxxx>
• Stimate utilizator
  • From: Web-Admin <webmail@xxxxxxxxxxx>
• Re: manually destriping a 4 drive raid5 with one missing drive
  • From: Neil Brown <nfbrown@xxxxxxxxxx>
• Re: kernel: BUG: soft lockup - CPU#1 stuck for 60s! [md0_raid5:1614]
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• manually destriping a 4 drive raid5 with one missing drive
  • From: Marek <mlf.conv@xxxxxxxxx>
• RE: Scalability of MD raid 1 mirror devices
  • From: Neil Brown <neilb@xxxxxxx>
• Re: kernel: BUG: soft lockup - CPU#1 stuck for 60s! [md0_raid5:1614]
  • From: Neil Brown <nfbrown@xxxxxxxxxx>
• RE: Scalability of MD raid 1 mirror devices
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH v2 10/12] block: move blk_integrity to request_queue
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2 00/12] blk-integrity lifetime fixes
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2 00/12] blk-integrity lifetime fixes
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• [PATCH v2 08/12] nvme: suspend i/o during runtime blk_integrity_unregister
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 12/12] block, libnvdimm, nvme: provide a built-in blk_integrity nop profile
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 11/12] block: blk_flush_integrity() for bio-based drivers
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 10/12] block: move blk_integrity to request_queue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 09/12] block: generic request_queue reference counting
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 07/12] md: suspend i/o during runtime blk_integrity_unregister
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 06/12] md, dm, scsi, nvme, libnvdimm: drop blk_integrity_unregister() at shutdown
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 05/12] block: Inline blk_integrity in struct gendisk
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 02/12] block: Consolidate static integrity profile properties
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 04/12] block: Export integrity data interval size in sysfs
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 03/12] block: Reduce the size of struct blk_integrity
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 01/12] block: Move integrity kobject to struct gendisk
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 00/12] blk-integrity lifetime fixes
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2 7/7] Smack: Handle labels consistently in untrusted mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• kernel: BUG: soft lockup - CPU#1 stuck for 60s! [md0_raid5:1614]
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• Re: Debian jessie - RAID 6 reshape - making no progress after >48 hours
  • From: Alexander Afonyashin <a.afonyashin@xxxxxxxxxxxxxx>
• RE: Scalability of MD raid 1 mirror devices
  • From: Ankur Bose <ankur.bose@xxxxxxxxxx>
• Re: Debian jessie - RAID 6 reshape - making no progress after >48 hours
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• RE: [PATCH] MD: fix missing cpu_to_le32 for MD_FEATURE_JOURNAL
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH] MD: fix missing cpu_to_le32 for MD_FEATURE_JOURNAL
  • From: Neil Brown <neilb@xxxxxxxx>
• [PATCH] MD: fix missing cpu_to_le32 for MD_FEATURE_JOURNAL
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH v2 7/7] Smack: Handle labels consistently in untrusted mounts
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [md:devel 40/44] drivers/md/md.c:1813:33: sparse: invalid assignment: |=
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• [md:devel 12/62] drivers/md/md-cluster.c:943:24: sparse: incorrect type in assignment (different base types)
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• Re: [PATCH] md: fix 32-bit build warning
  • From: Neil Brown <neilb@xxxxxxxx>
• Re: mdadm RAID 5 reshape not working
  • From: "Daniel J. R. May" <daniel.may@xxxxxxxxxxxxxx>
• mdadm RAID 5 reshape not working
  • From: "Daniel J. R. May" <daniel.may@xxxxxxxxxxxxxx>
• Debian jessie - RAID 6 reshape - making no progress after >48 hours
  • From: Phil Reynolds <phil@xxxxxxxxxxxxxxxxxx>
• Re: First 12Mb of data missing after accidental deletion of first drive (4 2TB raid5)
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: First 12Mb of data missing after accidental deletion of first drive (4 2TB raid5)
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/9] raid5-cache fixes
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH V2] MD: fix info output for journal disk
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH v2 5/7] selinux: Add support for unprivileged mounts from user namespaces
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 4/6] md: don't export log device
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 00/14] md-cluster: A better way for METADATA_UPDATED processing
  • From: Neil Brown <neilb@xxxxxxx>
• Re: First 12Mb of data missing after accidental deletion of first drive (4 2TB raid5)
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: Block integrity registration update
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 1/7] block_dev: Support checking inode permissions in lookup_bdev()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 2/7] block_dev: Check permissions towards block device inode when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 4/7] fs: Treat foreign mounts as nosuid
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 5/7] selinux: Add support for unprivileged mounts from user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 3/7] mtd: Check permissions towards mtd block device inode when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 6/7] userns: Replace in_userns with current_in_userns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 7/7] Smack: Handle labels consistently in untrusted mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: First 12Mb of data missing after accidental deletion of first drive (4 2TB raid5)
  • From: Marek <mlf.conv@xxxxxxxxx>
• Re: First 12Mb of data missing after accidental deletion of first drive (4 2TB raid5)
  • From: Marek <mlf.conv@xxxxxxxxx>
• [PATCH 06/14] md-cluster: Fix adding of new disk with new reload code
  • From: rgoldwyn@xxxxxxx
• Re: First 12Mb of data missing after accidental deletion of first drive (4 2TB raid5)
  • From: Alexander Afonyashin <a.afonyashin@xxxxxxxxxxxxxx>
• [PATCH 09/14] md-cluster: remove unnecessary setting for slot
  • From: rgoldwyn@xxxxxxx
• [PATCH 14/14] md: check the return value for metadata_update_start
  • From: rgoldwyn@xxxxxxx
• [PATCH 13/14] md-cluster: only call kick_rdev_from_array after remove disk successfully
  • From: rgoldwyn@xxxxxxx
• [PATCH 12/14] md-cluster: Add 'SUSE' as author for md-cluster.c
  • From: rgoldwyn@xxxxxxx
• [PATCH 11/14] md-cluster: zero cmsg before it was sent
  • From: rgoldwyn@xxxxxxx
• [PATCH 10/14] md-cluster: make sure the node do not receive it's own msg
  • From: rgoldwyn@xxxxxxx
• [PATCH 08/14] md-cluster: make other members of cluster_msg is handled by little endian funcs
  • From: rgoldwyn@xxxxxxx
• [PATCH 07/14] md-cluster: Do not printk() every received message
  • From: rgoldwyn@xxxxxxx
• [PATCH 05/14] md-cluster: Perform resync/recovery under a DLM lock
  • From: rgoldwyn@xxxxxxx
• [PATCH 04/14] md-cluster: Perform a lazy update
  • From: rgoldwyn@xxxxxxx
• [PATCH 03/14] md-cluster: Improve md_reload_sb to be less error prone
  • From: rgoldwyn@xxxxxxx
• [PATCH 02/14] md: remove_and_add_spares() to activate specific rdev
  • From: rgoldwyn@xxxxxxx
• [PATCH 01/14] md-cluster: Wake up suspended process
  • From: rgoldwyn@xxxxxxx
• [PATCH 00/14] md-cluster: A better way for METADATA_UPDATED processing
  • From: rgoldwyn@xxxxxxx
• Re: First 12Mb of data missing after accidental deletion of first drive (4 2TB raid5)
  • From: Marek <mlf.conv@xxxxxxxxx>
• Re: First 12Mb of data missing after accidental deletion of first drive (4 2TB raid5)
  • From: Marek <mlf.conv@xxxxxxxxx>
• Re: First 12Mb of data missing after accidental deletion of first drive (4 2TB raid5)
  • From: Alexander Afonyashin <a.afonyashin@xxxxxxxxxxxxxx>
• Fwd: First 12Mb of data missing after accidental deletion of first drive (4 2TB raid5)
  • From: Marek <mlf.conv@xxxxxxxxx>
• [PATCH] dm snapshot: fix memory leak in error path
  • From: Michael Opdenacker <michael.opdenacker@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 4/6] md: don't export log device
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH] dm snapshot: fix memory leak
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: Puzzled by raid 10 (f2) and raid 6 direct i/o read behaviour
  • From: Dragan Milivojević <galileo@xxxxxxxxxxx>
• [PATCH V2] MD: fix info output for journal disk
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 1/9] MD: fix info output for journal disk
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 1/9] MD: fix info output for journal disk
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 1/9] MD: fix info output for journal disk
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 2/9] raid5-cache: add trim support for log
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH] md: workqueue: Remove WQ_CPU_INTENSIVE from unbound workqueue allocations
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Scalability of MD raid 1 mirror devices
  • From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
• Re: [PATCH] md: fix 32-bit build warning
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH 0/9] raid5-cache fixes
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 2/9] raid5-cache: add trim support for log
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 1/9] MD: fix info output for journal disk
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md: fix 32-bit build warning
  • From: Neil Brown <neilb@xxxxxxxx>
• [GIT PULL REQUEST] md bugfix
  • From: Neil Brown <neil@xxxxxxxxxx>
• Re: 30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke cryptsetup on my machine
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: 30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke cryptsetup on my machine
  • From: Giedrius Statkevičius <giedrius.statkevicius@xxxxxxxxx>
• Re: [parted-devel] [PATCH 1/2] Add nonfs partition type 0xda (#1263835)
  • From: "Brian C. Lane" <bcl@xxxxxxxxxx>
• Re: [parted-devel] [PATCH 1/2] Add nonfs partition type 0xda (#1263835)
  • From: Phil Susi <psusi@xxxxxxxxxx>
• Re: [parted-devel] [PATCH 1/2] Add nonfs partition type 0xda (#1263835)
  • From: "Brian C. Lane" <bcl@xxxxxxxxxx>
• Re: [parted-devel] [PATCH 1/2] Add nonfs partition type 0xda (#1263835)
  • From: Phil Susi <psusi@xxxxxxxxxx>
• [PATCH] md: fix 32-bit build warning
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• [PATCH v2 4/6] Assemble array with write journal
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH v2 5/6] Check write journal in incremental
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH v2 6/6] Add help message and man entry for --write-journal
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH v2 3/6] Enable create array with write journal (--write-journal DEVICE).
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH v2 2/6] Show device as journal in --detail --examine
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH v2 1/6] add macros for MD_DISK_ROLE_(SPARE/FAULTY)
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH v2 0/6] mdadm support for journal device of RAID-4/5/6
  • From: Song Liu <songliubraving@xxxxxx>
• Re: Change "mv $targetdir/log $logdir/$log" to "cp $targetdir/log $logdir/$log"
  • From: Neil Brown <neil@xxxxxxxxxx>
• [PATCH 5/9] MD: add new bit to indicate raid array with journal
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 1/9] MD: fix info output for journal disk
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 4/9] raid5-cache: IO error handling
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 6/9] raid5-cache: start raid5 readonly if journal is missing
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 7/9] MD: kick out journal disk if it's not fresh
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 9/9] MD: when RAID journal is missing/faulty, block RESTART_ARRAY_RW
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 8/9] MD: set journal disk ->raid_disk
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 0/9] raid5-cache fixes
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 3/9] raid5: journal disk can't be removed
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 2/9] raid5-cache: add trim support for log
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH] md: workqueue: Remove WQ_CPU_INTENSIVE from unbound workqueue allocations
  • From: Xunlei Pang <xlpang@xxxxxxx>
• Re: Problem w/ commit ac8fa4196d20 on older, slower hardware
  • From: Neil Brown <neilb@xxxxxxxx>
• Re: [PATCH] crash in md-raid1 and md-raid10 due to incorrect list manipulation
  • From: Neil Brown <neilb@xxxxxxxx>
• Re: [PATCH 1/5] fs: Verify access of user towards block device file when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: 30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke cryptsetup on my machine
  • From: Geliang Tang <geliangtang@xxxxxxx>
• [PATCH] dm ioctl: bugfix for kvfree() in free_params()
  • From: Geliang Tang <geliangtang@xxxxxxx>
• Re: [PATCH 4/6] md: don't export log device
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 4/6] md: don't export log device
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH RESEND] imsm: don't call abort_reshape() in imsm_manage_reshape()
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 4/6] md: don't export log device
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 0/6] raid5-cache fixes
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 0/6] raid5-cache fixes
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 4/6] md: don't export log device
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 0/6] raid5-cache fixes
  • From: Shaohua Li <shli@xxxxxx>
• Re: raid5-cache I/O path improvements V3
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 0/6] raid5-cache fixes
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 4/6] md: don't export log device
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 3/6] raid5-cache: add trim support for log
  • From: Neil Brown <neilb@xxxxxxx>
• 30c2a1faaeb3db94fc92f79553cc72634aa3b218 broke cryptsetup on my machine
  • From: Giedrius Statkevičius <giedrius.statkevicius@xxxxxxxxx>
• RE: [PATCH 4/6] Assemble array with write journal
  • From: Song Liu <songliubraving@xxxxxx>
• RE: [PATCH 3/6] Enable create array with write journal (--write-journal DEVICE).
  • From: Song Liu <songliubraving@xxxxxx>
• Re: Unable to assemble RAID6 after Ubuntu>Arch switch
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: [PATCH 5/6] Check write journal in incremental
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 4/6] Assemble array with write journal
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 3/6] Enable create array with write journal (--write-journal DEVICE).
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: raid5-cache I/O path improvements V3
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 5/5] Fix adding of new disk with new reload code
  • From: rgoldwyn@xxxxxxx
• [PATCH 4/5] Perform resync/recovery under a DLM lock
  • From: rgoldwyn@xxxxxxx
• [PATCH 3/5] md-cluster: Perform a lazy update
  • From: rgoldwyn@xxxxxxx
• [PATCH 2/5] md-cluster: Improve md_reload_sb to be less error prone
  • From: rgoldwyn@xxxxxxx
• [PATCH 1/5] remove_and_add_spares() to activate specific rdev
  • From: rgoldwyn@xxxxxxx
• [PATCH 0/5 v2] md-cluster: A better way for METADATA_UPDATED processing
  • From: rgoldwyn@xxxxxxx
• Re: [PATCH 1/5] fs: Verify access of user towards block device file when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH RESEND] imsm: don't call abort_reshape() in imsm_manage_reshape()
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH] bcache: Really show state of work pending bit
  • From: Petr Mladek <pmladek@xxxxxxxx>
• Problem w/ commit ac8fa4196d20 on older, slower hardware
  • From: Joshua Kinard <kumba@xxxxxxxxxx>
• [PATCH 11/11] raid5-cache: use bio chaining
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 10/11] raid5-cache: small log->seq cleanup
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 09/11] raid5-cache: new helper: r5_reserve_log_entry
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 08/11] raid5-cache: inline r5l_alloc_io_unit into r5l_new_meta
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 07/11] raid5-cache: take rdev->data_offset into account early on
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 05/11] raid5-cache: clean up r5l_get_meta
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 06/11] raid5-cache: refactor bio allocation
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 04/11] raid5-cache: simplify state machine when caches flushes are not needed
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 03/11] raid5-cache: factor out a helper to run all stripes for an I/O unit
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 02/11] raid5-cache: rename flushed_ios to finished_ios
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 01/11] raid5-cache: free I/O units earlier
  • From: Christoph Hellwig <hch@xxxxxx>
• raid5-cache I/O path improvements V3
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 6/6] raid5-cache: IO error handling
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 4/6] md: don't export log device
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 3/6] raid5-cache: add trim support for log
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 1/6] md: show journal for journal disk in disk state sysfs
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 0/6] raid5-cache fixes
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 5/6] md: set In_Sync for log disk
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 2/6] raid5-cache: move reclaim stop to quiesce
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 3/3] raid5-cache: IO error handling
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [GIT PULL REQUEST] md fixes for 4.3
  • From: Neil Brown <neil@xxxxxxxxxx>
• [md:devel 19/33] ERROR: "wrong_size_cmpxchg" [drivers/md/raid456.ko] undefined!
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• [md:devel 18/33] mips-linux-gnu-ld: drivers/md/raid5-cache.o: warning: Inconsistent ISA between e_flags and .MIPS.abiflags
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• [PATCH] dm ioctl: use kvfree() in free_params()
  • From: Geliang Tang <geliangtang@xxxxxxx>
• Re: md127 auto created when use "-B" to build a legacy array without superblocks
  • From: Neil Brown <neilb@xxxxxxxx>
• RE: [PATCH 7/8] md: skip resync for raid array with journal
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 1/5] fs: Verify access of user towards block device file when mounting
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH] crash in md-raid1 and md-raid10 due to incorrect list manipulation
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• mdraid + dm-multipath - non-dm-mulitpath boot md coexisting with dm-multi md data volume?
  • From: Jeff Johnson <jeff.johnson@xxxxxxxxxxxxxxxxx>
• RE: [PATCH 7/8] md: skip resync for raid array with journal
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 1/5] fs: Verify access of user towards block device file when mounting
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 1/5] fs: Verify access of user towards block device file when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 1/5] fs: Verify access of user towards block device file when mounting
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 1/5] fs: Verify access of user towards block device file when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 1/5] fs: Verify access of user towards block device file when mounting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/5] fs: Verify access of user towards block device file when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 3/3] raid5-cache: IO error handling
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 2/3] md: don't export log device
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 1/3] raid5-cache: add trim support for log
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 1/5] fs: Verify access of user towards block device file when mounting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 3/3] raid5-cache: IO error handling
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 0/3] raid5-cache fixes
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 2/3] md: don't export log device
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 1/3] raid5-cache: add trim support for log
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 0/5] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 3/5] selinux: Add support for unprivileged mounts from user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 4/5] userns: Replace in_userns with current_in_userns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 5/5] Smack: Handle labels consistently in untrusted mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 2/5] fs: Treat foreign mounts as nosuid
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 1/5] fs: Verify access of user towards block device file when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: raid5-cache I/O path improvements V2
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] skip match_mddev_units check for special roles
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] enable bypass raid5 journal for full stripe writes
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 1/2] md: clear CHANGE_PENDING in readonly array
  • From: Neil Brown <neilb@xxxxxxx>
• [md:devel 19/30] drivers/md/raid5-cache.c:836:24: sparse: incompatible types in comparison expression (different address spaces)
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• Re: raid5-cache I/O path improvements V2
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 0/8] raid5-cache fixes
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 7/8] md: skip resync for raid array with journal
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 8/8] raid5-cache: add trim support for log
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 2/3] md-cluster: Improve md_reload_sb to be less error prone
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 3/3] md-cluster: Perform a lazy update
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [RFC PATCH] md-cluster: does_sb_need_changing() can be static
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [RFC PATCH] md-cluster: __md_error() can be static
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 2/3] md-cluster: Improve md_reload_sb to be less error prone
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 2/3] md-cluster: Improve md_reload_sb to be less error prone
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 2/3] md-cluster: Improve md_reload_sb to be less error prone
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [PATCH 0/3] md-cluster: A better way for METADATA_UPDATED processing
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxx>
• [PATCH 2/3] md-cluster: Improve md_reload_sb to be less error prone
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxx>
• [PATCH 3/3] md-cluster: Perform a lazy update
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxx>
• [PATCH 1/3] remove_and_add_spares() to activate specific rdev
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxx>
• Re: raid5-cache I/O path improvements V2
  • From: Christoph Hellwig <hch@xxxxxx>
• Start reshape failed
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Guidance on reshape stuck at 0% after --grow
  • From: Guillaume Paumier <guillaume.paumier@xxxxxxxxx>
• Re: Guidance on reshape stuck at 0% after --grow
  • From: Guillaume Paumier <guillaume.paumier@xxxxxxxxx>
• Re: Unable to assemble RAID6 after Ubuntu>Arch switch
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Unable to assemble RAID6 after Ubuntu>Arch switch
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Unable to assemble RAID6 after Ubuntu>Arch switch
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Unable to assemble RAID6 after Ubuntu>Arch switch
  • From: Alexander Afonyashin <a.afonyashin@xxxxxxxxxxxxxx>
• Re: Bad raid0 bio too large problem
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Unable to assemble RAID6 after Ubuntu>Arch switch
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: [PATCH 1/2] md: clear CHANGE_PENDING in readonly array
  • From: Shaohua Li <shli@xxxxxx>
• Re: Bad raid0 bio too large problem
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• RAID5 Recovery From NAS With 4x3TB SATA Disks
  • From: mike@xxxxxxxxxxxx
• Re: Unable to assemble RAID6 after Ubuntu>Arch switch
  • From: Alexander Afonyashin <a.afonyashin@xxxxxxxxxxxxxx>
• Re: Bad raid0 bio too large problem
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH 2/2] raid5: update analysis state for failed stripe
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 1/2] md: clear CHANGE_PENDING in readonly array
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Bad raid0 bio too large problem
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Unable to assemble RAID6 after Ubuntu>Arch switch
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Guidance on reshape stuck at 0% after --grow
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Bad raid0 bio too large problem
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Bad raid0 bio too large problem
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Bad raid0 bio too large problem
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 1/1] md/raid1: Avoid raid1 resync getting stuck
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 2/2] raid5: update analysis state for failed stripe
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 2/2] raid5: update analysis state for failed stripe
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Unable to assemble RAID6 after Ubuntu>Arch switch
  • From: Alexander Afonyashin <a.afonyashin@xxxxxxxxxxxxxx>
• Re: [PATCH 1/2] md: clear CHANGE_PENDING in readonly array
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 1/2] md: clear CHANGE_PENDING in readonly array
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Bad raid0 bio too large problem
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Guidance on reshape stuck at 0% after --grow
  • From: Guillaume Paumier <guillaume.paumier@xxxxxxxxx>
• Unable to assemble RAID6 after Ubuntu>Arch switch
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Bad raid0 bio too large problem
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Bad raid0 bio too large problem
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Guidance on reshape stuck at 0% after --grow
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Fwd: Failed Raid6 Array.....want some guidance before attempting restart
  • From: Another Sillyname <anothersname@xxxxxxxxxxxxxx>
• md: How to change homehost without re-assemble md
  • From: Apple Yin <bravery.apple@xxxxxxxxx>
• Re: Recommendations for RAID setup needed
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Recommendations for RAID setup needed
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: Recommendations for RAID setup needed
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Guidance on reshape stuck at 0% after --grow
  • From: Guillaume Paumier <guillaume.paumier@xxxxxxxxx>
• Re: Fwd: Failed Raid6 Array.....want some guidance before attempting restart
  • From: Another Sillyname <anothersname@xxxxxxxxxxxxxx>
• Re: Fwd: Failed Raid6 Array.....want some guidance before attempting restart
  • From: Another Sillyname <anothersname@xxxxxxxxxxxxxx>
• Re: Fwd: Failed Raid6 Array.....want some guidance before attempting restart
  • From: Alexander Afonyashin <a.afonyashin@xxxxxxxxxxxxxx>
• Re: Fwd: Failed Raid6 Array.....want some guidance before attempting restart
  • From: Another Sillyname <anothersname@xxxxxxxxxxxxxx>
• Re: Fwd: Failed Raid6 Array.....want some guidance before attempting restart
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Fwd: Failed Raid6 Array.....want some guidance before attempting restart
  • From: Another Sillyname <anothersname@xxxxxxxxxxxxxx>
• Re: Fwd: Failed Raid6 Array.....want some guidance before attempting restart
  • From: Another Sillyname <anothersname@xxxxxxxxxxxxxx>
• Re: Fwd: Failed Raid6 Array.....want some guidance before attempting restart
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Fwd: Failed Raid6 Array.....want some guidance before attempting restart
  • From: Another Sillyname <anothersname@xxxxxxxxxxxxxx>
• Re: Failed Raid6 Array.....want some guidance before attempting restart
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Failed Raid6 Array.....want some guidance before attempting restart
  • From: Another Sillyname <anothersname@xxxxxxxxxxxxxx>
• [PATCH 2/2] raid5: update analysis state for failed stripe
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 1/2] md: clear CHANGE_PENDING in readonly array
  • From: Shaohua Li <shli@xxxxxx>
• strange syslog message on daily mdadm cron job
  • From: "Jens-U. Mozdzen" <jmozdzen@xxxxxx>
• Re: Recommendations for RAID setup needed
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: Recommendations for RAID setup needed
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Fwd: mdadm: not rebuilding IMSM array without OROM
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: raid5-cache I/O path improvements V2
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 02/12] raid5-cache: free I/O units earlier
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 02/12] raid5-cache: free I/O units earlier
  • From: Christoph Hellwig <hch@xxxxxx>
• Fwd: mdadm: not rebuilding IMSM array without OROM
  • From: Justin Capella <justincapella@xxxxxxxxx>
• Re: Recommendations for RAID setup needed
  • From: Alex <mysqlstudent@xxxxxxxxx>
• [PATCH 1/1] md/raid1: Avoid raid1 resync getting stuck
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/1] Fix raid1 resync getting stuck
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: Recommendations for RAID setup needed
  • From: "Jens-U. Mozdzen" <jmozdzen@xxxxxx>
• Re: Recommendations for RAID setup needed
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: raid5-cache I/O path improvements V2
  • From: Shaohua Li <shli@xxxxxx>
• Re: Recommendations for RAID setup needed
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Recommendations for RAID setup needed
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: dm: ioctl: prevent double freeing
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Recommendations for RAID setup needed
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Recommendations for RAID setup needed
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: [dm-devel] [PATCH] dm: ioctl: prevent double freeing
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: raid1 resync stuck
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: raid1 resync stuck
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5-cache I/O path improvements V2
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 17/39] md: drop null test before destroy functions
  • From: Neil Brown <neilb@xxxxxxxx>
• Re: [PATCH 02/12] raid5-cache: free I/O units earlier
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 02/12] raid5-cache: free I/O units earlier
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] dm: ioctl: prevent double freeing
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: raid5-cache I/O path improvements V2
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 12/39] dm: drop null test before destroy functions
  • From: Julia Lawall <julia.lawall@xxxxxxx>
• Re: [dm-devel] [PATCH 12/39] dm: drop null test before destroy functions
  • From: walter harms <wharms@xxxxxx>
• Re: [PATCH 12/39] dm: drop null test before destroy functions
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 12/39] dm: drop null test before destroy functions
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [dm-devel] [PATCH 12/39] dm: drop null test before destroy functions
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 00/39] drop null test before destroy functions
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 15/39] bcache: drop null test before destroy functions
  • From: Johannes Thumshirn <jthumshirn@xxxxxxx>
• Re: mdstat reporting (superblock & status side-by-side). Can it be changed ?
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• mdstat reporting (superblock & status side-by-side). Can it be changed ?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• [PATCH 00/39] drop null test before destroy functions
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH 12/39] dm: drop null test before destroy functions
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH 15/39] bcache: drop null test before destroy functions
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH 17/39] md: drop null test before destroy functions
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH 12/12] raid5-cache: use bio chaining
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 11/12] raid5-cache: small log->seq cleanup
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 04/12] raid5-cache: factor out a helper to run all stripes for an I/O unit
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 10/12] raid5-cache: new helper: r5_reserve_log_entry
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 09/12] raid5-cache: inline r5l_alloc_io_unit into r5l_new_meta
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 08/12] raid5-cache: take rdev->data_offset into account early on
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 07/12] raid5-cache: refactor bio allocation
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 06/12] raid5-cache: clean up r5l_get_meta
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 05/12] raid5-cache: use FUA writes for the log
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 03/12] raid5-cache: rename flushed_ios to finished_ios
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 02/12] raid5-cache: free I/O units earlier
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 01/12] raid5-cache: port to 4.3-rc
  • From: Christoph Hellwig <hch@xxxxxx>
• raid5-cache I/O path improvements V2
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: raid1 resync stuck
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: raid role number off on one array?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: raid role number off on one array?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• raid role number off on one array?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• [PATCH] Remove unused argument in md_new_event()
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: raid1 resync stuck
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• raid1 resync stuck
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: raid5-cache I/O path improvements
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: raid5-cache I/O path improvements
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: raid5-cache I/O path improvements
  • From: Shaohua Li <shli@xxxxxx>
• Re: raid5-cache I/O path improvements
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: raid5-cache I/O path improvements
  • From: Shaohua Li <shli@xxxxxx>
• Re: raid5-cache I/O path improvements
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: raid5-cache I/O path improvements
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: raid5-cache I/O path improvements
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: raid5-cache I/O path improvements
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: RAID4/5/6 reshape grow stuck
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• Re: raid5-cache I/O path improvements
  • From: Shaohua Li <shli@xxxxxx>
• md127 auto created when use "-B" to build a legacy array without superblocks
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• RAID4/5/6 reshape grow stuck
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• Disk failed on grow process and missing backup-file
  • From: Юрий Букин <yury@xxxxxxxx>
• [PATCH 10/10] raid5-cache: use bio chaining
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 09/10] raid5-cache: small log->seq cleanup
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 08/10] raid5-cache: new helper: r5_reserve_log_entry
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 07/10] raid5-cache: inline r5l_alloc_io_unit into r5l_new_meta
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 06/10] raid5-cache: take rdev->data_offset into account early on
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 05/10] raid5-cache: refactor bio allocation
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 04/10] raid5-cache: clean up r5l_get_meta
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 03/10] raid5-cache: use FUA writes for the log
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 02/10] raid5-cache: free I/O units earlier
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 01/10] raid5-cache: port to 4.3-rc
  • From: Christoph Hellwig <hch@xxxxxx>
• raid5-cache I/O path improvements
  • From: Christoph Hellwig <hch@xxxxxx>
• Change "mv $targetdir/log $logdir/$log" to "cp $targetdir/log $logdir/$log"
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• Re: [GIT PULL REQUEST] md updates for 4.3
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• [GIT PULL REQUEST] md updates for 4.3
  • From: Neil Brown <neil@xxxxxxxxxx>
• [PATCH] raid5-cache: don't delay stripe captured in log
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH] raid5-cache: check stripe finish out of order
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH] dm: ioctl: prevent double freeing
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• [PATCH] imsm: don't call abort_reshape() in imsm_manage_reshape()
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: Raid 10 array problems
  • From: Alexander Afonyashin <a.afonyashin@xxxxxxxxxxxxxx>
• [PATCH] enable bypass raid5 journal for full stripe writes
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH] skip match_mddev_units check for special roles
  • From: Song Liu <songliubraving@xxxxxx>
• Raid 10 array problems
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Expanding RAID0
  • From: Alexander Afonyashin <a.afonyashin@xxxxxxxxxxxxxx>
• [PATCH 3/8] raid5-cache: switching to state machine for log disk cache flush
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 7/8] md: skip resync for raid array with journal
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 8/8] raid5-cache: add trim support for log
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 5/8] raid5-cache: move functionality out of __r5l_set_io_unit_state
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 6/8] raid5-cache: optimize FLUSH IO with log enabled
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 1/8] md: fix feature map check
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 0/8] raid5-cache fixes
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 4/8] raid5-cache: fix a user-after-free bug
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 2/8] raid5: fix build error
  • From: Shaohua Li <shli@xxxxxx>
• Re: fix use after free in raid5-cache
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: fix use after free in raid5-cache
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 1/3] raid5-cache: move functionality out of __r5l_set_io_unit_state
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 3/3] raid5-cache: fix __r5l_stripe_write_finished
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 2/3] raid5-cache: remove r5l_move_io_unit_list
  • From: Christoph Hellwig <hch@xxxxxx>
• fix use after free in raid5-cache
  • From: Christoph Hellwig <hch@xxxxxx>
• Expanding RAID0
  • From: Alexander Afonyashin <a.afonyashin@xxxxxxxxxxxxxx>
• RE: [PATCH 2/6] Show device as journal in --detail --examine
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 2/6] Show device as journal in --detail --examine
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• RE: [PATCH 2/6] Show device as journal in --detail --examine
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 2/6] Show device as journal in --detail --examine
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re-add of raid1 drive resulted in strange loss of data on Archlinux?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• [PATCH 2/6] Show device as journal in --detail --examine
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 5/6] Check write journal in incremental
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 3/6] Enable create array with write journal (--write-journal DEVICE).
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 1/6] add macros for MD_DISK_ROLE_(SPARE/FAULTY)
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 4/6] Assemble array with write journal
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 6/6] Add help message and man entry for --write-journal
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 0/6] mdadm support for journal device of RAID-4/5/6
  • From: Song Liu <songliubraving@xxxxxx>
• Re: How best to re-sync raid1 array? zero superblock on removed disk and let it rebuild?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: How best to re-sync raid1 array? zero superblock on removed disk and let it rebuild?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: How best to re-sync raid1 array? zero superblock on removed disk and let it rebuild?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: How best to re-sync raid1 array? zero superblock on removed disk and let it rebuild?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• How best to re-sync raid1 array? zero superblock on removed disk and let it rebuild?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• [PATCH 1/3] config.c: since dlist is initialized as NULL, remove the useless code
  • From: Lidong Zhong <lzhong@xxxxxxxx>
• [PATCH 3/3] mdadm: remove duplicate logic when c.delay is 0
  • From: Lidong Zhong <lzhong@xxxxxxxx>
• [PATCH 2/3] policy.c: make it easily understood when comparing the string
  • From: Lidong Zhong <lzhong@xxxxxxxx>
• Re: Re-add not selecting drive for correct slot?
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: [PATCH stable] md/bitmap: return an error when bitmap superblock is corrupt.
  • From: Luis Henriques <luis.henriques@xxxxxxxxxxxxx>
• Re: unable to handle kernel NULL pointer dereference in get_free_stripe
  • From: Christian Hesse <list@xxxxxxxx>
• Re: unable to handle kernel NULL pointer dereference in get_free_stripe
  • From: Neil Brown <neilb@xxxxxxxx>
• unable to handle kernel NULL pointer dereference in get_free_stripe
  • From: Christian Hesse <list@xxxxxxxx>
• ques on multi threaded raid
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: [md:devel 46/50] drivers/md/raid5-cache.c:710:1371: error: call to '__cmpxchg_wrong_size' declared with attribute error: Bad argument size for cmpxchg
  • From: Shaohua Li <shli@xxxxxx>
• [md:devel 47/50] drivers/md/raid5-cache.c:828:24: sparse: incompatible types in comparison expression (different address spaces)
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• [md:devel 41/50] drivers/md/md.c:1663:33: sparse: restricted __le32 degrades to integer
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• [PATCH 0/2] mdadm: Fix udev rule interaction with systemd
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• [PATCH 2/2] udev: Work around race condition on array activation
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• [PATCH 1/2] udev: Set SYSTEMD_READY to 1 when the array becomes active
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Re: moving arrays from MBR part table install to GPT? Possible?
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• Re: moving arrays from MBR part table install to GPT? Possible?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: moving arrays from MBR part table install to GPT? Possible?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: [patch v2 00/11]md: fix raid5 write hole
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH stable] md/bitmap: return an error when bitmap superblock is corrupt.
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: moving arrays from MBR part table install to GPT? Possible?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• moving arrays from MBR part table install to GPT? Possible?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: Failed to grow
  • From: Daniel Koch <koch@xxxxxxxxxxx>
• Re: Problems with Seagate 8TB SMR archive drives
  • From: Tejas Rao <raot@xxxxxxx>
• Re: Problems with Seagate 8TB SMR archive drives
  • From: Jeff Johnson <jeff.johnson@xxxxxxxxxxxxxxxxx>
• Re: Problems with Seagate 8TB SMR archive drives
  • From: Tejas Rao <raot@xxxxxxx>
• [PATCH 3.10 34/35] md/bitmap: return an error when bitmap superblock is corrupt.
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Problems with Seagate 8TB SMR archive drives
  • From: Tejas Rao <raot@xxxxxxx>
• [PATCH 3.14 43/44] md/bitmap: return an error when bitmap superblock is corrupt.
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Patch "md/bitmap: return an error when bitmap superblock is corrupt." has been added to the 3.10-stable tree
  • From: <gregkh@xxxxxxxxxxxxxxxxxxx>
• Patch "md/bitmap: return an error when bitmap superblock is corrupt." has been added to the 3.14-stable tree
  • From: <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH stable] md/bitmap: return an error when bitmap superblock is corrupt.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH] drivers/md/md.c: ignore recovery_offset if bitmap exists
  • From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
• Re: Failed to grow
  • From: Daniel Koch <koch@xxxxxxxxxxx>
• Re: How will mdadm handle a wrongly added drive, when the original comes back on line?
  • From: "Wilson, Jonathan" <i400s@xxxxxxxxxxx>
• [PATCH stable] md/bitmap: return an error when bitmap superblock is corrupt.
  • From: NeilBrown <neilb@xxxxxxxx>
• [patch v2 06/11] raid5: add basic stripe log
  • From: Shaohua Li <shli@xxxxxx>
• [patch v2 11/11] raid5: enable log for raid array with cache disk
  • From: Shaohua Li <shli@xxxxxx>
• [patch v2 09/11] raid5: disable batch with log enabled
  • From: Shaohua Li <shli@xxxxxx>
• [patch v2 05/11] raid5: add a new state for stripe log handling
  • From: Shaohua Li <shli@xxxxxx>
• [patch v2 10/11] raid5: don't allow resize/reshape with cache(log) support
  • From: Shaohua Li <shli@xxxxxx>
• [patch v2 00/11]md: fix raid5 write hole
  • From: Shaohua Li <shli@xxxxxx>
• [patch v2 04/11] raid5: export some functions
  • From: Shaohua Li <shli@xxxxxx>
• [patch v2 08/11] raid5: log recovery
  • From: Shaohua Li <shli@xxxxxx>
• [patch v2 07/11] raid5: log reclaim support
  • From: Shaohua Li <shli@xxxxxx>
• [patch v2 03/11] md: override md superblock recovery_offset for journal device
  • From: Shaohua Li <shli@xxxxxx>
• [patch v2 02/11] MD: add a new disk role to present write journal device
  • From: Shaohua Li <shli@xxxxxx>
• [patch v2 01/11] MD: replace special disk roles with macros
  • From: Shaohua Li <shli@xxxxxx>
• Failed to grow
  • From: Daniel Koch <koch@xxxxxxxxxxx>
• Re: Rebuilding array
  • From: Can Jeuleers <can.jeuleers@xxxxxxxxx>
• Rebuilding array
  • From: Hans Malissa <hmalissa@xxxxxx>
• [PATCH v6 06/11] md/raid5: split bio for chunk_aligned_read
  • From: Ming Lin <mlin@xxxxxxxxxx>
• [PATCH v6 07/11] md/raid5: get rid of bio_fits_rdev()
  • From: Ming Lin <mlin@xxxxxxxxxx>
• [PATCH v6 08/11] block: kill merge_bvec_fn() completely
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH 7/9] raid5: don't allow resize/reshape with cache(log) support
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 5/9] raid5: log recovery
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 4/9] raid5: log reclaim support
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 3/9] raid5: add basic stripe log
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Problem with XOR Engine
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] block: don't access bio->bi_error after bio_put()
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] block: don't access bio->bi_error after bio_put()
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: Problem with XOR Engine
  • From: Carsten Aulbert <Carsten.Aulbert@xxxxxxxxxx>
• Problem with XOR Engine
  • From: Tarak Anumolu <tarak.a@xxxxxxxxxxx>
• Re: Need some information about mdadm 3.2.5
  • From: Tarak Anumolu <tarak.a@xxxxxxxxxxx>
• Re: RAID5 TRIM/DISCARD user land support (fstriim and mkfs)
  • From: Christian Balzer <chibi@xxxxxxx>
• Re: Need some information about mdadm 3.2.5
  • From: Tarak Anumolu <tarak.a@xxxxxxxxxxx>
• Problem with XOR Engine
  • From: Tarak <tarak.a@xxxxxxxxxxx>
• [PATCH] block: don't access bio->bi_error after bio_put()
  • From: Sasha Levin <sasha.levin@xxxxxxxxxx>
• Re: Re-add not selecting drive for correct slot?
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Re-add not selecting drive for correct slot?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Re-add not selecting drive for correct slot?
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Re-add not selecting drive for correct slot?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: RAID5 TRIM/DISCARD user land support (fstriim and mkfs)
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: RAID5 TRIM/DISCARD user land support (fstriim and mkfs)
  • From: Christian Balzer <chibi@xxxxxxx>
• Re: RAID5 TRIM/DISCARD user land support (fstriim and mkfs)
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• RAID5 TRIM/DISCARD user land support (fstriim and mkfs)
  • From: Christian Balzer <chibi@xxxxxxx>
• [PATCH V1 Resend 04/11] drivers: md: Drop unlikely before IS_ERR(_OR_NULL)
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: Re-add not selecting drive for correct slot?
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Re-add not selecting drive for correct slot?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Re-add not selecting drive for correct slot?
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• [Patch v1 3/4] md/raid5: STIPE_HANDLE bit in handle_strype_dirtying()
  • From: <stockhausen@xxxxxxxxxxx>
• [Patch v1 4/4] md/raid5: Fix rmw/rcw parametrization check
  • From: <stockhausen@xxxxxxxxxxx>
• [Patch v1 0/4] md/raid5: Cleanups for handle_stripe_dirtying()
  • From: <stockhausen@xxxxxxxxxxx>
• [Patch v1 2/4] md/raid5: simplify handle_strype_dirtying()
  • From: <stockhausen@xxxxxxxxxxx>
• [Patch v1 1/4] md/raid5: MAX_DISKS define
  • From: <stockhausen@xxxxxxxxxxx>
• Re: Re-add not selecting drive for correct slot?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re-add not selecting drive for correct slot?
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: [dm-devel] kernel BUG at drivers/scsi/scsi_lib.c:1101! observed during md5sum for one file on (RAID4->RAID0) device
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [dm-devel] kernel BUG at drivers/scsi/scsi_lib.c:1101! observed during md5sum for one file on (RAID4->RAID0) device
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• Re: raid1 (re)-add recovery data corruption
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• Re: [PATCH 7/9] raid5: don't allow resize/reshape with cache(log) support
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 5/9] raid5: log recovery
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 4/9] raid5: log reclaim support
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 3/9] raid5: add basic stripe log
  • From: Shaohua Li <shli@xxxxxx>
• Re: RAID 6 reshape/grow interrupted
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: RAID 6 reshape/grow interrupted
  • From: George Rapp <george.rapp@xxxxxxxxx>
• read errors aren't corrected
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: RAID 6 reshape/grow interrupted
  • From: George Rapp <george.rapp@xxxxxxxxx>
• RAID 6 reshape/grow interrupted
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Re: [PATCH 9/9] raid5: skip resync if cache(log) is enabled
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 7/9] raid5: don't allow resize/reshape with cache(log) support
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 5/9] raid5: log recovery
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 4/9] raid5: log reclaim support
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 4/9] raid5: log reclaim support
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 3/9] raid5: add basic stripe log
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 2/9] md: override md superblock recovery_offset for cache device
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 1/9] MD: add a new disk role to present cache device
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 1/9] MD: add a new disk role to present cache device
  • From: NeilBrown <neilb@xxxxxxxx>
• [GIT PULL REQUEST] md updates for 4.2-rc
  • From: NeilBrown <neilb@xxxxxxxx>
• ANNOUNCE: mdadm 3.3.4 - A tool for managing md Soft RAID under Linux
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: raid5: handle_stripe_dirtying
  • From: NeilBrown <neilb@xxxxxxxx>
• raid5: handle_stripe_dirtying
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• RE: [PATCH 1/9] MD: add a new disk role to present cache device
  • From: Song Liu <songliubraving@xxxxxx>
• Re: RAID1 degraded
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: RAID1 degraded
  • From: Anthonys Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/9] md: override md superblock recovery_offset for cache device
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/9] MD: add a new disk role to present cache device
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] Safeguard against writing to an active device of another node
  • From: Guoqing Jiang <gqJiang@xxxxxxxx>
• Re: [PATCH 1/2] Safeguard against writing to an active device of another node
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] Make cmap_* also has same policy as dlm_*
  • From: Guoqing Jiang <gqJiang@xxxxxxxx>
• Re: [PATCH 1/2] Safeguard against writing to an active device of another node
  • From: Guoqing Jiang <gqJiang@xxxxxxxx>
• Re: RAID1 degraded
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID1 degraded
  • From: Hans Malissa <hmalissa@xxxxxx>
• Re: RAID1 degraded
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID1 degraded
  • From: Hans Malissa <hmalissa@xxxxxx>
• Re: RAID1 degraded
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: How will mdadm handle a wrongly added drive, when the original comes back on line?
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• RAID1 degraded
  • From: Hans Malissa <hmalissa@xxxxxx>
• How will mdadm handle a wrongly added drive, when the original comes back on line?
  • From: "Wilson, Jonathan" <i400s@xxxxxxxxxxx>
• Re: [PATCH 2/2] Make cmap_* also has same policy as dlm_*
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxx>
• Re: [PATCH 1/2] Safeguard against writing to an active device of another node
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxx>
• Re: Thoughts on big SSD arrays?
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• [PATCH 2/2] Make cmap_* also has same policy as dlm_*
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 1/2] Safeguard against writing to an active device of another node
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• AW: Thoughts on big SSD arrays?
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: [PATCH 3/3] Safeguard against writing to an active device of another node
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 3/3] Safeguard against writing to an active device of another node
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Thoughts on big SSD arrays?
  • From: Pasi Kärkkäinen <pasik@xxxxxx>
• Thoughts on big SSD arrays?
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: [V2 PATCH] Safeguard against writing to an active device of another node
  • From: Guoqing Jiang <gqJiang@xxxxxxxx>
• Re: raid5 regression in 4.1.x
  • From: Tomas Papan <tomas.papan@xxxxxxxxx>
• [PATCH 06/15] drivers: md: Drop unlikely before IS_ERR(_OR_NULL)
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [dm-devel] kernel BUG at drivers/scsi/scsi_lib.c:1101! observed during md5sum for one file on (RAID4->RAID0) device
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: raid1_end_read_request does not retry failed READ from a recovering drive
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Subject: ANNOUNCE: mdadm 3.3.3 - A tool for managing md Soft RAID under Linux
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: raid5 regression in 4.1.x
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: kernel BUG at drivers/scsi/scsi_lib.c:1101! observed during md5sum for one file on (RAID4->RAID0) device
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• raid1 (re)-add recovery data corruption
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• Re: [V2 PATCH] Safeguard against writing to an active device of another node
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxx>
• kernel BUG at drivers/scsi/scsi_lib.c:1101! observed during md5sum for one file on (RAID4->RAID0) device
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• [V2 PATCH] Safeguard against writing to an active device of another node
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 3/3] Safeguard against writing to an active device of another node
  • From: Guoqing Jiang <gqJiang@xxxxxxxx>
• Re: [PATCH 3/3] Safeguard against writing to an active device of another node
  • From: Guoqing Jiang <gqJiang@xxxxxxxx>
• Re: [PATCH 3/3] Safeguard against writing to an active device of another node
  • From: Guoqing Jiang <gqJiang@xxxxxxxx>
• Re: [PATCH 3/3] Safeguard against writing to an active device of another node
  • From: Guoqing Jiang <gqJiang@xxxxxxxx>
• [PATCH 5/9] raid5: log recovery
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 4/9] raid5: log reclaim support
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 1/9] MD: add a new disk role to present cache device
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 7/9] raid5: don't allow resize/reshape with cache(log) support
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 8/9] raid5: enable log for raid array with cache disk
  • From: Shaohua Li <shli@xxxxxx>