alexskysilk's latest activity
-
Aalexskysilk replied to the thread Storage setup? Separate OS and data drive? ZFS + Slog?.the slog will make absolutely no difference for this use case. it will, however, create a second spof point making your store more fragile.
-
Aalexskysilk replied to the thread [TUTORIAL] Why LVM-Thin Cannot Be Shared Storage in Proxmox.@bbgeek17 no disagreement. I was simply pointing out that the premise that a full node fence is required isnt necessarily true for the proposed solution to work. I'm not suggesting its easy, not fraught with gaping holes, probably too slow to be...
-
Aalexskysilk replied to the thread [TUTORIAL] Why LVM-Thin Cannot Be Shared Storage in Proxmox.I agree with this sentiment entirely- but it doesnt necessarily mean the conclusion. fencing in this context is just the vg activation on the "source", not full node fence. Any while I agree that this SHOULDNT be a function of the storage...
-
Aalexskysilk replied to the thread Dell PowerVault ME5024 iSCSI Performance: High Latency Spikes and Low Sequential Throughput on PVE 9.Fairly easy to test, since you have access to the storage both at the "linux" level on pve OR passed as an iscsi target directly to a vm instead of as a virtio device. sounds like you got most of those covered; however, its imperative that you...
-
Aalexskysilk replied to the thread Proxmox and Intel VROC.You may want to take a second and reconsider what that means. While using mirroring or parity/ec creates disk level fault tolerance in a storage solution, REDUNDANCY is a function of system level fault tolerance; if redundancy is a mission...
-
Aalexskysilk replied to the thread LVM Volume Recovery.testdisk doesnt make distinction between lvm or raw blocks. it looks for file system signatures, and assembled directories/files from available metadata. if that behavior is desirable, run testdisk on the vg/lv instead of the disk but its a very...
-
Aalexskysilk replied to the thread LVM Volume Recovery.If testdisk isnt recovering it, its gone. I suspect you already know this.
-
Aalexskysilk reacted to bbgeek17's post in the thread Proxmox in enterprice environments with shared fc storage with
Like.
Fair point. Reflink with sparse raw files gets you thin provisioning and snapshots without qcow2... so qcow2 metadata is out of the picture. What's left is the stuff underneath. o2cb has its own heartbeat and fencing that doesn't know corosync... -
Aalexskysilk replied to the thread Remote backup failing because of path.pay closer attention to what the error is telling you. Youre trying to create a virtual machine using /mnt/pve/iso as the DESTINATION STORAGE. there are two things you should do- first, go to datacenter-storage, select iso, and UNCHECK disk...
-
Aalexskysilk replied to the thread Can't update - No space left on device.that changes nothing. When you operate your own environment you weigh the tradeoffs and make decisions accordingly. there is nothing in a "home environment" that stops you from partitioning; if you cant be bothered thats your decision. best...
-
Aalexskysilk replied to the thread Remote backup failing because of path.you dont have write access to /mnt/pve/ISO. check owners/permissions on the remote filesystem and/or nfs export. I also dont think you meant to use that location as your vdisk destination.
-
Aalexskysilk replied to the thread Poor user experience with Windows Server 2025 on Proxmox.I feel that in my bones :lol: your config (and system) is as optimized as it could be. other than different storage choices there are not likely many knobs left to turn. Since the guest type and performance appear to be hard requirements, you...
-
Aalexskysilk replied to the thread Can't update - No space left on device.Scope is the relevent point. Best practices always stipulates that the OPERATING SYSTEM should have no other claimants on its space, since it serves as the underpinning of the rest of the system. In a general purpose Linux server, It has long...
-
Aalexskysilk replied to the thread Can't update - No space left on device.The fact that YOU do something doesnt make it a good idea or rationalize it as best practices. Its not a "better" point. its a different point. Yes, you should monitor your environment. A hypervisor's function should not have its operating...
-
Aalexskysilk replied to the thread Can't update - No space left on device.You're out of space. delete things. This is also a prime example why you dont comingle OS and data on the same partition. various services besides just not being able to update will not work now as they dont have room to operate.
-
Aalexskysilk replied to the thread Poor user experience with Windows Server 2025 on Proxmox.That is a useful and potentially important bit of information. These CPUs are actually cpu clusters and are internally individual NUMA nodes. With 8 cores this is probably fine with NUMA disabled, BUT the memory situation could be impacted as off...
-
Aalexskysilk replied to the thread [PROJECT] BASTRIX SharedLVM for Proxmox VE 9 — FC/iSCSI Storage with Thin Pools, Thick Generations and Multipath Safety.hmm. could this approach be used to facilitate other CoW filesystems (zfs/btrfs?) --edit on reflection, no. answered my own question ;) but it does seem to be a great option for nvof.
-
Aalexskysilk replied to the thread Cloned VMs from template receive the same DHCP IP address.Delete the mac address from the NIC before starting it. I believe choosing the unique checkbox when cloning does the same thing.
-
Aalexskysilk reacted to bbgeek17's post in the thread iSCSI on Proxmox itself for SQL Server Failover Cluster Instance (FCI) VMs with Like.
Manuel already noted this is outside what PVE supports. I'd go a step further: I can't recommend doing either of these in production. It's worth being clear about what WSFC actually needs from that disk. It isn't so much the block device as...
-
Aalexskysilk replied to the thread Poor user experience with Windows Server 2025 on Proxmox.there's your problem. Host exposes the full set of cpu flags to the guest, which means all mitigations applicable to your cpu will apply. in a virtualized environment, mitigations will destroy guest performance- Windows most of all...