Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • 1
    And right now any backups taken before "shutting down" may possibly simply backup corrupted data, though in this situation it is more likely that file system meta-data is corrupted, rather than file contents. Commented Mar 5, 2013 at 16:39
  • I'm afraid you are going to lose at least some of the data in any case. Turning the host off physically or terminating the VMs forcefully might have the unwanted consequence of messing up everything (i.e. even those file systems that are only mounted once). I would probably try to terminate everything as cleanly as possible to minimise the losses. And of course making sure it doesn't happen again. Commented Mar 5, 2013 at 20:59
  • As for preventing it, IIUC you might try to set permissions on the device in dom0 once it is opened by the guest, but since fs permissions (on the device files) can be crossed by root (unless you have a patched kernel) it might not need to help. Commented Mar 5, 2013 at 21:36
  • 1
    Regarding your post script: if the devices are visible through multiple paths then the kernel probably doesn't even know that they are all the same device, so how could it "reserve" it? As for exporting a device from dom0 to multiple domUs, it lets you do that because you might actually want to do it on purpose (e.g. with a filesystem that supports it, or mounted read-only everywhere). Commented Mar 5, 2013 at 22:06
  • @Celada I thought aboust that, but there are ways of "locking" devices: PowerPath should (does in the case of Solaris) reserve all the parent-paths of a device (At the time it initializes). Additionally SCSI "reserve" commands are managed by the target device, so once a target is reserved, it should refuse to allow a reserve against any of the paths for that device. At least that is my limited understanding. Commented Mar 6, 2013 at 4:19