Skip to content

Manipulating (pre-)existing thin-pool devices not backed by LinearDevs #943

Closed

Description

@ckatsak

Hello! Thank you for maintaining this work :)

As far as I can tell, the high-level crate (devicemapper) cannot be employed to manipulate (pre-)existing thin-pool devices present in the system, unless they are backed by LinearDev block devices. Otherwise, no corresponding ThinPoolDev can be instantiated (e.g., via ThinPoolDev::setup()).

For example, no valid ThinPoolDev can be instantiated for the following:

# dmsetup table dm-thinpool -v
Name:              dm-thinpool
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE & INACTIVE
Open count:        0
Event number:      0
Major, minor:      254, 0
Number of targets: 1

0 104857600 thin-pool 7:1 7:0 128 32768 1 skip_block_zeroing

since its data & metadata devices are loop devices (major number 7).

Is that right, or am I missing something?

I hope I'm asking this at the right place. Thanks!

Activity

  1. locked and limited conversation to collaborators on Nov 15, 2024
  2. converted this issue into a discussion #945 on Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions