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

Disk full condition can wipe out a project file #2114

Open
BrentBaccala opened this issue Sep 23, 2022 · 1 comment
Open

Disk full condition can wipe out a project file #2114

BrentBaccala opened this issue Sep 23, 2022 · 1 comment
Labels
Milestone

Comments

@BrentBaccala
Copy link
Contributor

This is GNS3 2.2.34 (from the GNS3 PPA) on Ubuntu 18.04.6 LTS.

I ran out of disk space on the gns3 partition while I had one project open in the GUI. I switched to another project (hoping to delete one of the nodes there), but couldn't open the project because of the disk full condition. So I switched the GUI back to the first project.

The .gns3, .gns3.backup, and .gns3.tmp files for the second project (that I tried to open and failed), are now all zero-length files.

@BrentBaccala
Copy link
Contributor Author

I was able to recover the data on the project's Ubuntu nodes using the following procedure:

  1. Fix the disk full condition
  2. grep in the qemu.log files in the project's qemu directories to find the command lines that were used to start each node, and from this figure out which hda_disk.qcow2 file corresponded to each node
  3. Use the GNS3/upload-image.py script in https://github.com/BrentBaccala/NPDC to upload the qcow2 file to the GNS3 server as an image
  4. Use the GNS3/add-appliance.py script (same repository) to create an appliance file using the uploaded image as its disk template
  5. Import the appliance into the GNS3 GUI
  6. Clone the appliance as a node and boot it

The resulting nodes have a disk backed by the recovered disk image, which is itself backed by the original node's backing file, so make sure not to delete the original node's backing file.

@grossmj grossmj added this to the 2.2.35 milestone Sep 28, 2022
@grossmj grossmj modified the milestones: 2.2.35, 2.2.36 Oct 18, 2022
@grossmj grossmj modified the milestones: 2.2.36, TBD Dec 28, 2022
@grossmj grossmj modified the milestones: TBD, 3.1 Jan 30, 2023
@grossmj grossmj added the Bug label Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants