Search results for query: ZFS

...Linux 6.8.12-18-pve System: Lenovo M710 SFF intel core i5-7400 3.0 ghz DDR4 memory 8 gb OS drive - M.2 drive, 1 TB, teamgroup Storage pool is in ZFS, including 3 SSDs, samsung 2 TB each Currently running monitor via one of the displayport outputs Troubleshooting steps taken 1. Prolonged...

...horse. My recommendation is just to consider all possibilities and have all information available before being blindsided later down the road. ZFS replication is the easiest, most set and forget configuration for a 2 node cluster. It definitely becomes wasteful and less attractive for a 3...

...[445562.837128] Call Trace: [445562.837131] <TASK> [445562.837137] __schedule+0x468/0x1310 [445562.837150] ? dbuf_find+0x254/0x260 [zfs] [445562.837591] schedule+0x27/0xf0 [445562.837598] schedule_preempt_disabled+0x15/0x30 [445562.837603] __mutex_lock.constprop.0+0x508/0xa20...

...so far! (Uptime is less than 15 minutes so... will report back later...) System details: System: Dell PowerEdge R740XD CPU: Intel Xeon Gold 6154 ZFS as root-filesystem on SATA PM883's ZFS as VM-storage filesystem running NVMe Kioxia CD8-R's. The server does seem to be running a little bit...

Sorry for my late response, thank you for your feedback! As you mentioned it is only logged once, difficulty is that those messages are reported at the end in the logs, so it is a timing issue. For now I leave it, as it is not a recurring error, only one per zfs pool after boot. Have a great day.

...Feedback about how the new kernel performs in any of your setups is welcome! Please provide basic details like CPU model, storage types used, ZFS as root file system, and the like, for both positive feedback or if you ran into issues where using the opt-in 7.0 kernel seems to be the likely...

Hello, Is it possible to migrate VM from a node to another node (same cluster or not) using Datacenter Manager by selecting a different storage (ex: source : local-zfs -> destination : local-zfs2) ?

...and yet much more stable than any other solution without proper built-in HA like ZFS replication or even NFS or any other SPOF-based setup like OP's. Sure, 5 node cluster is better than 3, but if you're coming from a two node cluster VMware, you're not going to have a 5 node ceph cluster...

...if you are not adequately prepared. To play devil’s advocate, do you truly need the 3 node environment? Could you not get by with a traditional ZFS replication setup (like you are used to) between two of the servers? The third server could then be a qdevice or a glorified quorum voting PVE...

...going to start off with an apology of my own ;) Sorry, but let’s dumb this down for my own sake. Essentially you have a high end mini PC with a ZFS mirror for the OS, and a few DAS devices connected over high speed USB. As far as I understand, you basically have a bunch of media and IoT...

...Turnkey FS was a disaster that I suspect is obsolete anyway. Here's the Proxmox host (on a higher end miniPC) configuration: 1. 1TB ZFS on 1TB NVME SSD x 2TB NVME SSD paired - Proxmox can have all 1TB for Proxmox overhead and magic 2. 1TB XFS on second partition of the 2TB NVME SSD...

Thank you for the clarification MnxBil, I wrongly thought that because the underlying file system of my nfs shares was ZFS, it might have been possible. I now understand that I have nothing to replicate to pve3. I do come from the road you described : ZFS replication inside the cluster with...

replicated to what? You need a ZFS source and destination pool. Your NFS cannot be it, so you have only one pool on pve3. I don't see a way with the hardware you have described. I would use a proper HA NFS solution or a SAN (dedicated as in a box with two controllers or distributed like ceph...

VMs auf HDDs betreiben ist generell nicht best practice ;) Aber als Datengrab schon vertretbar und genau für den Usecase wurde ZFS ja ursprünglich auch entwickelt, das kam als erstes in von Sun vertickten Solaris-Dateiservern zum Einsatz. So wie ich das verstehe will der OP die HDDs ja nicht...

...on my third node : pve1 and pve2 have access to the nfs shares named SAS & SATA. pve3 does not use the nfs shares, it has local disks and two ZFS pools named SAS & SATA (both created before joining the cluster), that will be used as a zfs replication target. The gui (datacenter => storage =>...

...kernels and updates GRUB to point to them correctly. This solves the hang-at-boot issue in the majority of post-upgrade cases. If you are using ZFS as the root filesystem, the process is slightly different. PVE 9 updated the ZFS ABI and if the pool was not imported cleanly, boot will stall...

Sers Johannes, das ist mir schon klar. Aber soweit ist der TE noch nicht. Ich sehe ihn mehr in der "Fehler-Ausbügel-Phase". Und ein ZFS nur auf HDDs ist ja auch nicht wirlich best practice.

Nicht im Ernst, oder? Die ganze Kiste funktioniert ja sowieso noch nicht, also lösche bitte mal im Proxmox die beiden Festplatten. Node/Disk/WipeDisk Dann reichst du die beiden Platten einzeln an OMV durch und erst da tust du das erste Dateisystem drauf. Aber erst, wenn das mit der kleinen...

Naja, ein ZFS mirror hat eine schnellere Lesegewschwindigkeit als ein einzelnes ZFS device. Und hat dazu die ganzen Features, die ext4 nicht hat: https://forum.proxmox.com/threads/fabu-this-is-just-a-small-setup-with-limited-resources-and-only-a-few-disks-should-i-use-zfs-at-all.160037/ Also...

Hi, I have a cluster of 4 nodes which is all up-to-date (9.1.6), but I still see zfsutils-linux as upgradable but not upgraded (even is nothing is on hold, from APT's perspective). # apt list --upgradable zfsutils-linux/stable 2.4.0-pve1 amd64 [upgradable from: 2.3.4-pve1] Notice: There are 3...