you're right that pbs does does not store multiple media sets on a single tape and every backup made with it is fully deduplicated (within one media set)
The idea here is that a media-set is the smallest consistent unit, so we'd recommend having...
no, not yet. but feel free to open an enhancement request here: https://bugzilla.proxmox.com
i think it makes sense to have maybe a 'table-like' resource view, similar to what the tree view widget + usage graphs could be
hi,
yeah this was probably just copied over from pve/pbs. There are currently no groups in PDM because nobody implemented it yet, and it seems there was not much demand for it yet.
you're right, the docs could be much better here. would you mind...
for that i sent a patch [0] to improve the error message in that case:
what should also have worked besides clearing out the tape manually would have been:
proxmox-tape format --drive <driveid>
(or clicking format in the webui)
this erases...
hi,
could you try to create a new user from the cli (pveum) with a very simple password and try that?
also a section from the journal during login would maybe help.
(it seems there are a few things not right on the system, the zpool, the rrd...
i couldn't reproduce it here yet, but the browser crashing doesn't sound like it's a fault on our side.
can you open firefox from the commandline and e.g. enable some debug logging to see if there is any hint where this might come from? anything...
does it also crash with a current version? e.g. currently there should be 156 in the arch repos: https://archlinux.org/packages/extra/x86_64/firefox/ ?
do you have any extensions etc installed? if yes, could you try in private mode?
looks weird, we request 262144 byte but only get 10240 back...
is there some transfer size limit on the lio side maybe?
EDIT: did you format the tape beforehand? (this is necessary for labeling)
yep seems like it:
says : 'ExpXferLen: 16' so 'expected transfer len 16' which would match our code before the patch
and then
which is exactly that ITT
in the meantime the package was bumped (should be included in proxmox-backup-server...
IMO the ui looks nice and i get why this is a feature that some want. but there is currently a big caveat: for each pbs snapshot that is mounted there will be an extra helper vm that consumes memory and cpu resources. these will be auto cleanup...
ok reading the errors from the target side, it seems this is an issue in our code that was recentyl fixed:
https://lore.proxmox.com/pbs-devel/20260817123128.2813924-1-d.csapak@proxmox.com/T/#t
the patch is applied, but not yet in a bumped...
aside from using the tape drive/changers via iscsi there is no other possibility at the moment. we only do datastore-> tape backup, not direct to tape, nor can we 'mount' a foreign pbs datatstore (e.g. for locking reasons)
using it via iscsi...
Hi,
not sure what is happening, but we'll hopefully find out :)
no manually adding will not help since the labeling also includes writing the first block to the tape (our 'media' header)
can you post the output of dmesg after a failed (manual)...
mhmm can you try to open a `journalctl -f` or `dmesg -w` on the host while trying to boot the vm so you can see the messages live when it starts to hang (could also work over ssh, but directly on the machine would be best) maybe there can be seen...
usb hotplug is implemented since quite a while..
if it does not work for you, can you post your vm config (qm config ID) and versions (pveversion -v) ?
Hi Everyone,
Every few months someone asks some version of "why can't I use LVM-thin on my shared SAN LUN?" Thick LVM works fine as shared storage, but has no native snapshots. LVM-thin has snapshots but is local-only... it's natural to wonder...
it's a bit of a narrow use case IMO, but at least worth discussing. would you mind opening a feature request on our bugtracker (https://bugzilla.proxmox.com) ? there we can track it better and other devs can also chime in
do you have a working ipv6 connection? it seems apt resolves the ip to ipv6 and tries with that, but it says that this is unreachable.
maybe because your client does not try to use ipv6?
does 'lspci -nnk' after a reboot show 'vfio-pci' as a driver? if not you might need to order vfio-pci before ahci fot it to work
excerpt from our docs:
https://pve.proxmox.com/wiki/PCI(e)_Passthrough
so in your case there should be a file...