Lines Matching refs:device
12 #include <linux/device-mapper.h>
42 * The block size of the device holding pool data must be
61 * snapshot. They are just two device trees that happen to point to the
81 * effects the btree of that specific device. Btrees for the other
83 * device as it was after the last commit is untouched, ie. we're using
103 * will continue to think that data block in the snapshot device is shared
194 * A pool device ties together a metadata device and a data device. It
671 * This section of code contains the logic for processing a thin device's IO.
767 * on the metadata device.
979 * metadata device.
1508 DMWARN("%s: reached low water mark for data device: sending event.",
1581 * If we have run out of space, queue bios until the device is
2409 * The data device was flushed as part of metadata commit,
2840 * If discard_passdown was enabled verify that the data device
2860 DMWARN("Data device (%pg) %s: Disabling discard passdown.", data_bdev, reason);
3098 *error = "metadata device already in use by a pool";
3102 *error = "data device already in use by a pool";
3199 DMWARN("%s: reached low water mark for metadata device: sending event.",
3206 * We need to flush the data device **before** committing the metadata.
3233 DMWARN("Metadata device %pg is larger than %u sectors: excess space will not be used.",
3258 * userland should respond by growing the metadata device. We could let
3266 * device deletion which is harmless if it fails (just retry the
3267 * delete after you've grown the device).
3283 * no_discard_passdown: don't pass discards down to the data device
3316 ti->error = "Error setting metadata or data device";
3335 ti->error = "Error opening metadata block device";
3342 ti->error = "Error getting data device";
3378 * device changes.
3397 * them down to the data device. The thin device's discard
3471 DMERR("%s: failed to retrieve data device size",
3484 DMERR("%s: unable to grow the data device until repaired.",
3490 DMINFO("%s: growing the data device from %llu to %llu blocks",
3518 DMERR("%s: failed to retrieve metadata device size",
3524 DMERR("%s: metadata device (%llu blocks) too small: expected %llu",
3531 DMERR("%s: unable to grow the metadata device until repaired.",
3537 DMINFO("%s: growing the metadata device from %llu to %llu blocks",
3557 * Retrieves the number of blocks of the data device from
3558 * the superblock and compares it to the actual device size,
3559 * thus resizing the data device in case it has grown.
3565 * grown the data device in reaction to a table event.
3700 DMWARN("Message received with invalid device id: %s", arg);
3720 DMWARN("Creation of new thinly-provisioned device with id %s failed.",
3748 DMWARN("Creation of new snapshot %s of device %s failed.",
3771 DMWARN("Deletion of thin device %s failed.", argv[1]);
4063 * This is especially beneficial when the pool's data device is a RAID
4064 * device that has a full stripe width that matches pool->sectors_per_block
4102 * device. DM core has already set this up.
4107 * block layer will stack them if pool's data device has support.
4179 * dev_id: the internal device identifier
4180 * origin_dev: a device external to the pool that should act as the origin
4182 * If the pool device has discards disabled, they get disabled for the thin
4183 * device as well.
4215 ti->error = "Error setting origin device";
4222 ti->error = "Error opening origin device";
4230 ti->error = "Error opening pool device";
4236 ti->error = "Invalid device id";
4243 ti->error = "Couldn't get pool mapped device";
4257 ti->error = "Couldn't open thin device, Pool is in fail mode";
4264 ti->error = "Couldn't open thin internal device";
4291 ti->error = "Unable to activate thin device while pool is suspended";