search

QubesOS / qubes-issues

The Qubes OS Project issue tracker
https://www.qubes-os.org/doc/issue-tracking/
542 stars 48 forks source link

LVM pool can’t activate LVs with activationskip flag #9579

Closed DemiMarie closed 1 week ago

DemiMarie commented 1 week ago

How to file a helpful issue

Qubes OS release

R4.3 git main but probably affects R4.2 too

Brief summary

The LVM pool does not pass the --ignoreactivationskip flag to lvchange --activate=y, so volumes with the activation skip flag cannot be activated.

Steps to reproduce

Set the “activation skip” flag on an LV.

Expected behavior

Everything works since QubesOS/qubes-core-admin@6dffbf9363a5539d89fccdc007ef7fd199ccb5c2

Actual behavior

Activation does not work.

marmarek commented 1 week ago

Did you hit this issue somewhere? How have you arrived at such situation? Volumes we care about are created with --setactivationskip=n already.

DemiMarie commented 1 week ago

Did you hit this issue somewhere?

No.

How have you arrived at such situation?

I have not. I saw that --ignoreactivationskip was not passed and assumed that it should be.

Volumes we care about are created with --setactivationskip=n already.

Correct, but what if there is a volume that does not have this flag?

marmarek commented 1 week ago

Correct, but what if there is a volume that does not have this flag?

It means somebody has removed it, probably intentionally. We shouldn't override this.

github-actions[bot] commented 1 week ago

This issue has been closed as "not applicable." Here are some common examples of cases in which issues are closed as not applicable:

We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.

Regarding help and support requests, please note that this issue tracker (qubes-issues) is not intended to serve as a help desk or tech support center. Instead, we've set up other venues where you can ask for help and support, ask questions, and have discussions. By contrast, the issue tracker is more of a technical tool intended to support our developers in their work. We thank you for your understanding.

If anyone reading this believes that this issue was closed in error or that the resolution of "not applicable" is not accurate, please leave a comment below saying so, and we will review this issue again. For more information, see How issues get closed.