Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BACKPORT][v1.6.1][BUG][1.6.0] ENGINE v2 : disk /dev/xxxx is already used by AIO bdev disk-x #8133

Closed
github-actions bot opened this issue Mar 7, 2024 · 2 comments
Assignees
Labels
area/v2-data-engine v2 data engine (SPDK) kind/backport Backport request kind/bug require/backport Require backport. Only used when the specific versions to backport have not been definied. require/qa-review-coverage Require QA to review coverage
Milestone

Comments

@github-actions
Copy link

github-actions bot commented Mar 7, 2024

backport #8129

@github-actions github-actions bot added area/v2-data-engine v2 data engine (SPDK) kind/backport Backport request kind/bug require/backport Require backport. Only used when the specific versions to backport have not been definied. require/qa-review-coverage Require QA to review coverage labels Mar 7, 2024
@github-actions github-actions bot added this to the v1.6.1 milestone Mar 7, 2024
@derekbit derekbit self-assigned this Mar 9, 2024
@longhorn-io-github-bot
Copy link

longhorn-io-github-bot commented Mar 9, 2024

Pre Ready-For-Testing Checklist

  • Where is the reproduce steps/test steps documented?
    The reproduce steps/test steps are at:
  1. Enable v2-data-engine
  2. Create two block devices such as loop devices
  3. Add the two disks to block-type disks
  4. One of the two disks shows the error message ... is already used by AIO bdev ... in node.status.diskStatus

After the fix, the two disks can be added successfully.

  • Does the PR include the explanation for the fix or the feature?

  • Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)?
    The PR is at

longhorn/longhorn-instance-manager#430

  • Which areas/issues this PR might have potential impacts on?
    Area: v2 volume
    Issues

@chriscchien chriscchien self-assigned this Mar 11, 2024
@chriscchien
Copy link
Contributor

Verified pass on longhorn v1.6.x(longhorn-instance-manager 7a1637) with test steps

Can add two block devices as block-type disks on the same longhorn node without problem

    disk-3:
      conditions:
      - lastProbeTime: ""
        lastTransitionTime: "2024-03-11T07:28:13Z"
        message: Disk disk-3(/dev/loop5) on node ip-172-31-44-108 is ready
        reason: ""
        status: "True"
        type: Ready
      - lastProbeTime: ""
        lastTransitionTime: "2024-03-11T07:28:13Z"
        message: Disk disk-3(/dev/loop5) on node ip-172-31-44-108 is schedulable
        reason: ""
        status: "True"
        type: Schedulable
      diskType: block
      diskUUID: a5017ece-5d7d-47f3-b4d9-65cc3006be27
      filesystemType: ""
      scheduledReplica: {}
      storageAvailable: 10590617600
      storageMaximum: 10694426624
      storageScheduled: 0
    disk-4:
      conditions:
      - lastProbeTime: ""
        lastTransitionTime: "2024-03-11T08:18:43Z"
        message: Disk disk-4(/dev/loop7) on node ip-172-31-44-108 is ready
        reason: ""
        status: "True"
        type: Ready
      - lastProbeTime: ""
        lastTransitionTime: "2024-03-11T08:18:43Z"
        message: Disk disk-4(/dev/loop7) on node ip-172-31-44-108 is schedulable
        reason: ""
        status: "True"
        type: Schedulable
      diskType: block
      diskUUID: f33fa13f-e07d-41e7-827b-f6dc2e90af2d
      filesystemType: ""
      scheduledReplica: {}
      storageAvailable: 10590617600
      storageMaximum: 10694426624
      storageScheduled: 0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/v2-data-engine v2 data engine (SPDK) kind/backport Backport request kind/bug require/backport Require backport. Only used when the specific versions to backport have not been definied. require/qa-review-coverage Require QA to review coverage
Projects
None yet
Development

No branches or pull requests

3 participants