On Wed, Dec 13, 2023 at 10:57:10AM +0100, Rok Jaklič wrote:
> Hi,
>
> shouldn't etag of a "parent" object change when "child" objects are added
> on s3?
>
> Example:
> 1. I add an object to test bucket: "example/" - size 0
> "example/" has an etag XYZ1
> 2. I add an object to test bucket:
Is there a 'Howto' or 'workflow' to implement a one-line patch in a
running cluster? With full understanding it will be gone on the next
upgrade?
Hopefully without having to set up an entire packaging/development
environment?
Thanks!
To implement:
* /Subject/: Re: Permanent KeyError:
This turned out to be really easy to fix.
1. Find the correct number of extents that would fit on the physical
devices. In my case 13262
2. Just extend the DB LVMs accordingly (in my case, it was all of them,
identically):
find /dev/ceph-*/osd-db-* | xargs -I{} lvextend -l 13626 {}
3. Restart
