Search results

Tested 16.2.6. Resharding works!

Ceph 16.2.6 has been released which contains a fix for this issue.

Ceph has changed the fix status to “Under Review”. You can track the PR here. The issue is here.

In my limited testing and experience with Ceph Pacific, it will create new OSD's just fine. Those OSD's will use the new DB sharding parameters. The problem is resharding a RocksDB created prior to Pacific in order to enable the new Pacific features. That is where the error occurs. I can't...

This is relatively obvious and intuitive, but just a community reminder: If you take advantage of the new ACME letsencrypt certificates in PBS 2.0 (thank you Proxmox Devs!), your SHA fingerprint will change. You must update the fingerprint for any backup or sync jobs configured on other PBS...

It will be advertised as having PLP / Power Loss Protection. Check spec sheets.

Have you cleared all caches in Safari? I am not having any issues with 7.0-8 in Safari after clearing all local website data. Safari -> Preferences -> Privacy -> Manage Website Data

haha and waiting to install a full new release after letting others test it or reading all the release notes wasn't an option either. PBS incompatibility with PVE 7 has been known since the launch of the beta. Anyone coming here shocked and upset didn't do their own due diligence prior to...

The subnet you are using is a public network, not a private IP address range. Assuming that your Proxmox install is not receiving a dedicated public IP but instead you are on a local network with private address ranges, you need to fix your networking. Why not just handout an IP with DHCP...

Your repos are all messed up. http:/ needs to be http:// Also, the Proxmox 6 repo is "deb http://download.proxmox.com/debian buster pve-no-subscription", not Release.

Clear all web browser cache.

It is a kernel panic. The system's lock up typically means there is no time or ability to write out to any persistent log file. You can enable debugging to dump more data on screen, but you would still need to catch the data when it is crashing. Yes, it takes time and effort. There is no...

Many tunables control recovery and backfill speed. 1, 2. Since you care more about load on the network and less about the speed of rebalancing, adjust down from defaults. You can do the same thing. You can also set each OSD that is newly added to a very low reweight. Slowly raising the...

Just curious, when you say "in-place", do you mean it can't have downtime or be taken out of production? It isn't possible to resize and edit the partitions without booting into a live ISO. You will spend more time editing the existing install compared to re-installing. What is the barrier...

It isn’t clear what you have done to narrow down and identify your issues. I see you keep testing Proxmox, but that won’t eliminate whether this is a hardware or software issue. Have you removed all but one DIMM and tested each module individually with memtest? Have you tested any other...

It’s “possible”, but a clean install with a new partition layout for the EFI ESP partition will be safer, faster, and easier.

It did it again. 2021-07-01T21:52:00.975669-0500 mds.viper (mds.0) 78 : cluster [WRN] force file system read-only 2021-07-01T21:52:09.270904-0500 mon.viper (mon.0) 70522 : cluster [WRN] Health check failed: 1 MDSs are read only (MDS_READ_ONLY) 2021-07-01T21:52:09.332355-0500 mon.viper (mon.0)...

Testing 7 Beta with Ceph Pacific 16.2.4. The cluster keeps randomly entering "1 MDSs are read only". This issue never occurred previously under Nautilus or Octopus. The cluster is otherwise healthy. The MDS must be restarted to temporarily clear the error until it reappears hours later...

I have migrated the ZFS mirrored boot SSD's from a Supermicro X9 system to an X10 system previously. It is smooth sailing with the obvious exception being that you should expect all networking to be broken on first boot. You will need to use the IPMI/BMC console to edit your...

It is really hard to know exactly what is wrong or what you are doing because you are inconsistent in your command descriptions. You need to be using zfs SEND not zfs SENT. I can't tell if that is a typo only on the forum or the command you are issuing. The reason you originally only copied...