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

qvm-block allows attaching the same device twice #950

Closed
marmarek opened this issue Mar 8, 2015 · 1 comment
Closed

qvm-block allows attaching the same device twice #950

marmarek opened this issue Mar 8, 2015 · 1 comment
Labels
C: core P: major Priority: major. Between "default" and "critical" in severity. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@marmarek
Copy link
Member

marmarek commented Mar 8, 2015

Reported by marmarek on 9 Feb 2015 13:18 UTC
Steps to reproduce:

  1. add external hdd to daily appvm
~]$ qvm-block -a daily dom0:sde1
  1. list the device
...
dom0:sde1 (data) 488 GiB (attached to 'daily' as 'xvdi')
  1. mount at daily appvm
user ~]$ sudo mount /dev/xvdi /mnt
  1. accidentaly add to daily vm again on dom0
~]$ qvm-block -a daily dom0:sde1
~]$ qvm-block
...
dom0:sde1 (data) 488 GiB (attached to 'daily' as 'xvdj')
...

there is double add to daily (appVM) with double device mount point, but on daily (appVM) still mounted as /dev/xvdi , and we can mount again as /dev/xvdj

when delete on dom0

~]$ qvm-block -d dom0:sde1
~]$ qvm-block
...
dom0:sde1 (data) 488 GiB

but, on daily (appVM) still can access the mount point (rw mode) on /dev/xvdi when do umount at daily (appVM) , umount successful but on dom0 was not attached to any appVM

https://groups.google.com/d/msgid/qubes-users/2dd14e12-4a31-4b33-b505-48aaa48f1a02%40googlegroups.com

Migrated-From: https://wiki.qubes-os.org/ticket/950

@marmarek marmarek added this to the Release 2.1 (post R2) milestone Mar 8, 2015
@marmarek marmarek added T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. C: core P: major Priority: major. Between "default" and "critical" in severity. labels Mar 8, 2015
@marmarek
Copy link
Member Author

marmarek commented Oct 3, 2015

This may appear as the device is still there, because it is mounted, but in
fact any access to the device will fail. The only data still available is that
being cached by the kernel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: core P: major Priority: major. Between "default" and "critical" in severity. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

1 participant