Proxmox - use storj as storage for lxc or iso's

Im not to familliar with S3, im not sure if this is a stupid idea, but im trying to get storj running as storage for lxc or vms

as you can see it’s possible to mount storj using s3fs, however trying to use it creates a lot of problems currently.


LXC
ormatting ‘/var/lib/vz/images/108/vm-108-disk-0.raw’, fmt=raw size=8589934592 preallocation=off
Creating filesystem with 2097152 4k blocks and 524288 inodes
Filesystem UUID: 76abbfe1-c2c0-45f4-9643-1a2ae825c64d
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
extracting archive ‘/mnt/storj/prox/template/cache/debian-10-standard_10.7-1_amd64.tar.gz’
tar (grandchild): Cannot close: Operation not permitted
tar (grandchild): Error is not recoverable: exiting now
tar: Child died with signal 13
tar: Error is not recoverable: exiting now
TASK ERROR: unable to create CT 108 - command ‘lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 – tar xpf - -z --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs ‘–xattrs-include=user.’ ‘–xattrs-include=security.capability’ ‘–warning=no-file-ignored’ ‘–warning=no-xattr-write’ -C /var/lib/lxc/108/rootfs --skip-old-files --anchored --exclude './dev/’’ failed: exit code 2

BACKUP
recovering backed-up configuration from ‘storj:backup/vzdump-lxc-102-2024_05_26-22_19_41.tar.zst’
Formatting ‘/var/lib/vz/images/108/vm-108-disk-1.raw’, fmt=raw size=8589934592 preallocation=off
Creating filesystem with 2097152 4k blocks and 524288 inodes
Filesystem UUID: b12fee26-f74c-467b-a811-0320e999d84f
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
restoring ‘storj:backup/vzdump-lxc-102-2024_05_26-22_19_41.tar.zst’ now…
extracting archive ‘/mnt/storj/prox/dump/vzdump-lxc-102-2024_05_26-22_19_41.tar.zst’
tar (grandchild): Cannot close: Operation not permitted
tar (grandchild): Error is not recoverable: exiting now
tar: Child died with signal 13
tar: Error is not recoverable: exiting now
TASK ERROR: unable to restore CT 108 - command ‘lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 – tar xpf - --zstd --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs ‘–xattrs-include=user.’ ‘–xattrs-include=security.capability’ ‘–warning=no-file-ignored’ ‘–warning=no-xattr-write’ -C /var/lib/lxc/108/rootfs --skip-old-files --anchored --exclude './dev/’’ failed: exit code 2

VM
Formatting ‘/mnt/pve/truenas/images/108/vm-108-disk-0.qcow2’, fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=metadata compression_type=zlib size=540672 lazy_refcounts=off refcount_bits=16
transferred 0.0 B of 528.0 KiB (0.00%)
transferred 528.0 KiB of 528.0 KiB (100.00%)
transferred 528.0 KiB of 528.0 KiB (100.00%)
efidisk0: successfully created disk ‘truenas:108/vm-108-disk-0.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K’
Formatting ‘/mnt/storj/prox/images/108/vm-108-disk-0.qcow2’, fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=metadata compression_type=zlib size=19327352832 lazy_refcounts=off refcount_bits=16
TASK ERROR: unable to create VM 108 - unable to create image: qemu-img: /mnt/storj/prox/images/108/vm-108-disk-0.qcow2: Could not resize file: Input/output error

And constantly getting Input/output error

If anyone has suggestions on how this could be achievable i would greatly appreciate any insight

It will be an uphill battle. You may want to enable caching, or try rclone with VFS cache in full mode. But even then, not all filesystem features will be supported.

You may have better luck mounting the sparse disk image with rclone, and storing data in that disk image. Not sure if that is the option on the os your are using.

1 Like

Yes, rclone mount --vfs-cache-mode full could be a solution, but perhaps you could have some issues anyway.
You may also take a look on Veeam, they recently added support of Proxmox for VM backups: Veeam Backup for Proxmox.

See Guide to Veeam and Storj Integration - Storj Docs.

By the way, you may also take a look on cunoFS: cunoFS: Unleashing Object Storage — cunoFS Documentation, just need to configure it for S3-compatible objects storage, not Amazon’s one.