I have my disk set up as the following...
sda1 /boot
sda2 /
sda3 /var/lib/qubes
I also have
sda1 /boot
sda2 /
sdb1 /var/lib/qubes
Thing is, I used to be able to restore them and all, BEFORE I updated the
manager.
The only difference between 2 PCs is the version of the manager.
Why doesn't it restore to where I tell it to instead of trying to restore to
the tmp directory AS WELL as the location I say?
The whole methodology of it is just unknown.
It does one of 5+ different things when it stuffs up.
So multiple storage pools or not, doesn't matter.
On another PC I have several storage areas, and I just use links from the
/var/lib/qubes/*/{GUESTNAME} path to where the guests really are stored.
So just saying it's multiple storage pools is not really accurate as to the
issue. There is something more in-depth than that. It could fail on a drive
that has no partitions at all, and mine do at times.
There are also times when it expands the guests drives to 100% size instead of
being thinly provisioned.
HVM, AppVM, HVMTemplate, HVMTemplate converted to VMTemplate, or anything,
doesn't matter.
If you need more details, let me know.
There is A LOT that I can tell you about this one thing, restoring, that has
issues that have not been resolved.
On Thursday, 19 April 2018 09:29:59 UTC+10, Pablo Di Noto wrote:
> > This is completely unacceptable that you still have not resolved these bugs
> > I mentioned in Qubes version 2. Please fix!
>
> Quick question, were the VMs backed up from a Qubes install with multiple
> storage pools, by chance?
>
> I am about to create an issue about that as soon as I can grab proper logs.
> It looks very similar to your problem, and the very specific nature of the
> case can explain why it was never solved. Just a shot in the dark.
>
> Cheers,
> ///Pablo
>
> >
> > ================================================
> > Extracting data: 11.1 GiB to restore
> > ERROR: unable to extract files for
> > /var/tmp/restore_4y7IsA/vm31/private.img.027, tar output: tar:
> > vm31/private.img: Cannot write: No space left on device tar: Exiting with
> > failure status due to previous errors
> > Some errors occurred during data extraction, continuing anyway to restore
> > at least some VMs
> > -> Restoring QubesHVm win7x64...
> > -> Done. Please install updates for all the restored templates.
> > Please unmount your backup volume and cancel the file selection dialog.
> > Finished with errors!
> > ------------------------------------------------
> > There was 18 GB on the dive where I was restoring to.
> > 1. Why isn't it restoring to where it's meant to restore?
> > 2. Why is it restoring to the operating system partition?
> > 3. Why doesn't it check space BEFORE it starts?
> > 4. If there isn't enough space why doesn't it restore to where it's told to?
> >
> >
> > ================================================
> > Extracting data: 18.5 GiB to restore
> > Some errors occurred during data extraction, continuing anyway to restore
> > at least some VMs
> > -> Restoring QubesTemplateHVm Win7x64...
> > ERROR: VM private image file doesn't exist:
> > /var/lib/qubes/vm-templates/Win7x64/private.img
> > *** Skipping VM: Win7x64
> > -> Done. Please install updates for all the restored templates.
> > Please unmount your backup volume and cancel the file selection dialog.
> > Finished with errors!
> > ------------------------------------------------
> > private.img does exist in the archive/backup.
> > Why isn't it knowing that and restoring?
> >
> >
> > ================================================
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/3e29e6ac-2232-4a04-bfc5-9353db089316%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
