/qubes-issues

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

qvm-grow-root can fail silently for a TemplateVM #2359

Open
jbwells opened this Issue Oct 2, 2016 · 0 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
  Release 3.2 updates
3 participants
@jbwells @andrewdavidwong @marmarek
@jbwells

jbwells commented Oct 2, 2016

Qubes OS version (e.g., R3.1):

R3.2-rc2 with all updates

Affected TemplateVMs (e.g., fedora-23, if applicable):

debian-8 (probably all templates)

Expected behavior:

"qvm-grow-root --allow-start debian-8 12G" should either grow the filesystem or give an error message.

Actual behavior:

It fails silently if any AppVMs based on the TemplateVM are running.

Steps to reproduce the behavior:

  1. Create an AppVM based on debian-8 (or probably any template).
  2. Start that AppVM.
  3. Run "qvm-grow-root --allow-start debian-8 12G".
  4. Observe that the command in step 3 gives the appearance of having succeeded.
  5. Observe that the filesystem in debian-8 is not any bigger.

General notes:

Until you stop all the AppVMs that use the TemplateVM and then restart the TemplateVM, the TemplateVM wlll think the partition has not grown any larger, and it therefore won't grow the filesystem when resize2fs is run.

I haven't checked whether qubes-manager handles this case any better.

Related issues:

@andrewdavidwong andrewdavidwong added bug C: core labels Oct 2, 2016

@andrewdavidwong andrewdavidwong added this to the Release 3.2 milestone Oct 2, 2016

@marmarek marmarek modified the milestones: Release 3.2, Release 3.2 updates Nov 19, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment