Re: [qubes-users] Re: Restoring VM causes drive to fill but it isn't full..

2016-11-14 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Nov 13, 2016 at 11:12:36PM -0800, Drew White wrote:
> On Monday, 14 November 2016 17:19:43 UTC+11, Drew White  wrote:
> > Hi folks,
> > 
> > 
> > I'm trying to restore a guest.
> > I have / which has 2.1 GB free. (The root drive where things exist)
> > Then I have my /var/lib/qubes with 78 GB free. (drive which contains all my 
> > Guests)
> > 
> > I try to restore a guest which takes up ~ 48 GB.
> > 
> > Upon initialising the restore script, my / drive starts to fill up 
> > completely.
> > And then the software says it has errors (specifically, no space left on 
> > drive).
> > 
> > It's already extracted a file list to the correct directory on 
> > /var/lib/qubes.
> > 
> > Why does it tell me the drive is full when there is over 78 GB free and it 
> > should be using /var/lib/qubes not / ?
> > 
> > Is this a bug in the Qubes Restore?
> 
> Only way I found to work around this bug is to perform the following..
> 
> On secondary drive create a directory for holding information..
> Get to the second stage of the restore.
> Open the /var/tmp directory.
> Delete the restore_XX directory
> Create a link of that name in the /var/tmp directory that links to the 
> directory on the other drive.
> 
> Doing this meant that the actual usage of drive space never went over 200 MB 
> for that folder.
> 
> The system was unable to extract the menus and apps.templates directory and a 
> few other meaningless things that wouldn't prevent the system from working.
> 
> Why when it's targeting in your /var/tmp directory does it absorb the / disk 
> drive in a matter of seconds?
> 
> Is it just a bug in the code somewhere?
> Or is it a file system thing?
> Or is it the "stick-bit" ?
> 
> I created a new directory there with no sticky bit, and the entire restore 
> utility couldn't extract to that directory.
> 
> Only way around it was to create the new directory and link it to a folder on 
> the storage drive.

Yes, /var/tmp is used to restore the data and there is (currently) no
option to use alternative location. So you method with symlinking
/var/tmp is currently one of the best what you can do...

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJYKinCAAoJENuP0xzK19csTKsH/jU+LocZh9XnubGW0lcPGP+k
abQqZoJ5MMzcAbEoT3zRSCJwyS5sPs28vCIAPOAThSj8DYtVOG/V8k4ZV1XCKcOR
5C8ScAfAd/6m8ruNGw3vipATy4taEAWXK5vgdB5z2PvdnpLptMYgCIsQF81+fCB/
dFhFkecGYww2StRRVXY2xLTqG2k+Og9jX9lm16KVY8A1h+F+dhAdgZPwphI66JpW
JiiHC98GEr5naLvEGKJTjm4R1sPPvGmmZsbRGHfD9Q0T6v3B2wCDdbVAzPC2r5sA
gSE4DS30luVYN9UPL6futzEqAbgrRGxMJIhsWeDfJ+oc58ZknMWl3FIXEay750g=
=CoOJ
-END PGP SIGNATURE-

-- 
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/20161114211650.GB3417%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Restoring VM causes drive to fill but it isn't full..

2016-11-13 Thread Drew White
On Monday, 14 November 2016 17:19:43 UTC+11, Drew White  wrote:
> Hi folks,
> 
> 
> I'm trying to restore a guest.
> I have / which has 2.1 GB free. (The root drive where things exist)
> Then I have my /var/lib/qubes with 78 GB free. (drive which contains all my 
> Guests)
> 
> I try to restore a guest which takes up ~ 48 GB.
> 
> Upon initialising the restore script, my / drive starts to fill up completely.
> And then the software says it has errors (specifically, no space left on 
> drive).
> 
> It's already extracted a file list to the correct directory on /var/lib/qubes.
> 
> Why does it tell me the drive is full when there is over 78 GB free and it 
> should be using /var/lib/qubes not / ?
> 
> Is this a bug in the Qubes Restore?

Only way I found to work around this bug is to perform the following..

On secondary drive create a directory for holding information..
Get to the second stage of the restore.
Open the /var/tmp directory.
Delete the restore_XX directory
Create a link of that name in the /var/tmp directory that links to the 
directory on the other drive.

Doing this meant that the actual usage of drive space never went over 200 MB 
for that folder.

The system was unable to extract the menus and apps.templates directory and a 
few other meaningless things that wouldn't prevent the system from working.

Why when it's targeting in your /var/tmp directory does it absorb the / disk 
drive in a matter of seconds?

Is it just a bug in the code somewhere?
Or is it a file system thing?
Or is it the "stick-bit" ?

I created a new directory there with no sticky bit, and the entire restore 
utility couldn't extract to that directory.

Only way around it was to create the new directory and link it to a folder on 
the storage drive.

-- 
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/311204ce-cba2-4c7f-934e-585045c8663c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.