Recent content by alexskysilk

I think we may be experiencing some semantical difference. "SAN" or Storage Area Networks typically mean shared block storage- eg iSCSI, FC, NVOF or even SAS/SCSI. "Directory Storage" means (to me) locally mounted filesystem, either on exclusive (local) disk or network storage device...

Lets begin with the obvious. what are you using now? I presume it some sort of NAS since you're using "directory-based storage." Is this besides the above? in addition to? Either a NAS or a SAN can handle this, so it looks like you already have it covered. What pain points are you...

nfs is just the transport. no special magic occurs because thats what you are using for connectivity.

I think you might want to re-evaluate the basis of troubleshooting from belief to, ahem, troubleshooting. Well that is the problem isnt it; maybe post those too?

neat idea, but I think you may want to pick EITHER homelab/smb use vs actual enterprise use, as their usecase will dictate widely different requirements. IF you want to target home/SMB use, you need a gui for user and ACL management; maybe integrate openldap/freeipa. without this it will still...

check logs on your smb serving device (unraid) around the time you get disconnected. most likely network issues.

tldr- its working as intended, and that "unknown" is cosmetic only. ignore it.

"Best Practices" in this context are largely dependent on your use case.. While performance is an important part of your strategy, its not the sole objective. As you should be aware, LVM on shared storage is supported on lvm thick only. Snapshot facility is possible at the QEMU level but it...

That probably depends on your customers more than it does you. Having some exposure to the industry, I can tell you most studios will effectively give you their policies when you'll submit a vendor security questionnaire. "Proxmox" isnt really relevent in this conversation. Lynis produces a...

payload on the host. you can share directories to your containers as mountpoints. Instead of your data living INSIDE a VM logical volume, it can live on your normal filesystem (eg, /srv/my_important_data) that makes things easier and safer, but the approach remains the same. In general you...

ok, but what happens when you run the workload on host B for a while? do you have any form of check to make sure you're synchronizing the right source to the right destination? The above procedure is fairly simple to set up with two PVE hosts that have ZFS as their payload backend. see...

you created a circular dependency. your host is dependent on a datastore served by a guest, but the guest needs the host to run. I would begin by disabling the SMB_NODE_200 datastore. Next, make sure the container is running, the storage is available, and the nfs service is running. Then...

Cavium Nitrox is a line of security coprocessors. The only useful function their linux drivers expose is cryptographic acceleration, so if you're building a "high performance" vpn appliance it COULD be useful (I put high performance in quotes because a modern server cpu can cope with the same...

Not just terrible. likely defective. did you run a smart long test?

I've used those before. What I recommend to make your life easier is to create a separate vlan per interface, and match them on the initiators. I'd leave the vlans on separate class C's so you dont inadvertently create conflicting routes. I imagine you have 2 ports connected per controller-...