messages from 2011-07-14 05:42:31 to 2011-07-22 07:13:20 UTC [more...]
mdadm striped parity RAID with Advanced Format drives
2011-07-22 7:13 UTC (6+ messages)
[md PATCH 00/34] md patches for 3.1 - part 1
2011-07-22 7:09 UTC (48+ messages)
` [md PATCH 01/34] md/raid10: get rid of duplicated conditional expression
` [md PATCH 02/34] md/raid10: factor out common bio handling code
` [md PATCH 03/34] md/raid10: share pages between read and write bio's during recovery
` [md PATCH 09/34] md/raid5: move common code into handle_stripe
` [md PATCH 04/34] md/raid5: use kmem_cache_zalloc()
` [md PATCH 08/34] md/raid5: replace sh->lock with an 'active' flag
` [md PATCH 06/34] md/raid5: Remove use of sh->lock in sync_request
` [md PATCH 07/34] md/raid5: Protect some more code with ->device_lock
` [md PATCH 10/34] md/raid5: unify stripe_head_state and r6_state
` [md PATCH 11/34] md/raid5: add some more fields to stripe_head_state
` [md PATCH 05/34] md/raid5: get rid of duplicated call to bio_data_dir()
` [md PATCH 18/34] md/raid5: move more common code into handle_stripe
` [md PATCH 19/34] md/raid5: move some "
` [md PATCH 17/34] md/raid5: unite handle_stripe_dirtying5 and handle_stripe_dirtying6
` [md PATCH 13/34] md/raid5: Move code for finishing a reconstruction into handle_stripe
` [md PATCH 16/34] md/raid5: unite fetch_block5 and fetch_block6
` [md PATCH 15/34] md/raid5: rearrange a test in fetch_block6
` [md PATCH 14/34] md/raid5: move more code into common handle_stripe
` [md PATCH 12/34] md/raid5: move stripe_head_state and more code into handle_stripe
` [md PATCH 22/34] md/raid: use printk_ratelimited instead of printk_ratelimit
` [md PATCH 27/34] md/raid10: Improve decision on whether to fail a device with a read error
` [md PATCH 26/34] md/raid10: Make use of new recovery_disabled handling
` [md PATCH 20/34] md/raid5: finalise new merged handle_stripe
` [md PATCH 23/34] md: introduce link/unlink_rdev() helpers
` [md PATCH 21/34] md: use proper little-endian bitops
` [md PATCH 24/34] md: remove ro check in md_check_recovery()
` [md PATCH 25/34] md: change managed of recovery_disabled
` [md PATCH 33/34] MD: raid1 s/sysfs_notify_dirent/sysfs_notify_dirent_safe
` [md PATCH 30/34] md/raid5: move rdev->corrected_errors counting
` [md PATCH 31/34] md/raid10: "
` [md PATCH 28/34] md: get rid of unnecessary casts on page_address()
` [md PATCH 29/34] md/raid1: move rdev->corrected_errors counting
` [md PATCH 34/34] MD bitmap: Revert DM dirty log hooks
` [md PATCH 32/34] md/raid5: Avoid BUG caused by multiple failures
standard performance (write speed 20Mb/s)
2011-07-22 7:08 UTC (15+ messages)
` standard performance (write speed ??Mb/s) - new raid5 array
[PATCH] RAID-6 check standalone
2011-07-22 6:41 UTC (14+ messages)
` [PATCH] RAID-6 check standalone code cleanup
` [PATCH] RAID-6 check standalone suspend array
` [PATCH] RAID-6 check standalone suspend array V2.0
Confusion with setting up new RAID6 with mdadm
2011-07-22 5:17 UTC (4+ messages)
[PATCH 1/1] md: style/readability cleanups
2011-07-22 4:42 UTC
linux-next: Tree for July 21 (drivers/md/dm-raid)
2011-07-22 1:14 UTC (4+ messages)
` [dm-devel] "
` [PATCH -next] dm: fix dm-flakey printk warning
standard performance (write speed 20Mb/s)
2011-07-22 0:24 UTC (11+ messages)
` standard performance (write speed 65Mb/s)
upgrading the superblock version
2011-07-21 15:44 UTC (2+ messages)
Raid5 boot failure after grow
2011-07-21 15:18 UTC (6+ messages)
[md PATCH 00/36] md patches for 3.1 - part 2: bad block logs
2011-07-21 2:58 UTC (37+ messages)
` [md PATCH 01/36] md: beginnings of bad block management
` [md PATCH 04/36] md: load/store badblock list from v1.x metadata
` [md PATCH 03/36] md: don't allow arrays to contain devices with bad blocks
` [md PATCH 02/36] md/bad-block-log: add sysfs interface for accessing bad-block-log
` [md PATCH 14/36] md/raid1: record badblocks found during resync etc
` [md PATCH 09/36] md: make it easier to wait for bad blocks to be acknowledged
` [md PATCH 13/36] md/raid1: Handle write errors by updating badblock log
` [md PATCH 05/36] md: Disable bad blocks and v0.90 metadata
` [md PATCH 11/36] md/raid1: clear bad-block record when write succeeds
` [md PATCH 10/36] md/raid1: avoid writing to known-bad blocks on known-bad drives
` [md PATCH 07/36] md/raid1: avoid reading known bad blocks during resync
` [md PATCH 12/36] md/raid1: store behind-write pages in bi_vecs
` [md PATCH 08/36] md: add 'write_error' flag to component devices
` [md PATCH 06/36] md/raid1: avoid reading from known bad blocks
` [md PATCH 18/36] md/raid5: use bad-block log to improve handling of uncorrectable read errors
` [md PATCH 19/36] md/raid5: write errors should be recorded as bad blocks if possible
` [md PATCH 23/36] md/raid10: Split handle_read_error out from raid10d
` [md PATCH 15/36] md/raid1: improve handling of read failure during recovery
` [md PATCH 20/36] md/raid5. Don't write to known bad block on doubtful devices
` [md PATCH 17/36] md/raid5: avoid reading from known bad blocks
` [md PATCH 24/36] md/raid10: avoid reading from known bad blocks - part 1
` [md PATCH 16/36] md/raid1: factor several functions out or raid1d()
` [md PATCH 21/36] md/raid5: Clear bad blocks on successful write
` [md PATCH 22/36] md/raid10: simplify/reindent some loops
` [md PATCH 30/36] md/raid10: clear bad-block record when write succeeds
` [md PATCH 33/36] md/raid10: record bad blocks due to write errors during resync/recovery
` [md PATCH 31/36] md/raid10: Handle write errors by updating badblock log
` [md PATCH 28/36] md/raid10 record bad blocks as needed during recovery
` [md PATCH 27/36] md/raid10: avoid reading known bad blocks during resync/recovery
` [md PATCH 26/36] md/raid10 - avoid reading from known bad blocks - part 3
` [md PATCH 32/36] md/raid10: attempt to fix read errors during resync/check
` [md PATCH 29/36] md/raid10: avoid writing to known bad blocks on known bad drives
` [md PATCH 25/36] md/raid10: avoid reading from known bad blocks - part 2
` [md PATCH 34/36] md/raid10: simplify read error handling during recovery
` [md PATCH 35/36] md/raid10: Handle read errors during recovery better
` [md PATCH 36/36] md/raid10: handle further errors during fix_read_error better
Problems with raid after reboot
2011-07-20 21:24 UTC
[PATCH] MD: generate an event when array sync is complete
2011-07-20 19:16 UTC (3+ messages)
RAID 1 using SSD and 2 HDD
2011-07-20 12:59 UTC (5+ messages)
[PATCH] mdadm.8: Disk coercion with IMSM metadata
2011-07-20 12:54 UTC (4+ messages)
Software RAID and TRIM
2011-07-20 12:25 UTC (34+ messages)
data corruption after rebuild
2011-07-20 8:20 UTC (11+ messages)
[PATCH] MD bitmap: Revert DM dirty log hooks
2011-07-20 2:07 UTC (2+ messages)
[PATCH] MD: raid1 s/sysfs_notify_dirent/sysfs_notify_dirent_safe
2011-07-20 1:47 UTC (2+ messages)
how to recover filesystem after clobbering array?
2011-07-19 12:44 UTC (6+ messages)
maybe a raid10 module issue?
2011-07-19 12:40 UTC
[PATCH] Grow: fix version number in error message
2011-07-19 4:34 UTC
SSDs vs. md/sync_speed_(min|max)
2011-07-18 18:42 UTC
md stuck while rebuilding?
2011-07-18 15:14 UTC
RAID5: failing an active component during spare rebuild - arrays hangs
2011-07-17 8:29 UTC (5+ messages)
possible bug in md
2011-07-14 16:17 UTC (5+ messages)
sys/time.h missing from linux/raid/pq.h for userspace builds
2011-07-14 14:15 UTC
Reinstall OS Without Disturbing Software Raid Array
2011-07-14 11:01 UTC (3+ messages)
[PATCH 0/3] count rdev->corrected_errors after final re-read
2011-07-14 5:54 UTC (3+ messages)
` [PATCH 3/3] md/raid10: move rdev->corrected_errors counting
[PATCH] md: get rid of unnecessary casts on page_address()
2011-07-14 5:44 UTC (2+ messages)
[PATCH] imsm: FIX: getinfo_super_imsm_volume() doesn't fill all disk information
2011-07-14 5:42 UTC (2+ messages)
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox