Hi,
Recently we need do some change timezone test on our ubuntu node. And this node
mount a cephfs with kernel driver. when I changed the time of the system(for
example, current is 2022-01-05 09:00:00, then we change the time to 2022-01-03
08:00:00 using date command), after about 30m~1h,
Sorry for the late reply - vacation :/
Seems there is some confusion here: the AWS GO SDK sets the format as ISO
8601 basic -
https://github.com/aws/aws-sdk-go/blob/main/aws/signer/v4/v4.go#L84. So I
don't know where the divergence is happening :(. FWIW the aws go sdk works
fine against S3 and
I saw something similar, when I added a block.db on a ssd partition to the
OSD.I think the OSD is taking the total size of db + data as the OSD size,
and then counting the db as already allocated.
From: Daniel Persson
Sent: Tuesday, January 4, 2022 12:41
Hi.
I'm currently trying out cephadm, and I got into a state that was a bit
unexpected for me.
I created three host machines in VirtualBox to try out cephadm. All drives
I made for OSD are 20GB in size for simplicity.
Bootstrapped one host with one drive and then added the other two. Then
they
"ceph fs rename" will be available in Quincy. see also:
https://tracker.ceph.com/issues/47276
On Sat, Jan 1, 2022 at 10:26 PM Aaron Oneal wrote:
>
> Hi all, I’m trying to rename a file system with the “fs rename” command and
> it seems to not be supported by my 16.2.7 Debian client. Any
Hello,
I filed this [1] feature request in the tracker a a while ago. I started
looking at the possibilty
of helping out with this feature but gave up after digging for a while.
Maybe somebody else with more ninja foo can look at it :)
[1] https://tracker.ceph.com/issues/47342
> On 28 Oct
My ceph cluster's MDS aren't working. They start up, go into a reconnect state
followed by rejoin then they crash and the cycle repeats.
I am running containerized octopus and currently have two file systems. The one
that is having problems had to be rebuilt and was working well enough to copy
If anyone else trips over this, I found a workaround: simply disable
and re-enable mirroring for the file system.
On Mon, Jan 3, 2022 at 4:36 PM Manuel Holtgrewe wrote:
>
> Happy new year everyone,
>
> can I work around this problem or am I doing something wrong here and
> someone can correct
