Search results for query: ZFS

...genauer an: fdisk -l /dev/sdb fdisk -l /dev/sdc Siehst du noch Partitionen, oder sind die Platten "raw"? zdb -l /dev/sdb zdb -l /dev/sdc Wenn ZFS-Metadaten noch vorhanden sind, siehst du hier den Pool-Namen und die GUID. ZFS schreibt seine Labels an den Anfang und ans Ende jeder Disk...

...Einstellungen. Da der HBA Modus war nicht eingeschaltet und wurde von mir aktiviert. Blauäugig wie ich bin, ist auch meiner erster Kontakt mit ZFS, habe ich natürlich keine Maßnahmen ergriffen, wie ein Pool export oder gar Backup. Nach dem Boot mit dem getauschten Controller meckerte Proxmox...

...the same for 512 and 4kn throughout multiple runs with difference about 1% - which might be statistical error. Other tests - random read, sequential read/write, fsync showed even smaller differences. I might test that on different PVE cluster using ZFS next time. Thanks everybody for your...

@Stoiko Ivanov please disregard. Moved to: https://github.com/openzfs/zfs/pull/18408

Running PVE on hosts with 512/512 disks, storage is ZFS (ashift=12) and Ceph. Guests use virtio-scsi-single, mostly Linux, some Windows. I wonder if it's worth adding (or similiar): args: -global scsi-hd.physical_block_size=4096 -global scsi-hd.logical_block_size=4096 For Linux it feels...

Thanks for looking through openzfs issues - seems like this could indeed be a fix - I'll try to reproduce the issue here. * Does your System have `/` on ZFS? * how does the container config look like? (`pct config <vmid>`)? * how does the zpool look (`zpool status`) * could you share the...

see - https://forum.proxmox.com/threads/proxmox-zfs-lxc-docker-container-oom-results-in-kernel-bug-at-mm-usercopy-c-102.182232/ - seems potentially similar what kind of workload is running on the machine - lxc-containers? - do you see any other issues in the journal before this occurs/could...

Having looked at your code a bit I think your plugin manages iSCSI at a lower level than the native ZFS over iSCSI implementation. Proxmox relies on iscsidirect to make the connections.

...here today and realized I never replied! I ended up building my NAS and pretty much took most of the advice you wrote above. I installed Proxmox on two 1TB M.2. running in a ZFS mirror. I then passed through an HBA card to TrueNAS and running three 3.5" drives in RAIDZ1. Thank you for your...

...o detiene el bucle de sincronización. limit= : límite de ancho de banda en KB/s (ej. 62500 ≈ 50% de una red 1 Gbps). zpoolname= : nombre del pool ZFS (debe ser el mismo en ambos lados). debug=1|0 : activa logs detallados. Ejecuta pve-zsync sync para cada VM, respetando el sentido indicado...

Did you test that? I know that you know that pve is a fuse-mounted database; a snapshot of the "/"-filesystem is... empty: ~# ls -Al /.zfs/snapshot/manual/etc/ | grep pve; echo "inside pve:"; ls -Al /.zfs/snapshot/manual/etc/pve/ drwxr-xr-x 2 root root 2 Aug 26 2023 pve inside pve...

Another option would be to copy /etc/pve from a zfs or lvm snapshot.

That’s why a little bit of context helps a lot because seeing that error I focused on the zfs itself :-)

Try booting the virtual with a different options or kind of livecd to try the zpool import -f rpool This will show you the reason why it didn't import automatically. It could be because the drive is inaccessible or zfs pool is in some unexpected state.

Hi, It looks like ZFS pool didn't import properly after the upgrade. It's not pbs/proxmox specific - Linux usually doesn't like bios->uefi upgrades. Can you boot the vm into shell and try importing the zfs pool manually ? zpool import -f rpool

Try to set Display to none. Maybe configure a serial terminal first. Unrelated but you should enable discard for disks on a thin provisioned storage such as local-zfs.

See: https://bugzilla.proxmox.com/show_bug.cgi?id=3662 Discussion here: https://forum.proxmox.com/threads/cant-boot-vm-after-put-tpm-state-on-zfs-over-iscsi.103099/ TPM does not work over PVE's native ZFS over iSCSI implementation.

...filter = [ "a|/dev/mapper/.*|", "r|/dev/sd.*|" ] } This is what it needs to look like: devices { # added by pve-manager to avoid scanning ZFS zvols and Ceph rbds global_filter = [ "r|/dev/zd.*|", "r|/dev/rbd.*|" ] preferred_names = [ "^/dev/mapper/", "^/dev/sd" ] filter =...

Also just realized, I believe the original disk was in a zfs by itself. The caching was then pointed at the zfs pool I believe.

I have a PVE 8.x cluster using TheGrandZazoo's freenas‑proxmox plugin to work with data served from TrueNAS Scale 23.10.2. I'd like to get PVE and TrueNAS upgraded to the latest versions, and start using the new truenas-proxmox plugin. I've not had any luck finding a guide for migrating from the...