[ceph-users] Re: 16.2.7 pacific QE validation status, RC1 available for testing

On Tue, Nov 30, 2021 at 01:57:14PM +0530, Deepika Upadhyay wrote: > krbd, rbd lgtm! > >- krbd: > > > > > > > >- rbd > >

[ceph-users] Re: allocate_bluefs_freespace failed to allocate

Hello again. It's hard to upgrade while having this problem because I have high I/O usage and 1/30 OSD's are flapping almost everyday. I'm afraid of having the OSD fail during the upgrade. I need a temporary solution because I'm sure that while upgrading the system at least one of the OSD's will f

[ceph-users] [bluestore-SMR] vstart fails on ZNS emulator

Hello, I am a student studying zns. I want to run Ceph on the zns emulator (null_blk module), but deployment through vstart did not work well. My OS is Ubuntu 18.04 (kernel version=5.10.37) and Ceph code is cloned to Sage Weil's github, latest version of bluestore-smr-clean branch. I also tried it

[ceph-users] mgrmap.epoch in ceph -s output

Dear all, when calling `ceph -s --format=json-pretty`, there is no setting `{"mgrmap": {"epoch": ...}}` in ceph 16.2.6. I'm using the monitoring software Check_MK which looks at this value, however [1]. I could not reconstruct from the Ceph source code whether the value should be in the output or

[ceph-users] Re: allocate_bluefs_freespace failed to allocate

> On 30 Nov 2021, at 13:40, mhnx wrote: > > Is there any other solution to cover the issue for safe upgrade? > Is there any problem with switching hybrid allocator to bitmap > allocator just for upgrade? > Do I need to re-create OSD's? Or just stop and start with the bitmap > allocator and afte

[ceph-users] UID/GID-mapping with cephfs

Hi all, We are trying to use UID/GID-mapping with cephfs over ceph-fuse client, but we have not succeeded. The "module=idmap" option seems not to be supported by ceph-fuse: ceph-fuse ... /mnt/cephfs -o modules=idmap -o umap=user.map fuse: unknown option `modules=idmap' ceph-fuse[..]: fuse f

[ceph-users] What if: Upgrade procedure mistake by restarting OSD before MON?

Hi, I am planning a Luminous to Nautilus upgrade. The instructions state (very terse version): - install Nautilus ceph packages - restart MONs - restart MGRs - restart OSDs We have OSDs running on our MON hosts (essentially all our ceph hosts are the same chassis). So, if everything goes

[ceph-users] Re: What if: Upgrade procedure mistake by restarting OSD before MON?

Hi, Just make a systemctl disable ceph targets to avoid start services on boot k Sent from my iPhone > On 1 Dec 2021, at 02:42, Mark Kirkwood wrote: > > I'm wondering about the situation where you are part way through restarting > your MONs (or MGRs) and one of the hosts reboots (or perhaps

[ceph-users] Re: How to remove the features config?

Den ons 1 dec. 2021 kl 03:17 skrev GHui : > > I have deployed the v16 Ceph Cluster. One day I test ceph-osd and ceph-mon at > v17 version. > But now I cannot start ceph-mon at v16. And the follow is error message. > > ** File Read Latency Histogram By Level [default] ** > debug 2021-12-01T02:07:56