MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "SELinux_Policy_Writing",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "59": {
                "pageid": 59,
                "ns": 0,
                "title": "Remove Logical Volume",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "In this example, we will use a logical volume Ldata in volume group Vdata, mounted to mount point /data.\n\n\nTo remove a logical volume, first you must ensure that the machine will not attempt to mount a device that no longer exists on boot. On modern RHEL7 machines, this will freeze during the next boot and go into maintenance mode, which is a potential headache. So, to not have that happen, edit /etc/fstab and comment it out or remove the line entirely:\n\n<code># vi /etc/fstab</code>\n <nowiki>#/dev/Vdata/Ldata      /data           ext4    defaults    0 0</nowiki>\n\nNext, unmount it:\n\n<code># umount /data</code>\n\nYou should now see that a <code>mount -a</code> will not remount the device. You may want to remove the mount point folder as well:\n\n<code># rmdir /data</code>\n\nEven though the LV is unmounted, the kernel will still keep the device operational, and will prompt you if you are certain you want to remove an active logical volume. To stop this prompt, you can deactivate the LV with:\n\n<code># lvchange -an /dev/Vdata/Ldata</code>\n\nThis also makes sure that the device truly is not in use. If you are having trouble deactivating the LV, then you may need to look at the untested section below, or restart the machine to clean up the device handles. If you don't do this, you'll see the following prompt after executing this command to remove the LV:\n\n<code># lvremove Vdata/ackbar</code>\n <nowiki>Do you really want to remove active logical volume Vdata/Ldata? [y/n]: y\n  Logical volume \"Ldata\" successfully removed</nowiki>\n\nThe logical volume is now removed."
                    }
                ]
            },
            "55": {
                "pageid": 55,
                "ns": 0,
                "title": "Remove Multipath Block Device",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "= Removing path/device =\n\nLet's take an example where the paths have already been closed from the SAN, and see see this from using multipath:\n\n<code># multipath -ll </code>\n <nowiki>sdb: checker msg is \"tur checker reports path is down\"\nsdd: checker msg is \"tur checker reports path is down\"\nsystem (3600508b4001078340000d00004c10000) dm-0 HP,HSV210\n[size=25G][features=1 queue_if_no_path][hwhandler=0]\n\\_ round-robin 0 [prio=100][active]\n \\_ 0:0:6:1 sdc 8:32  [active][ready]\n \\_ 0:0:7:1 sdd 8:48  [failed][faulty]\n \\_ 1:0:6:1 sdg 8:96  [active][ready]\n\\_ round-robin 0 [prio=20][enabled]\n \\_ 0:0:4:1 sda 8:0   [active][ready]\n \\_ 0:0:5:1 sdb 8:16  [failed][faulty]\n \\_ 1:0:4:1 sde 8:64  [active][ready]</nowiki>\n\nWe see that this block device is still operating, but that two paths have been removed, one from each fabric. The unpresented devices are sdb and sdd, thus to remove them:\n\n<code># multipathd -k\"del path sdb\"</code>\n\n<code># multipathd -k\"del path sdd\"</code>\n\nThen remove the devices from the kernel block device list:\n\n<code># echo 1 > /sys/block/sdb/device/delete</code>\n\n<code># echo 1 > /sys/block/sdd/device/delete</code>\n\nFinally, restart multipathd:\n\n<code># /etc/init.d/multipathd restart</code>\n\n<code>#  multipath -ll</code>\n\n <nowiki>system (3600508b4001078340000d00004c10000) dm-0 HP,HSV210\n[size=25G][features=1 queue_if_no_path][hwhandler=0]\n\\_ round-robin 0 [prio=100][active]\n \\_ 0:0:6:1 sdc 8:32  [active][ready]\n \\_ 1:0:6:1 sdg 8:96  [active][ready]\n\\_ round-robin 0 [prio=20][enabled]\n \\_ 0:0:4:1 sda 8:0   [active][ready]\n \\_ 1:0:4:1 sde 8:64  [active][ready]</nowiki>\n\n== Alternative (untested!) approach ==\nIf things get really stuck, then you might have some luck with dmsetup.\n\nIf \"multipath -ll\" shows failed disks (that have been unpresented properly), use dmsetup to remove the failed disk with the command:\n\n<code># dmsetup remove <device></code>\n\nwhere <device> is \"mpath<num>\".\n\nFind the stuck one from the output of multipath -ll; be sure you've got the right mpath device.\nOptionally, if you've got stuck lvmdiskscan or pvdisplay type processes (trying to access the missing disk), then the \"remove\" will fail, claiming the device is in use (which, in some senses, it is).\n\nIn this case, double check you've got the right mpath device (otherwise you'll fsck your system), and run:\n\n<code># dmsetup remove \\--force <device></code>\n\nThis will claim failure (device-mapper: remove ioctl failed: Device or resource busy), but if you now run\n<code># dmsetup info <device></code>\n\nthen you'll see the \"Open count\" has gone to zero.&nbsp; You can now run the plain remove one more time:\n\n<code># dmsetup remove <device></code>\n\nand it will be removed.\n\nYour hung processes will finally die the death they deserve, and the unpresented disk will be unknown to the system any longer."
                    }
                ]
            }
        }
    }
}