Search results

Those are SMR HDDs. Don't use SMR HDDs for anything if possible, especially not for server workloads or ZFS. CMR HDDs only exists up to 2.4TB in 2.5" form factor. Once the CMR-cache is full those SMR HDDs will totally suck and can't keep up writing.

Don't install it on pen drives, SD cards and similar. PVE writes a lot and will kill those quickly. With ZFS for raid1 it it might even kill small/cheap consumer SSDs pretty fast. Get proper HDDs or SSDs. I usually recommend to use 32GB for the root fileystem. If you want to upload big ISOs or...

Then its a single disk vdev and not a raidz (which would be the equivalent of a raid5). You can't. Backup everything, destroy that pool, recreate it as a 3-disk raidz and do a restore. But be aware that you won't be able to add a 4th/5th disk later (yet).

Yes. Or "pvesm set <YourStorageID> --is_mountpoint <AbsolutePathToMountpoint>" in case the folder your are using as a directory storage isn't the mountpoint itself but a folder below it.

No, read the link. Its a database and it contents are presented via fuse as files. Without the PVE service running (and it won't when booting something else than PVE) there won't be any files. Find out what's consuming the space, delete that stuff, reboot and see if it is working again. And if...

That's not unusual as that's not a normal folder and the pve-cluster.service needs to be running for it to be mounted and this often isn't the case with a full root flesystem. See: https://pve.proxmox.com/wiki/Proxmox_Cluster_File_System_(pmxcfs)

Dann bist du aber auch schon wieder an einem Punkt wo du fast kein Live Patching mehr brauchst. Dann könntest du noch für 10+€ einen SBC/Thin-Client als QDevice dazupacken und hättest ein Cluster, damit du mit Live Migration einen Node für einen Reboot freiräumen könntest. ;)

Das Zitat sagt doch genau das. Du musst die VM migrieren oder neustarten (und das über PVE was dann ein Shutdown + Start macht damit die VM einmal wirklich stoppt...Reboot innerhalb der VM reicht nicht). Sonst läuft die VM mit der veralteten QEMU Version weiter selbst wenn auf dem Host bereit...

Stand-alone PVE node or cluster? Usually it is full root filesystem, storage problems or quorum lost.

USB passthrough isn't great for devices that need low latency or high bandwidth like an USB disk. So for an USB disk I would recommend using disk passthrough via virtio SCSI: https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)

Aber natürlich auch nur, wenn PBS nicht ständig darauf zugreift. Bei einer 14TB HDD wird die aber sehr viel zu tun haben. Nicht vergessen: PBS braucht IOPS-Performance und daher am besten SSDs für die Backups. HDDs kann man nutzen, dann muss man sich aber nicht wundern, wenn so ein Maintainance...

Denke die meisten umgehen das einfach über einen Cluster und Live Migration. Da flog sogar ein Script (glaube von Tuxis?) rum was dir automatisch einen Node von Gästen freiräumt, dann kannst du den Node neustarten, ohne das irgendein Gast Downtime hätte und dann werden die Gäste wieder...

Wenn du oft auf deine Downloads von Windows zugreifen willst, dann würde ich lieber eine NAS VM/LXC laufen lassen die einen SMB-Share bereit stellt. Wenn dein Metube in einem privilegierten LXC oder in einer VM laufen würde, dann könnte man diesen SMB-Share dort einbinden, dass dir Metube die...

The keyword here is the "up to". 6.6 GB/s is when writing to DRAM-cache for some seconds. Once the DRAM-cache is full performance will drop to SLC-cache performance. Once the SLC-cache is full it will drop to TLC-NAND performance. And then its not unusual that such an SSD can't handle more than...

8MB/s is a lot of writes for a system disk that isn't storing any guests. 177 IOPS shouldn't be a problem for consumer SSDs even if those would be sync writes. Yes, so basically what I wrote above about cache filling up and disks can't keep up writing it to disk. With caching set to "none" ZFS...

Here, yes. All you have to do to steal my server is to break a window. No tools or ladder are required. You don't even have to enter the building, you could grab it from outside and pull it through the window. You just need some muscles because those servers are fully populated 4U chassis. ;)...

Checking the "shared" checkbox won't share that directory. You have to share it on your own by setting up a NFS server via CLI or similar. That checkbox is only to tell PVE that it is working with a shared filesystem. Jep, makes much more sense. If all the second node should do is backup your...

You should explain a bit more with infos like what guestOS, what exact error message and so on. If you are that unspecific no one could help.

I don't think ZFS is the problem. Most stuff the system disks are writing are logs, metrics and updates of the cluster DB. HDDs could handle this, then consumer SSD shouldn't have a problem either. You could use tools like iotop or iostat to narrow down whats causing the io delay. zpool iostat...

Ich würde mich an deiner Stelle per SSH mit dem LXC verbinden und dann dort mal mit etwas wie du -a / 2>/dev/null | sort -n -r | head -n 20 nach den größten Ordnern suchen. pct config <VmidDeinesLXCs> würde auch helfen zu wissen, ob es da irgendwelche Bind-Mounts oder ähnliches gibt. Aber am...