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/...
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...
Hi,
On a machine with 6x4 TB hdd I installed PVE 6.4 (up to date) choosing RAIDZ2 (ashift left to default 12), and this should leave 4x4=16 TB or 14.1 TiB usable.
# zpool status
pool: rpool
state: ONLINE
scan: scrub repaired 0B in 1 days 00:35:33 with 0 errors on Mon Sep 13 00:59:36 2021...
Hi,
I'm about to dist-upgrade PVE and pve-qemu-kvm will go from 5.2.0-2 (with the qmp timeout / VM freeze issue starting to hit us) to 5.2.0-6 (current stable).
Once the dist-upgrade is done is there a way to "migrate" a running VM from the host it's running to the same host so that I runs...
Hi,
Today I had to migrate a physical machine running Fedora Core 32 with NVME root disk and UEFI boot to a virtual machine (OVMF) under PVE 6.3.
Unsurprisingly Fedora boot failed if I just copied (offline using an adapter) the whole /dev/nvme0n1 original block device to a ZFS volume and used...
While checking the logs of my PBS I noticed the longest PVE VM backup job was of a stopped VM (been in stopped state for a few weeks / daily PBS backups) which has a relatively large disk raw image (200G) on a relatively slow directory (NFS mounted by /etc/fstab not by PVE).
Is there a way to...
Note that I had relatively similar looking issue there with PVE running a PBS VM:
https://forum.proxmox.com/threads/proxmox-backup-client-gets-http-2-0-after-70mn-pbs-server-crashed.85312/#post-375257
It also has an old CPU Atom C2550 (like other posters here) and I had qmp failed messages too...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.