Recent content by alexskysilk

Good news here; while I dont know if there is official plugin available, quts is just linux, the storage fairly plain zfs, and the target is SCST target which the pve provided zfs-over-iscsi plugin supports.

ZFS offers the same disk aggregation functionality as a SAN; edit zfs is a disk aggregation mechanism. SAN is a multi initiator storage router. You will need exactly the same number of drives at the same replication or parity levels. In fact, there are SAN solutions that use ZFS for disk...

Rampocalypse is universal. You either accept the new cost of doing business or hold on to your old equipment for as long as you can. I'm doing the latter where I can ;) Ironically, for the most part, customers only really need to upgrade because the assets depreciated to zero, not because there...

In the enterprise, Uhh.... you might want to have a conversation with Blockbridge before you make that assumption. Pretty sure they dont give out their product for free. The other thing you might want to consider is that disks is just a portion of the cost- with ceph you will need a minimum of...

sure- the implication isnt that it doesnt work, its that its slow and painful.

hardware issue, yes- but not in the sense that anything is defective. searching the forum brings up https://forum.proxmox.com/threads/pbs-failure-with-kernel-7-0.183853/ Which doesnt have a known working solution. If you want to keep running pve on this system, just pin 6.17. it'll still work.

Ambitious. While I wont comment on the business case for this, point 5 is probably the most marketable. If you can already reconstruct a file from txg history without a snapshot marker and without needing to make a full static ddimage to mezzanine storage you have a customer right here.

I think you're going about this the wrong way. the payload of virtualization or standalong filesystem are not materially different. when I fire up testdisk on a block device, it doesnt care whether its a fileset of naked pictures or a root linux filesystem. If your intention is to built a zfs...

your root partition is on a disk that is experiencing problems- either hardware, cabling, or software. smartctl --test=long /dev/[path to your root device) dmesg | grep [your root device]

yeah I dont see anything in those links to suggest difficulty. and the only thing that changes for local vm migration is that the target will have to be on a clustered storage- which is still easiest handled via storage migration in cluster.

Yes, in the sense this is a feature that has a procedure to function in a linux system. If you specify By WHOM, you'd know who to ask specifically. If you mean per the Proxmox zfs on PVE pages, its "experimental" in the sense it is not within the PVE scope of support, at least in pve8. see...

This is the way. You can do this but it serves no real purpose; the storage is shared. Curious- what is the friction? adding and removing nodes is straight forward.

link_mode: active means all corosync traffic- checksums, encrypt, decrypt, etc- happens twice. It is not insignificant. You CAN utilize that to protect against the symptom you describe, but its a rather heavy solution for a transient problem that you are correcting. What might work well enough...

You are experiencing timeouts between your host(s) and your backup target. these issues stem from one or more of Source disk bandwidth network transport Destination disk bandwidth. for item 1- you mentioned your host storage is ceph. what is the OSD arrangement (drive type/count) and network...

Troubleshooting order: 1. Did you map your luns to your PVE HBA WWN? 2. does your HBA see the LUN during boot? 3. Whats the make and model of your HBA? are you using the default drivers that shipped with debian, or did you install a outside driver?