)]}' { "log": [ { "commit": "327372797c88b24953f454cd51a3734c02697bdd", "tree": "e7f7e3dff1415817b31af76d746240d80772b448", "parents": [ "b12d437b73d32203a41fde0d407e91812c866844" ], "author": { "name": "Jonathan Brassow", "email": "jbrassow@redhat.com", "time": "Tue Aug 02 12:32:07 2011 +0100" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Tue Aug 02 12:32:07 2011 +0100" }, "message": "dm raid: add md raid1 support\n\nSupport the MD RAID1 personality through dm-raid.\n\nSigned-off-by: Jonathan Brassow \u003cjbrassow@redhat.com\u003e\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" }, { "commit": "b12d437b73d32203a41fde0d407e91812c866844", "tree": "3c7a33f4a45779da4a5edb71678ce7f8ae4169e7", "parents": [ "46bed2b5c16bb7c82e1088d7ae75fb958c8a8c4e" ], "author": { "name": "Jonathan Brassow", "email": "jbrassow@redhat.com", "time": "Tue Aug 02 12:32:07 2011 +0100" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Tue Aug 02 12:32:07 2011 +0100" }, "message": "dm raid: support metadata devices\n\nAdd the ability to parse and use metadata devices to dm-raid. Although\nnot strictly required, without the metadata devices, many features of\nRAID are unavailable. They are used to store a superblock and bitmap.\n\nThe role, or position in the array, of each device must be recorded in\nits superblock. This is to help with fault handling, array reshaping,\nand sanity checks. RAID 4/5/6 devices must be loaded in a specific order:\nin this way, the \u0027array_position\u0027 field helps validate the correctness\nof the mapping when it is loaded. It can be used during reshaping to\nidentify which devices are added/removed. Fault handling is impossible\nwithout this field. For example, when a device fails it is recorded in\nthe superblock. If this is a RAID1 device and the offending device is\nremoved from the array, there must be a way during subsequent array\nassembly to determine that the failed device was the one removed. This\nis done by correlating the \u0027array_position\u0027 field and the bit-field\nvariable \u0027failed_devices\u0027.\n\nSigned-off-by: Jonathan Brassow \u003cjbrassow@redhat.com\u003e\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" }, { "commit": "46bed2b5c16bb7c82e1088d7ae75fb958c8a8c4e", "tree": "bab932a8eec324ca470407ff54097d86a3c0e27f", "parents": [ "c1084561bb85da3630540ebe951749a8cd8fc714" ], "author": { "name": "Jonathan Brassow", "email": "jbrassow@redhat.com", "time": "Tue Aug 02 12:32:07 2011 +0100" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Tue Aug 02 12:32:07 2011 +0100" }, "message": "dm raid: add write_mostly parameter\n\nAdd the write_mostly parameter to RAID1 dm-raid tables.\n\nThis allows the user to set the WriteMostly flag on a RAID1 device that\nshould normally be avoided for read I/O.\n\nSigned-off-by: Jonathan Brassow \u003cjbrassow@redhat.com\u003e\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" }, { "commit": "c1084561bb85da3630540ebe951749a8cd8fc714", "tree": "ecdefcf24dd88f4c19a873fa5d26039a0edf03a7", "parents": [ "c0a2fa1ef1057a1e9450d6f055f1cde2ad4f85a2" ], "author": { "name": "Jonathan Brassow", "email": "jbrassow@redhat.com", "time": "Tue Aug 02 12:32:07 2011 +0100" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Tue Aug 02 12:32:07 2011 +0100" }, "message": "dm raid: add region_size parameter\n\nAllow the user to specify the region_size.\n\nEnsures that the supplied value meets md\u0027s constraints, viz. the number of\nregions does not exceed 2^21.\n\nSigned-off-by: Jonathan Brassow \u003cjbrassow@redhat.com\u003e\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" }, { "commit": "3e8dbb7f3966c80d77272f8b4f430babc99f6595", "tree": "00192da87f8e5db890bd5c6dab9c941a905b294e", "parents": [ "2ca4c92f58f9386e080b26f9ccd78c9ca5825a42" ], "author": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Tue Aug 02 12:32:03 2011 +0100" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Tue Aug 02 12:32:03 2011 +0100" }, "message": "dm raid: tidy includes\n\nA dm target only needs to use include/linux dm headers.\n\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" }, { "commit": "13c87583ea4e867211fc3e7edab750c353c47c95", "tree": "93d1a2b20f1033e031eedf86a19ab822b1fbb576", "parents": [ "a2d2b0345a0f30c169b7d08b8cebdd4853fcb0f8" ], "author": { "name": "Jonathan Brassow", "email": "jbrassow@redhat.com", "time": "Tue Aug 02 12:32:03 2011 +0100" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Tue Aug 02 12:32:03 2011 +0100" }, "message": "dm raid: cleanup parameter handling\n\nRe-order the parameters so they are handled consistently in the same order\nwhere defined, parsed and output.\n\nOnly include rebuild parameters in the STATUSTYPE_TABLE output if they were\nsupplied in the original table line.\n\nCorrect the parameter count when outputting rebuild: there are two words,\nnot one.\n\nUse case-independent checks for keywords (as in other device-mapper targets).\n\nSigned-off-by: Jonathan Brassow \u003cjbrassow@redhat.com\u003e\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" }, { "commit": "af1db72d8b340f97ad12b60175afdef43e6f0e60", "tree": "c6f3d18bda596d136fdf9f7ba9e2a2ed1fdedc3b", "parents": [ "e1dfa0a29737142c32f00a3bac0f609dc85b4a82" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Apr 18 18:25:41 2011 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Apr 18 18:25:41 2011 +1000" }, "message": "md/dm - remove remains of plug_fn callback.\n\nNow that unplugging is done differently, the unplug_fn callback is\nnever called, so it can be completely discarded.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "7eaceaccab5f40bbfda044629a6298616aeaed50", "tree": "33954d12f63e25a47eb6d86ef3d3d0a5e62bf752", "parents": [ "73c101011926c5832e6e141682180c4debe2cf45" ], "author": { "name": "Jens Axboe", "email": "jaxboe@fusionio.com", "time": "Thu Mar 10 08:52:07 2011 +0100" }, "committer": { "name": "Jens Axboe", "email": "jaxboe@fusionio.com", "time": "Thu Mar 10 08:52:07 2011 +0100" }, "message": "block: remove per-queue plugging\n\nCode has been converted over to the new explicit on-stack plugging,\nand delay users have been converted to use the new API for that.\nSo lets kill off the old plugging along with aops-\u003esync_page().\n\nSigned-off-by: Jens Axboe \u003cjaxboe@fusionio.com\u003e\n" }, { "commit": "9d09e663d5502c46f2d9481c04c1087e1c2da698", "tree": "993f10eb7100a6ce8c00c0cff7951d7ffea9488e", "parents": [ "99d03c141b40914b67d63c9d23b8da4386422ed7" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jan 13 20:00:02 2011 +0000" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Thu Jan 13 20:00:02 2011 +0000" }, "message": "dm: raid456 basic support\n\nThis patch is the skeleton for the DM target that will be\nthe bridge from DM to MD (initially RAID456 and later RAID1). It\nprovides a way to use device-mapper interfaces to the MD RAID456\ndrivers.\n\nAs with all device-mapper targets, the nominal public interfaces are the\nconstructor (CTR) tables and the status outputs (both STATUSTYPE_INFO\nand STATUSTYPE_TABLE). The CTR table looks like the following:\n\n1: \u003cs\u003e \u003cl\u003e raid \\\n2:\t\u003craid_type\u003e \u003c#raid_params\u003e \u003craid_params\u003e \\\n3:\t\u003c#raid_devs\u003e \u003cmeta_dev1\u003e \u003cdev1\u003e .. \u003cmeta_devN\u003e \u003cdevN\u003e\n\nLine 1 contains the standard first three arguments to any device-mapper\ntarget - the start, length, and target type fields. The target type in\nthis case is \"raid\".\n\nLine 2 contains the arguments that define the particular raid\ntype/personality/level, the required arguments for that raid type, and\nany optional arguments. Possible raid types include: raid4, raid5_la,\nraid5_ls, raid5_rs, raid6_zr, raid6_nr, and raid6_nc. (again, raid1 is\nplanned for the future.) The list of required and optional parameters\nis the same for all the current raid types. The required parameters are\npositional, while the optional parameters are given as key/value pairs.\nThe possible parameters are as follows:\n \u003cchunk_size\u003e\t\tChunk size in sectors.\n [[no]sync]\t\tForce/Prevent RAID initialization\n [rebuild \u003cidx\u003e]\tRebuild the drive indicated by the index\n [daemon_sleep \u003cms\u003e]\tTime between bitmap daemon work to clear bits\n [min_recovery_rate \u003ckB/sec/disk\u003e]\tThrottle RAID initialization\n [max_recovery_rate \u003ckB/sec/disk\u003e]\tThrottle RAID initialization\n [max_write_behind \u003cvalue\u003e]\t\tSee \u0027-write-behind\u003d\u0027 (man mdadm)\n [stripe_cache \u003csectors\u003e]\t\tStripe cache size for higher RAIDs\n\nLine 3 contains the list of devices that compose the array in\nmetadata/data device pairs. If the metadata is stored separately, a \u0027-\u0027\nis given for the metadata device position. If a drive has failed or is\nmissing at creation time, a \u0027-\u0027 can be given for both the metadata and\ndata drives for a given position.\n\nExamples:\n# RAID4 - 4 data drives, 1 parity\n# No metadata devices specified to hold superblock/bitmap info\n# Chunk size of 1MiB\n# (Lines separated for easy reading)\n0 1960893648 raid \\\n\traid4 1 2048 \\\n\t5 - 8:17 - 8:33 - 8:49 - 8:65 - 8:81\n\n# RAID4 - 4 data drives, 1 parity (no metadata devices)\n# Chunk size of 1MiB, force RAID initialization,\n#\tmin recovery rate at 20 kiB/sec/disk\n0 1960893648 raid \\\n raid4 4 2048 min_recovery_rate 20 sync\\\n 5 - 8:17 - 8:33 - 8:49 - 8:65 - 8:81\n\nPerforming a \u0027dmsetup table\u0027 should display the CTR table used to\nconstruct the mapping (with possible reordering of optional\nparameters).\n\nPerforming a \u0027dmsetup status\u0027 will yield information on the state and\nhealth of the array. The output is as follows:\n1: \u003cs\u003e \u003cl\u003e raid \\\n2:\t\u003craid_type\u003e \u003c#devices\u003e \u003c1 health char for each dev\u003e \u003cresync_ratio\u003e\n\nLine 1 is standard DM output. Line 2 is best shown by example:\n\t0 1960893648 raid raid4 5 AAAAA 2/490221568\nHere we can see the RAID type is raid4, there are 5 devices - all of\nwhich are \u0027A\u0027live, and the array is 2/490221568 complete with recovery.\n\nCc: linux-raid@vger.kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nSigned-off-by: Jonathan Brassow \u003cjbrassow@redhat.com\u003e\nSigned-off-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" } ] }