Search results

No, I don't have an offsite backup. I'm trying to do an "undelete" of the entire directory of the index files

Hello, is there a way to "undo" a prune I run for error? of course I don't have run garbage collector yet

No one has the same problem? If I delete all the backups from the PBS server the first backup works like a charm, the second one break with the same error. Client proxmox-ve: 6.3-1 (running kernel: 5.4.73-1-pve) pve-manager: 6.3-6 (running version: 6.3-6/2184247e) pve-kernel-5.4: 6.3-8...

Too late :eek: I just reconfigure all of my windows server... hope it doesn't happen again after the next update!

I didn't find much on the net, I have to use just my head ;) Source modules do the tricks. I think that the source used in kernel newer then 5.3.10 is different from the previous. Can't say if true, but with the compiled ones (downloaded from Cavium) my controller start works again. With the...

Resolved by myself. I download http://filedownloads.cavium.com/Files/TempDownlods/98262/qla2xxx-src-v10.02.04.00-k.tar.gz installed kernel headers e build essential I build and install modules then I removed multipath apt purge multipath-tools rm -fr /etc/multipath* apt purge...

Thank you for your response. As you think it's a Lenovo card connected to a Lenovo DS storage. I think that I can't have support from the vendor cause Debian/Proxmox it's not a certified OS for this kind of hardware. Anyway I will try to open a ticket. I will look at your links in the meanwhile...

Still same errore on the last version (5.4.78-2-pve). Any news for my FC controller?

I still have the original backup file, I hope to find some times to makes a new restore and check again the used space after the restore

The real difference was small, about 3GB. My fault was that I paste you the result after 24h of production

The original container has: /dev/loop11 276G 241G 24G 92% / The restored container is almost the same (some data were added today): datastore/subvol-114-disk-0 350G 277G 74G 79% / P.S. I use 350 instead of 500 (like in your example)

It works! No error from command line.

Backups are on a PBS separate server, not a local storage. root@xxxxx-xx ~ # pct restore 114 pbs-c03:ct/114/2020-12-21T04:53:42Z --rootfs vms:500 unable to parse PBS volume name 'ct/114/2020-12-21T04:53:42Z' root@xxxxx-xx ~ #

What is the correct syntax for BACKUPSTORAGE?

I will give you some more information, hope it help: Original server: server1 PBS Server: backup1 Destination for restore: server2 Server 1 backup on backup1 without any error. Server 2 is a new server with a new and clear ZFS storage with 3.4T free. Operating system is installed on a...

Hello I restore from the GUI. This is the lxc conf from the original server: arch: amd64 cores: 4 hostname: xxxxxx-xx memory: 10240 net0: name=eth0,bridge=vmbr1,firewall=1,hwaddr=36:3B:FA:93:78:DA,ip=dhcp,ip6=auto,type=veth onboot: 1 ostype: ubuntu rootfs: vms:114/vm-114-disk-0.raw,size=280G...

Hello LachCraft, thank you for your time, but I think that my copy/paste alignment give you a wrong idea of what I have... This is the correct view: Inodes: 7218232103 IUsed: 6 IFree: 7218232097 IUse%: 1% Anyway, it's a new server. Datastore was never used before, and disks are new. So no...

It's not full, it's just 1% used: Filesystem Inodes IUsed IFree IUse% Mounted on [...] datastore/temp 7218232103 6 7218232097 1% /datastore/temp

datastore/temp 7218232103 6 7218232097 1% /datastore/temp