Search results

Testing 5.4.157-1-pve, after 24 hours no issue so far.

We already have a new VM with the newer software and operating system installed and validated by our user test team. The new VM just lacks the real data which is on the current (old) VM in production and quite large in size relative to our infrastructure (otherwise we would just have copied the...

Hi, To help upgrade a VM with a large disk (on ceph/rbd storage) we'd like to copy the VM disk and mount the copy on a new VM. I didn't see an obvious way to do it in the proxmox VE UI, did I miss something? I'm thinking of doing like described here...

There is only the root@pam user on our PBS server, our PVE cluster has access to it via PVE root@pam datacenter / storage / add PBS where we provided once the root@pam credentials of our PBS server. The nightly backups are scheduled by PVE root@pam user via datacenter / backup / add job. If...

Hmm may be this is due to PVE/PBS versions: On PVE 6.4-9 I have /etc/pve/user.cfg with: user:mytestuser1@pve:1:0:::::: role:PVEDatastoreAuditor:Datastore.Audit: acl:1:/storage/backup1:mytestuser1@pve:PVEDatastoreAuditor,PVEVMUser: acl:1:/vms/195:mytestuser1@pve:PVEVMUser: And in...

Hi, I want to give read only access to backups (mainly for "file restore") to one of our users so I added Datastore.Audit on the PBS storage for this user but it was not enough: empty backup list for the user. I had to add Datastore.AllocateSpace which is a write permission (allows the user to...

Done (we have "BASIC" level support on PBS but I didn't look how to link account to that yet :) https://bugzilla.proxmox.com/show_bug.cgi?id=3727 For proxmox-backup-debug it looks like it's not there in 1.x, will test a 2.x ASAP, thanks for the hint!

We had various crash with older PBS version and the PBS was undersized (CPU, RAM), we also had some reboot issues. So far my manual checks show all zero sized chunks on "backup2" are dated Jun 18 on "backup1". So probably not a direct PBS bug. Found another "blob too small" in the forum...

Hi, During our weekly verify one week ago on a PBS datastore "datastore2" on PBS 1.1.13-2 machine "backup2" we got 351 errors "blob too small (0 bytes)". The verify job renamed the zero sized blob to ".0.bad": # extract from LOGFILE=/var/log/proxmox-backup/tasks/...

pve-no-subscription just moved from 5.4.140 to pve-kernel-5.4.143-1-pve is there by any chance the 5.4.148 asmedia fix backported?

In my case I unchecked "Add as datastore" when creating the directory so there was no datastore in the UI.

Hi, On a test PBS 2.0.4 server on a dedicated disk (sdb, unused otherwise) I first created a directory "datastorage1" on sdb via administration/storage/directory/create directory, unchecking "Add as datastore" (since I did not want to create one immediately). Then I changed my mind and wanted...

More info from kernel developpers (about which version has the fix on each branch): https://bugzilla.kernel.org/show_bug.cgi?id=212695#c4 Pali Rohár : This issue was fixed/workarounded in following commit (in 5.15) which forces MPS to 256 bytes...

Thanks! Looks like someone had the issue before: https://forum.proxmox.com/threads/prevent-zpools-from-auto-importing.30551/ And there's now a "disable" which I assume should prevent autoimport on the specified pool.

I powered off only the external USB dock, then redid export then power on, then import and now the 2 USB disks are online with the others! # zpool history ... History for 'ssdbck1': ... 2021-10-12.16:19:16 zpool export ssdbck1 2021-10-12.16:19:37 zpool import -d /dev/disk/by-id/ -o...

@Dunuin zpool export ssdbck1 commands succeed (no output, exit code zero) but the pool is still there after the command. zpool import says "no pools available to import". zpool import ssdbck1 says # zpool import ssdbck1 cannot import 'ssdbck1': a pool with that name already exists use the...

Hi, I have a 6 disks RAIDZ2 pool, all 6 disks are currently on internal SATA. To workaround an issue on two of the SATA ports (1) I'd like to move (until a receive a new SATA PCIe controler card) two disks to an external USB3 enclosure. ZFS when on SATA has "ata-xxx-serialnumber" in front on...

To migrate the zvol to an appropriately configured ZFS I was not able to use zfs send/receive because it does not support setting volblocksize: zfs receive -o volblocksize=16k "cannot receive: invalid property 'volblocksize'" Feature request here: https://github.com/openzfs/zfs/issues/8704...

Hi, While running PVE 6.4 (kernel 5.4.140-1-pve) on a threadripper system based on AsrockRack TRX40D8-2N2T motherboard we recently lost two SATA SSD drives on kernel write errors, after testing various things (swapping SSD, cables) we found out the issue happens (after a while) only on the two...

Yes this is where I read about volblocksize. However it's not clear what value is optimal in my case, 128k ? 1MB ? 4MB (like ceph does I think) ? Also on the following advice: "When doing this, the guest needs to be tuned accordingly and depending on the use case, the problem of write...