Search results

Does your drives show up in the BIOS, then your data will most likely be intact on any of those drives. You surely can install PVE on another, unrelated drive and then check out either of your prior boot disks, to get the configs off of them. To play it safe, I'd install with only one drive in...

Ha ha - I know… I have been running ZFS for more than a decade now… However, I was just curious about using fio on a device, which I never had done before - I have always used fio on files… and for a good reason, of course. And you should see the numbers, if I disable direct read…

If you didn't put any guets onto the rpool, then it would probably be best to re-install PVE on one of those boot disks and scrape the config from the other after having imported the rpool using a different name and mount point. There are a couple of posts, which deal with such a scenario. Once...

How exactly, did you install this system? Also, is it a sole PVE install or was it first OS and then Proxmox on top?

For a start, have you checked the logs on your pve host? If no start with /var/log/messages and look for any storage-error.

You should check the storage on your pve host. Looks like vdisk inside the guest becomes read-only, which can have a number of reasons. One of the more common issues is, that the volume on the pve host has become full and thus no new data can be written to it.

Well, I was curious and I attached another 8GB disk to one of my running guests, which is locates on a 2-vdev mirror ZPOOL using 4 2TB HGST drives. And I must say… I cannot complain… ;) root@cloud:~# fio --ioengine=libaio --direct=1 --sync=1 --rw=read --bs=4K --numjobs=1 --iodepth=1...

I just learned about the smem utility, which you can install on your pve host and check which processes do use how much swap. Using that utility, I found out, that one of my guests - a steam /arkserver used approx. 3 GB of swap, which obviously the pve host has to provide. Maybe this utility...

Well, this is of course all true in regards how the kernel uses swap space, but it is also quite interesting, that my single server at home, which runs its 13 guests of a zpool, has managed to aquire more swap space than each of my clustered hosts I am running at work. Where the pve hosts at...

Yeah… well… the storage summary is really not that useful. It only shows you the physical storage without taking the type of FS on that storage into account. I am running ZFS with 4 x 1.8TiB disks in a 2 x 2 mirror pool and the storage summary shows, that I do have 4.42 TiB of 6.46 TiB left...

My advice would probably be to go with ZFS if you're using local storage - and this includes iSCSI LUNs in your case, and Ceph if your can setup a "real" storage cluster. Actually, most of my backup storage systems are running ZFS on top of iSCSI LUNs.

ZFS on Linux has come a long way and I finally settled on getting away from Solaris/Illumos back to Linux. Solaris/Illumos is an outstanding OS, but it was mainly ZFS which held me there…

Personally, I'd do a ZFS setup where I'd group the two SATA SSDs in a mirrored zpool for root and the 4 2TB NVMe SSDs as a 2nd mirror zpool, but that'd depend on your preference on higher speed or capacity, since you'd could also run a raidz1 using these 4 NVMe SSDS and get some decent...

Well, that's hard to say, without actually having seen the installation process, but the interface config file (afaik), will always be created by the installer, so I am assueming, that something went wrong with that. You can create a simple interface config manually, but if the installer failed...

Couldn't agree more… NFS is what I have been using for years with great speed and stability.

Don't use OCFS2, if you don't really have a very good reason to do so! I recently switched from OVM to Proxmox but even even when I was running OVM, I ditched OCFS2 after the 2nd catastrophic failure 2 years into running my OVM cluster and used a HA-NFS instead.

Good choice for the time being, I guess.

Yeah… very funny… ;) Actually, the reboot had been triggered by a rampant-going LXC which lead to repeated oom-killers. The point is… you can never be sure…

Do you need some more help? If yes, please post the out put of ls -l /dev/disk/by-id using CODE-Tags and I will try to help you to get it right.

Yeah, I am only using uncompressed backups, since I do have enough storage capacity available to go without compression. But then, I am not saving my dumps to a network device, but to a local ZFS folder. Maybe you can setup a local folder for testing and see, if the guest stays connected, if...