[qubes-users] Backup error file too large ?
Every backup test show "Error : Writing backup to VM X failed : cat:write error: File Too large. I put USB disk on VM and active de backup Qubes os. Then, I have this error. -- 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/f6f2b38c-561a-4c79-95dd-33de3acfb5ad%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup Error: Warning: unrecognized data found in configuration files
Eccentric Butterfly: Speaking of which, is there really any security benefit in making sure the backup is not connected to a network? Provided the encryption password is secure. I don't think this was mentioned in the docs anywhere as something to consider so it's probably a bit excessive on my part. Of course, provided the password is long and secure. Since all contents of all AppVMs you select pass through your Backup VM, it's a good idea in general to be cautious about attaching it to a network if you don't have to. Same with any other AppVM, really. Security benefit is that it makes it harder to exfiltrate data. -- 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/4c5c021a-8375-5e0a-0cc6-704cc6484e92%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup Error: Warning: unrecognized data found in configuration files
On Monday, 6 May 2019 17:14:46 UTC+1, daniel wrote: > On Sun, 5 May 2019 20:24:07 + > "'awokd' via qubes-users" wrote: > > > Eccentric Butterfly: > > > When I go to backup my Qubes, the backup screen shows a red error > > > at the bottom of the window saying "Warning: unrecognized data > > > found in configuration files". > > I ran into this and it was innocuous. Probably you have deleted a qube > that you backed up the last time you ran backup. The system remembers > the choices you made in the last backup and sets them up as the > defaults. So it knows it is supposed to backup a qube that isn't there > anymore. So it says it's confused. You can follow awokd's advice > (the file will be recreated when you run backup; it is where the > previous-backup settings are stored). Or you can just ignore the > message and continue with your backup. I'd delete the file, just in > case something more serious is happening. > > Best Wishes, > Daniel > > > /etc/qubes/backup/qubes-manager-backup.conf" in dom0 terminal. This > > will delete the configuration you saved last time you ran backup. > > > > > Why is this? Is there anything I need to do? Will this have any > > > effect on my ability to backup and restore? > > Haven't seen it before so don't know if it would prevent backups or > > restores. > > Thanks for your reply guys. I think it's a mix of what both of you are saying. When I backup qubes to a hard drive, I make sure the qube is not connected to a network. When I'm done, I usually delete the qube. Though in this case, it wasn't deleted (or I re-made the qube with the same name). but it also wasn't running. When I saw the contents of that file, I realised the path in the 'BACKUP' qube was no longer valid as 1) the qube was not running and 2) the hard drive would not be mounted. Thus, I ran the qube and mounted it and the error was gone. Thanks for your help, it was much appreciated! Butterfly. -- 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/f1d22ab5-6296-47fb-8e7c-eb5fe6ed4243%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup Error: Warning: unrecognized data found in configuration files
On Monday, 6 May 2019 22:35:55 UTC+1, Eccentric Butterfly wrote: > On Monday, 6 May 2019 17:14:46 UTC+1, daniel wrote: > > On Sun, 5 May 2019 20:24:07 + > > "'awokd' via qubes-users" wrote: > > > > > Eccentric Butterfly: > > > > When I go to backup my Qubes, the backup screen shows a red error > > > > at the bottom of the window saying "Warning: unrecognized data > > > > found in configuration files". > > > > I ran into this and it was innocuous. Probably you have deleted a qube > > that you backed up the last time you ran backup. The system remembers > > the choices you made in the last backup and sets them up as the > > defaults. So it knows it is supposed to backup a qube that isn't there > > anymore. So it says it's confused. You can follow awokd's advice > > (the file will be recreated when you run backup; it is where the > > previous-backup settings are stored). Or you can just ignore the > > message and continue with your backup. I'd delete the file, just in > > case something more serious is happening. > > > > Best Wishes, > > Daniel > > > > > /etc/qubes/backup/qubes-manager-backup.conf" in dom0 terminal. This > > > will delete the configuration you saved last time you ran backup. > > > > > > > Why is this? Is there anything I need to do? Will this have any > > > > effect on my ability to backup and restore? > > > Haven't seen it before so don't know if it would prevent backups or > > > restores. > > > > > > Thanks for your reply guys. I think it's a mix of what both of you are saying. > > When I backup qubes to a hard drive, I make sure the qube is not connected to > a network. When I'm done, I usually delete the qube. Though in this case, it > wasn't deleted (or I re-made the qube with the same name). but it also wasn't > running. > > When I saw the contents of that file, I realised the path in the 'BACKUP' > qube was no longer valid as 1) the qube was not running and 2) the hard drive > would not be mounted. Thus, I ran the qube and mounted it and the error was > gone. > > Thanks for your help, it was much appreciated! > Butterfly. Speaking of which, is there really any security benefit in making sure the backup is not connected to a network? Provided the encryption password is secure. I don't think this was mentioned in the docs anywhere as something to consider so it's probably a bit excessive on my part. Of course, provided the password is long and secure. -- 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/22534478-c0e4-4428-adcf-35baa15aa4ce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup Error: Warning: unrecognized data found in configuration files
On Sun, 5 May 2019 20:24:07 + "'awokd' via qubes-users" wrote: > Eccentric Butterfly: > > When I go to backup my Qubes, the backup screen shows a red error > > at the bottom of the window saying "Warning: unrecognized data > > found in configuration files". I ran into this and it was innocuous. Probably you have deleted a qube that you backed up the last time you ran backup. The system remembers the choices you made in the last backup and sets them up as the defaults. So it knows it is supposed to backup a qube that isn't there anymore. So it says it's confused. You can follow awokd's advice (the file will be recreated when you run backup; it is where the previous-backup settings are stored). Or you can just ignore the message and continue with your backup. I'd delete the file, just in case something more serious is happening. Best Wishes, Daniel > /etc/qubes/backup/qubes-manager-backup.conf" in dom0 terminal. This > will delete the configuration you saved last time you ran backup. > > > Why is this? Is there anything I need to do? Will this have any > > effect on my ability to backup and restore? > Haven't seen it before so don't know if it would prevent backups or > restores. > -- 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/20190506111437.6a563379%40allcock.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup Error: Warning: unrecognized data found in configuration files
Eccentric Butterfly: When I go to backup my Qubes, the backup screen shows a red error at the bottom of the window saying "Warning: unrecognized data found in configuration files". Try closing backup, then "rm /etc/qubes/backup/qubes-manager-backup.conf" in dom0 terminal. This will delete the configuration you saved last time you ran backup. Why is this? Is there anything I need to do? Will this have any effect on my ability to backup and restore? Haven't seen it before so don't know if it would prevent backups or restores. -- 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/2d59434f-6304-3753-ab5a-509f2dbc7194%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Backup Error: Warning: unrecognized data found in configuration files
When I go to backup my Qubes, the backup screen shows a red error at the bottom of the window saying "Warning: unrecognized data found in configuration files". Why is this? Is there anything I need to do? Will this have any effect on my ability to backup and restore? -- 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/aabae889-1b34-494d-b6fb-777c3ca5ec7d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Backup Error: Warning: unrecognized data found in configuration files
When I go to backup Qubes, the backup screen shows a red error at the bottom of the window saying "Warning: unrecognized data found in configuration files" -- 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/5f7742b1-5a8a-49e7-8f30-b1c3dfdae324%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup Error
> Likely the filesystem (FAT?) on the destination cannot handle files over > a certain size. You may want to reformat it with a native Linux fs like > Ext4. > > -- > > Chris Laprise, tas...@openmailbox.org > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 That was indeed the issue, thanks for the insight and suggestion! -- 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/81bc0cac-c133-49ec-9974-1c3872dd555c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup Error
On Friday, March 17, 2017 at 3:31:37 PM UTC-4, Chris Laprise wrote: > On 03/17/2017 02:55 PM, jimmy.dack...@gmail.com wrote: > > I'm trying out the backup feature in Qubes but getting an error. > > > > I'm trying to save VMs totaling 22.4GB in size on a USB stick with 63GB > > free. > > > > At 19% progress is get: > > "[Dom0] Backup error! > > ERROR: Failed to write the backup, VM output: cat: write error: File too > > large." > > > > Is there a maximum file size for backups? A RAM limitation (I have 8GB RAM > > and when I do the backup about 6GB is free)? Something else I'm not > > thinking of? > > > > I am able to do a small backup, such as just Dom0 itself. > > > > Also a general question about backups: if I do a backup and then restore, > > will it add what I backed up to what is already on the system? Or > > completely overwrite everything? For example, if I have 10 VMs and backup > > 3, then restore the 3, will it just overwrite those three and leave the > > other 7 alone? Or will I only have those 3 and the other 7 are wiped out? > > > > Likely the filesystem (FAT?) on the destination cannot handle files over > a certain size. You may want to reformat it with a native Linux fs like > Ext4. > 5Bp9975@cB%m0wkX > -- > > Chris Laprise, tas...@openmailbox.org > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 That was indeed the issue, thanks for the insight! -- 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/fd093e5a-5e9b-4330-a11e-3f783b09bc3b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup Error
On 2017-03-17 11:55, jimmy.dack...@gmail.com wrote: I'm trying out the backup feature in Qubes but getting an error. I'm trying to save VMs totaling 22.4GB in size on a USB stick with 63GB free. At 19% progress is get: "[Dom0] Backup error! ERROR: Failed to write the backup, VM output: cat: write error: File too large." Is there a maximum file size for backups? A RAM limitation (I have 8GB RAM and when I do the backup about 6GB is free)? Something else I'm not thinking of? I am able to do a small backup, such as just Dom0 itself. Also a general question about backups: if I do a backup and then restore, will it add what I backed up to what is already on the system? Or completely overwrite everything? For example, if I have 10 VMs and backup 3, then restore the 3, will it just overwrite those three and leave the other 7 alone? Or will I only have those 3 and the other 7 are wiped out? Also, be sure you didn't make the mistake I made once. I (stupidly) mounted by backup USB stick in Dom0. Then, when backing up Dom0, it tried to back up all the data on the backup stick, which of course kept increasing in size as more stuff got backed up onto it. I've since learned to use a USBVM, and mount the stick in a dedicated BackupVM. -- 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/10747aff541781e0d2738fb6c6ca7f97%40nowlas.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup Error
On Fri, Mar 17, 2017 at 03:31:24PM -0400, Chris Laprise wrote: > On 03/17/2017 02:55 PM, jimmy.dack...@gmail.com wrote: > >I'm trying out the backup feature in Qubes but getting an error. > > > >I'm trying to save VMs totaling 22.4GB in size on a USB stick with 63GB free. > > > >At 19% progress is get: > >"[Dom0] Backup error! > >ERROR: Failed to write the backup, VM output: cat: write error: File too > >large." > > > >Is there a maximum file size for backups? A RAM limitation (I have 8GB RAM > >and when I do the backup about 6GB is free)? Something else I'm not thinking > >of? > > > >I am able to do a small backup, such as just Dom0 itself. > > > >Also a general question about backups: if I do a backup and then restore, > >will it add what I backed up to what is already on the system? Or completely > >overwrite everything? For example, if I have 10 VMs and backup 3, then > >restore the 3, will it just overwrite those three and leave the other 7 > >alone? Or will I only have those 3 and the other 7 are wiped out? > > > > Likely the filesystem (FAT?) on the destination cannot handle files over a > certain size. You may want to reformat it with a native Linux fs like Ext4. > To answer your general question, the restore operation will tell you there is an existing qube with the same name and wont allow you to overwrite it. It certainly wont delete qubes not included in the restore. As always the command line tool offers many more options and more granular control - it still wont act on qubes not involved in the restore operation, (unless you are doing something to their template obviously.) unman -- 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/20170317212124.GC1810%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup Error
On 03/17/2017 02:55 PM, jimmy.dack...@gmail.com wrote: I'm trying out the backup feature in Qubes but getting an error. I'm trying to save VMs totaling 22.4GB in size on a USB stick with 63GB free. At 19% progress is get: "[Dom0] Backup error! ERROR: Failed to write the backup, VM output: cat: write error: File too large." Is there a maximum file size for backups? A RAM limitation (I have 8GB RAM and when I do the backup about 6GB is free)? Something else I'm not thinking of? I am able to do a small backup, such as just Dom0 itself. Also a general question about backups: if I do a backup and then restore, will it add what I backed up to what is already on the system? Or completely overwrite everything? For example, if I have 10 VMs and backup 3, then restore the 3, will it just overwrite those three and leave the other 7 alone? Or will I only have those 3 and the other 7 are wiped out? Likely the filesystem (FAT?) on the destination cannot handle files over a certain size. You may want to reformat it with a native Linux fs like Ext4. -- Chris Laprise, tas...@openmailbox.org https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/07c70ef9-0e9f-336b-1c04-2c2920d55e72%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Backup Error
I'm trying out the backup feature in Qubes but getting an error. I'm trying to save VMs totaling 22.4GB in size on a USB stick with 63GB free. At 19% progress is get: "[Dom0] Backup error! ERROR: Failed to write the backup, VM output: cat: write error: File too large." Is there a maximum file size for backups? A RAM limitation (I have 8GB RAM and when I do the backup about 6GB is free)? Something else I'm not thinking of? I am able to do a small backup, such as just Dom0 itself. Also a general question about backups: if I do a backup and then restore, will it add what I backed up to what is already on the system? Or completely overwrite everything? For example, if I have 10 VMs and backup 3, then restore the 3, will it just overwrite those three and leave the other 7 alone? Or will I only have those 3 and the other 7 are wiped out? -- 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/ec923dfc-2611-4523-a7f8-61470f64725c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup error - where is the log?
If I install a second Qubes system on a different partition - is there any way to copy the VMs from the first one? Because that was my goal with the backups. It is possible that the lack of space somehow corrupted the system - and that is the reason for the problems with backups - so maybe there is any other way to do that? Z. -- 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/CAGL_UUvMPW%3D6LteSw_gA3C%2B3jVyNbruc8BvuCRinfjy6c-77BQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup error - where is the log?
I removed some templates - and now there is no error about no disk space - but when restoring I still get the same error. It might be indeed about the path fed to tar - because when creating the archive I also get errors when I try to archive to a file in the current dir without giving the full path - it looks like the variable base_backup_dir does not get initialized, see below for the output. Backing up worked when I gave it a full path - still failing at restoring time. Z. == [zby@dom0 ~]$ qvm-backup -x dom0 -x anon-whonix -x sys-net -x sys-firewall -x sys-whonix -x python-anaconda backup --+--+--+ VM | type | size | --+--+--+ untrusted |AppVM | 16.0 KiB | personal |AppVM |0 | myovm |AppVM | 5.0 GiB | my-new-vm |AppVM | 9.9 GiB | exch |AppVM |315.8 MiB | --+--+--+ Total size: |15.1 GiB | --+--+--+ VMs not selected for backup: anon-whonix debian-8 debian-8-python dom0 fedora-23 fedora-23-dvm python-anaconda sys-firewall sys-net sys-whonix whonix-gw whonix-ws Traceback (most recent call last): File "/usr/bin/qvm-backup", line 218, in main() File "/usr/bin/qvm-backup", line 141, in main stat = os.statvfs(os.path.dirname(base_backup_dir)) OSError: [Errno 2] No such file or directory: '' On Fri, Feb 24, 2017 at 9:27 AM, Marek Marczykowski-Góreckiwrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Fri, Feb 24, 2017 at 08:23:00AM -0500, Zbigniew Łukasiak wrote: >> Ok - I tried the command line version - the output is below. The same >> error I see in ~/.xsession-errors. It looks to work correctly with the >> symlinked tmp - but still fails somehow - maybe the archive is >> corrupted. >> >> I tried to re-make the bacup from commandline, and this reports >> "qvm-backup: export error: [Errno 28] No space left on device" - even >> though I have enough space on both the /home and the /var/tmp >> partitions. See below for details - I mounted quite a big partition on >> /var/tmp. Maybe it somehow still uses the root partition. I did not >> see that error when running backup from Qubes Manager - but maybe the >> problem was still there and it was corrupting the backup. >> >> >> >> >> [zby@dom0 ~]$ qvm-backup-restore qubes-2017-02-22T111605 --verify-only >> --debug >> Please enter the passphrase to verify and (if encrypted) decrypt the backup: >> Checking backup content... >> Working in temporary dir:/var/tmp/restore_RxbZ1b >> Extracting data: 1.0 MiB to restore >> Run command[u'tar', u'-ixvf', 'qubes-2017-02-22T111605', u'-C', >> u'/var/tmp/restore_RxbZ1b', u'backup-header', u'backup-header.hmac', >> u'qubes.xml.000', u'qubes.xml.000.hmac'] >> Got backup header and hmac: backup-header, backup-header.hmac >> Verifying file /var/tmp/restore_RxbZ1b/backup-header >> Loading hmac for file /var/tmp/restore_RxbZ1b/backup-header >> File verification OK -> Sending file /var/tmp/restore_RxbZ1b/backup-header >> Creating pipe in: /var/tmp/restore_RxbZ1b/restore_pipe >> Getting new file:qubes.xml.000 >> Getting hmac:qubes.xml.000.hmac >> Verifying file /var/tmp/restore_RxbZ1b/qubes.xml.000 >> Started sending thread >> Moving to dir /var/tmp/restore_RxbZ1b >> Loading hmac for file /var/tmp/restore_RxbZ1b/qubes.xml.000 >> File verification OK -> Sending file /var/tmp/restore_RxbZ1b/qubes.xml.000 >> Getting new file: >> Waiting for the extraction process to finish...Extracting file >> /var/tmp/restore_RxbZ1b/qubes.xml.000 >> >> Running command [u'tar', u'-xkv', >> u'../../../../var/tmp/restore_RxbZ1b/qubes.xml'] > > This path looks strange. AFAIR it's calculated as "path to > /var/tmp/restore_RxbZ1b/qubes.xml, relative to /var/tmp/restore_RxbZ1b". > Have you actually mounted something on /var/tmp, or used a symlink? You > can use mount --bind if you don't want to mount the whole device there. > And be sure do to it before launching qvm-backup-restore, not during it. > >> === >> >> >> [zby@dom0 ~]$ df >> Filesystem 1K-blocks Used Available Use% Mounted on >> devtmpfs 2002988 0 2002988 0% /dev >> tmpfs2014408308256 1706152 16% /dev/shm >> tmpfs2014408 1316 2013092 1% /run >> tmpfs2014408 0 2014408 0% /sys/fs/cgroup >> /dev/dm-1 95989516 92623640 0 100% / > > Having / full is a problem anyway. Even if large files are placed in > /var/tmp. You need to clean up something - maybe old content of > /var/tmp? Or some old logs in /var/log? > >> tmpfs201440852 2014356 1% /tmp >> xenstore
Re: [qubes-users] Backup error - where is the log?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Feb 24, 2017 at 08:23:00AM -0500, Zbigniew Łukasiak wrote: > Ok - I tried the command line version - the output is below. The same > error I see in ~/.xsession-errors. It looks to work correctly with the > symlinked tmp - but still fails somehow - maybe the archive is > corrupted. > > I tried to re-make the bacup from commandline, and this reports > "qvm-backup: export error: [Errno 28] No space left on device" - even > though I have enough space on both the /home and the /var/tmp > partitions. See below for details - I mounted quite a big partition on > /var/tmp. Maybe it somehow still uses the root partition. I did not > see that error when running backup from Qubes Manager - but maybe the > problem was still there and it was corrupting the backup. > > > > > [zby@dom0 ~]$ qvm-backup-restore qubes-2017-02-22T111605 --verify-only --debug > Please enter the passphrase to verify and (if encrypted) decrypt the backup: > Checking backup content... > Working in temporary dir:/var/tmp/restore_RxbZ1b > Extracting data: 1.0 MiB to restore > Run command[u'tar', u'-ixvf', 'qubes-2017-02-22T111605', u'-C', > u'/var/tmp/restore_RxbZ1b', u'backup-header', u'backup-header.hmac', > u'qubes.xml.000', u'qubes.xml.000.hmac'] > Got backup header and hmac: backup-header, backup-header.hmac > Verifying file /var/tmp/restore_RxbZ1b/backup-header > Loading hmac for file /var/tmp/restore_RxbZ1b/backup-header > File verification OK -> Sending file /var/tmp/restore_RxbZ1b/backup-header > Creating pipe in: /var/tmp/restore_RxbZ1b/restore_pipe > Getting new file:qubes.xml.000 > Getting hmac:qubes.xml.000.hmac > Verifying file /var/tmp/restore_RxbZ1b/qubes.xml.000 > Started sending thread > Moving to dir /var/tmp/restore_RxbZ1b > Loading hmac for file /var/tmp/restore_RxbZ1b/qubes.xml.000 > File verification OK -> Sending file /var/tmp/restore_RxbZ1b/qubes.xml.000 > Getting new file: > Waiting for the extraction process to finish...Extracting file > /var/tmp/restore_RxbZ1b/qubes.xml.000 > > Running command [u'tar', u'-xkv', > u'../../../../var/tmp/restore_RxbZ1b/qubes.xml'] This path looks strange. AFAIR it's calculated as "path to /var/tmp/restore_RxbZ1b/qubes.xml, relative to /var/tmp/restore_RxbZ1b". Have you actually mounted something on /var/tmp, or used a symlink? You can use mount --bind if you don't want to mount the whole device there. And be sure do to it before launching qvm-backup-restore, not during it. > === > > > [zby@dom0 ~]$ df > Filesystem 1K-blocks Used Available Use% Mounted on > devtmpfs 2002988 0 2002988 0% /dev > tmpfs2014408308256 1706152 16% /dev/shm > tmpfs2014408 1316 2013092 1% /run > tmpfs2014408 0 2014408 0% /sys/fs/cgroup > /dev/dm-1 95989516 92623640 0 100% / Having / full is a problem anyway. Even if large files are placed in /var/tmp. You need to clean up something - maybe old content of /var/tmp? Or some old logs in /var/log? > tmpfs201440852 2014356 1% /tmp > xenstore 2014408 240 2014168 1% /var/lib/xenstored > /dev/sda11 1889292184884 1590388 11% /boot > /dev/dm-3 288243040 67263564 206314468 25% /home > tmpfs 402884 0402884 0% /run/user/991 > tmpfs 402884 8402876 1% /run/user/1000 > /dev/sda7 272256456 167991052 90412476 66% /home/zby/tmp - -- 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 iQEcBAEBCAAGBQJYsELWAAoJENuP0xzK19cs4sIH/3xTOfvVJ3RmfzdoXAfz85Z2 QH1loLH347X5omAENt+4HwhzlTq84LZFGKwRWMEgSDQUuj67saas711x5+ybH47N riswwTJfRC6SrEKPO27/QIN/JSGhCi1h+kmco9UxQSvaovSD0iSBoHsUui2iSvfL 4JfszFiWWVAsOZJu2nJdFOQPH7e69yKBC/hwMX+6PhP+FbhgmT8QZtIm6qWu3NGA n69O00exgPVKVjv1zhz1QoBzZn9J/MCq+N5vx/Ur6zVb8dD7+Vwu/3fvMFeuxKbx PJ7XXUQgVuiTxxc3GNfk0nrJqLSSAbn6HAmXDY6rtpcdXt1PyaYZDoxQkKtKJtY= =nXLP -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/20170224142730.GO1146%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Backup error - where is the log?
Ok - I tried the command line version - the output is below. The same error I see in ~/.xsession-errors. It looks to work correctly with the symlinked tmp - but still fails somehow - maybe the archive is corrupted. I tried to re-make the bacup from commandline, and this reports "qvm-backup: export error: [Errno 28] No space left on device" - even though I have enough space on both the /home and the /var/tmp partitions. See below for details - I mounted quite a big partition on /var/tmp. Maybe it somehow still uses the root partition. I did not see that error when running backup from Qubes Manager - but maybe the problem was still there and it was corrupting the backup. [zby@dom0 ~]$ qvm-backup-restore qubes-2017-02-22T111605 --verify-only --debug Please enter the passphrase to verify and (if encrypted) decrypt the backup: Checking backup content... Working in temporary dir:/var/tmp/restore_RxbZ1b Extracting data: 1.0 MiB to restore Run command[u'tar', u'-ixvf', 'qubes-2017-02-22T111605', u'-C', u'/var/tmp/restore_RxbZ1b', u'backup-header', u'backup-header.hmac', u'qubes.xml.000', u'qubes.xml.000.hmac'] Got backup header and hmac: backup-header, backup-header.hmac Verifying file /var/tmp/restore_RxbZ1b/backup-header Loading hmac for file /var/tmp/restore_RxbZ1b/backup-header File verification OK -> Sending file /var/tmp/restore_RxbZ1b/backup-header Creating pipe in: /var/tmp/restore_RxbZ1b/restore_pipe Getting new file:qubes.xml.000 Getting hmac:qubes.xml.000.hmac Verifying file /var/tmp/restore_RxbZ1b/qubes.xml.000 Started sending thread Moving to dir /var/tmp/restore_RxbZ1b Loading hmac for file /var/tmp/restore_RxbZ1b/qubes.xml.000 File verification OK -> Sending file /var/tmp/restore_RxbZ1b/qubes.xml.000 Getting new file: Waiting for the extraction process to finish...Extracting file /var/tmp/restore_RxbZ1b/qubes.xml.000 Running command [u'tar', u'-xkv', u'../../../../var/tmp/restore_RxbZ1b/qubes.xml'] Removing file /var/tmp/restore_RxbZ1b/qubes.xml.000 ERROR: unable to extract files for /var/tmp/restore_RxbZ1b/qubes.xml.000.(u'', u'tar: ../../../../var/tmp/restore_RxbZ1b/qubes.xml: Not found in archive\n\ntar: Exiting with failure status due to previous errors\n') Tar command output: %s Process ExtractWorker3-1: Traceback (most recent call last): File "/usr/lib64/python2.7/multiprocessing/process.py", line 258, in _bootstrap self.run() File "/usr/lib64/python2.7/site-packages/qubes/backup.py", line 931, in run self.__run__() File "/usr/lib64/python2.7/site-packages/qubes/backup.py", line 1251, in __run__ "\n".join(self.tar2_stderr QubesException: unable to extract files for /var/tmp/restore_RxbZ1b/qubes.xml.000.(u'', u'tar: ../../../../var/tmp/restore_RxbZ1b/qubes.xml: Not found in archive\n\ntar: Exiting with failure status due to previous errors\n') Tar command output: %s Extraction process finished with code:1 ERROR: unable to extract the qubes backup. Check extracting process errors. === [zby@dom0 ~]$ df Filesystem 1K-blocks Used Available Use% Mounted on devtmpfs 2002988 0 2002988 0% /dev tmpfs2014408308256 1706152 16% /dev/shm tmpfs2014408 1316 2013092 1% /run tmpfs2014408 0 2014408 0% /sys/fs/cgroup /dev/dm-1 95989516 92623640 0 100% / tmpfs201440852 2014356 1% /tmp xenstore 2014408 240 2014168 1% /var/lib/xenstored /dev/sda11 1889292184884 1590388 11% /boot /dev/dm-3 288243040 67263564 206314468 25% /home tmpfs 402884 0402884 0% /run/user/991 tmpfs 402884 8402876 1% /run/user/1000 /dev/sda7 272256456 167991052 90412476 66% /home/zby/tmp [zby@dom0 ~]$ qvm-backup -x dom0 -x untrusted -x anon-whonix -x vault -x personal -x work -x sys-net -x sys-firewall -x sys-whonix back -x python-anaconda --debug --+--+--+ VM | type | size | --+--+--+ myovm |AppVM | 5.0 GiB | my-new-vm |AppVM | 9.8 GiB | <-- The VM is running, please shut it down before proceeding with the backup! exch |AppVM |316.0 MiB | <-- The VM is running, please shut it down before proceeding with the backup! qvm-backup: export error: [Errno 28] No space left on device --+--+--+ Total size: |15.1 GiB | --+--+--+ VMs not selected for backup: anon-whonix debian-8 debian-8-python dom0 fedora-23 fedora-23-dvm personal python-anaconda sys-firewall sys-net sys-whonix untrusted vault whonix-gw whonix-ws work ERROR: Please shutdown all VMs before proceeding. On Thu, Feb 23, 2017 at 3:42 AM, Marek
Re: [qubes-users] Backup error - where is the log?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Feb 22, 2017 at 12:38:48PM -0500, Zbigniew Łukasiak wrote: > I am getting an error message when trying to restore a VM backup: > "unable to extract the qubes backup. Check the extracting process errors." > > Where should I look for the extracting process error log? > I don't see anything relevant in /var/log - but maybe I missed something. If you launched the backup from Qubes Manager, check ~/.xsession-errors. > More info: > > I made a bacup using the 'System' -> 'Bacup VMs' menu entry in the > Qubes VM Manager and then I tried to restore it with the 'System' -> > 'Restore VMs from backup' menu entry. I tried both just veryfying the > integrity and restoring it entirely - with the same result. > > My root filesystem if full - and I noticed that the backup > verification process tried to write to /var/tmp . This was failing - > so I tried symlinking that directory to another filesystem and > mounting another partition over it. This worked at the start and it > did create a 'restore_*' directory with some files in /var/tmp - > but then failed with the message I described above. I would like to > look into the error message - to understand what is failing. Out of disk space is most likely the reason. But if it isn't the case after symlinking /var/tmp, check messages in ~/.xsession-errors. If still nothing interesting, you can launch restoring (or verification) from command line (qvm-backup-restore), with --debug switch. - -- 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 iQEcBAEBCAAGBQJYrqCOAAoJENuP0xzK19csQXYH/2j89aAzUg1LAemETRfxOMcy T4oM+/ps2qlR1kgA1/LLKx6LdbW2cu5rMR9uAQhr5yHeLp15j5JXF4Ef/pFp1fXr TrvSMl4x9z+OAUKt+6uZncyl81J7UhMzJ0ixwE58B1vxUzP76aBXz7N8BwhdCLTw ydi0mg4Pd2iIMRV8wYCX4qxjT0M9OmYf4ClQpOcDUc8+68rEX2vwrD7vOuC0RIfu MUjutenc3jkLEnAEr0W9cXjwCR360R4ZU5r3SaOPXXo6P4JpBwHkdYdan1uv+cPT dGtKHMoQlgb6Gq3KPIobaMLhi+8WPv0RkThgjxodirUOHfiZ9GlVfpChtrd8Hjc= =pEg5 -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/20170223084254.GB13918%40mail-itl. For more options, visit https://groups.google.com/d/optout.