Posts by space_ranger

Quote

I'm not sure how it could be useful. Are you referring to some kind of notice? I don't think I follow you now...

When the GUI is used to edit an existing folder and change the drive it is assigned to. A new empty folder is made on the new drive.

The folder that was previously linked to that entry in the gui remains where it was along with anything that was in the folder. However the old folder is no longer represented in the GUI.

So if it were full of lots of data you could end up with a folder full of files sitting on the drive without a visible GUI entry to represent it.

Quote

What if that folder weighs 5TB? You would end up with 10TB of data.

Yeah true but since your moving between two drives at some point that has to be the case. I was thinking that intentionally separating the delete option might make it safer. Didn't know the delete option existed and was removed.

The process I was thinking was this

1. Select a shared folder edit it and change the storage - with the Option set to move files
2. New folder is creasted on the new drive
3. A new GUI entry is made called [Foldername]_Old which points to the previous folder location
4. A rsync command is run in the background to sync the previous folder with the new one

I'm not sure we're on the same page. My suggestion is to have an option to move the files. You could still choose not to which would result in the current behaviour.

Even without any file moving if the GUI respected the orphaned folder and added an entry to the gui to show it still exists that would be useful.

No files would be lost with my full suggestion. It would simply run the rsync for you. You would have two copys of all your files.

I appreciate it's probably something that is not done regularly by people. Maybe not worth the effort of implementing.

Using rsync from the GUI for one off jobs is a bit awkward, I used SSH as it was easier.

Context:

Selecting a folder in the GUI and changing the drive creates a new empty folder on that disk and leaves the old folder in place but does not move files.

Issue:

The expected behaviour would be to move the files from the old folder to the new one. Particularly as the old folder is no longer represented in the GUI after the operation.

Suggestion:

Add a feature, prompt or tick box that does the mv or rsync command to move the folders contents after making the new folder on the other drive. Optionally the old copy could be deleted or a new folder entry made in the shares list called MovedFolder_[insert folder name]

Just an update with a solution I found for anyone suffering with this problem. You can add a delay to the startup by creating a systemd override.

sudo systemctl edit libvirtd

Then add the following lines to delay for 30 seconds. That works for my setup but the time can be altered to whatever works for the sytem.

[Service]
ExecStartPre=/bin/sleep 30

The autostart function is now working fine for me.

I'm not sure if this is an issue with multiple causes but I have located why my VM seems to fail to start which may be related to the issues others have had.

Spice fails to start and then the VM exits. When i start the VM manually it runs fine but requires me to manually start spice if i want to get to the console which does work.

I think the issue is this one https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1492621

This it the forum post i found about it https://forums.debian.net/viewtopic.php?t=155857

I tried the workaround but it does not work for me. It would be nice to have some way to delay startup until the adapter is up. I have yet to figure out a reliable way to do that, open to suggestions?

That may be why the disabling ipv6 works for some if its making the ip4 come up faster?