Search results

I ran the trim on all PGs in all OSDs where the duplicate entries were greater than 6,000. That seems to have done the trick, my OSDs can now start and my cluster is healthy.

Apparently Ceph Quincy has a log entry that suggests running this command if the number of duplicates exceeds 6,000. https://forum.proxmox.com/threads/pve7-2-errors-in-osd-logs-after-upgrade-from-ceph-pacific-to-quincy.117009/

Yes, I really need to upgrade but can't do that while the cluster is unhealthy. I tried to go through the process documented on that webpage, but it's lacking some detail. The command: while read pg; do echo $pg; ceph-objectstore-tool --data-path /var/lib/ceph/osd/ceph-{OSD-ID} --op log...

A couple of additional data points: Two of the nodes have 32GB of memory, the other has 64GB of memory. All three nodes are experiencing the ceph-osd OOM issue. osd_memory_target for the OSDs appears to be 4GB ceph config get osd osd_memory_target 4294967296

I have a 3-node PVE 7.4-18 cluster running Ceph 15.2.17. There is one OSD per node, so pretty simple. I'm using 3 replicas, so the data should basically be mirrored across all OSDs in the cluster. Everything has been running fine for months, but I've suddenly lost the ability to get my OSDs up...

Yes, it's working perfectly for my application. I haven't observed any performance issues.

This is just a small home system. NFS performance is sufficient for my use case.

I am using proxmox-backup-client to backup my PVE nodes to a PBS repository. I'd like to get to the point where I can recover a PVE node by installing the PVE software and then running a restore from the backup, which will hopefully recover any PVE configurations for my system. Is there a...

I solved this by setting no_root_squash on the NFS share. Apparently in FreeNAS/TrueNAS you do this by setting the maproot user to 'root' and the maproot group to 'wheel' on the NFS share. https://www.truenas.com/community/threads/equivalent-for-root_squash-no_root_squash-on-freenas.80024/

I know there have been a lot of posts about this, but I'm still struggling. I have a new PBS instance started up running 3.2-2. I have a FreeNAS/TrueNAS server with an NFS share set up for my backups. I have mounted the NFS share using /etc/fstab under /mnt/backups in PBS. I have verified that...

I have a Proxmox 6.x home environment, and I'm using Ceph on my Proxmox cluster for storage of VM and LXC containers. On a separate server I have FreeNAS for my bulk storage, which I share out using NFS. Right now, I have the NFS mounts configured in Proxmox under /etc/fstab, with mount points...

It would be great if we could get this functionality. I have all my containers on RBD now, but can't snapshot them unless we can get this functionality with bind mounts. For me, the data within the bind mount is on ZFS with snapshots already...so it doesn't need to be included in the container...

The journalctl further up in the thread should still be valid, and I'm also attaching a new one here. I can't see anything obvious. Might be udev related, but I don't know enough about that to troubleshoot further. Yes, there is a running DHCP server on the network but none of the IP addresses...

I still seem to be having this problem after a reboot, but it's a bit sporadic. When the network fails to come up on a node, I have to manually start it with `ifup vmbr0`.

No, I was playing around with the IPMI and network boot settings. I've changed every combination back to see if I could reproduce, but unfortunately I can't.

This is somehow working now. I changed some IPMI settings in the BIOS, and it just started working. Reverted back the changes to see what might have solved the problem, but it's still working. So I guess I'm not sure why the network wasn't coming up initially. But all is well now. I've upgraded...

Maybe a timing issue? If I manually run 'ifup vmbr0', the network comes up successfully. Seems to be the same problem @kukachik reported in that thread. I have the same hardware (Dell C6100).

Output of 'pveversion -v': proxmox-ve: 6.0-2 (running kernel: 5.0.21-1-pve) pve-manager: 6.0-6 (running version: 6.0-6/c71f879f) pve-kernel-5.0: 6.0-7 pve-kernel-helper: 6.0-7 pve-kernel-4.15: 5.4-8 pve-kernel-5.0.21-1-pve: 5.0.21-1 pve-kernel-4.15.18-20-pve: 4.15.18-46...

Took the plunge and started upgrading my cluster to Proxmox 6. I upgraded one node in my 3-node cluster. After the reboot, my network won't come up. It's possible the upgrade wasn't completed successfully, since the upgrade finished with the message... Running hook script 'zz-pve-efiboot'...

The bug report referenced above has status "PATCH AVAILABLE", but I can't see any details on it. Is this issue solved with a patch?