Hi, Okay. Here is another case which was churning the osdmaps: https://tracker.ceph.com/issues/51433 Perhaps similar debugging will show what's creating the maps in your case. Cheers, Dan On Mon, Nov 8, 2021, 12:48 PM Manuel Lausch <manuel.lausch@xxxxxxxx> wrote: > Hi Dan, > > I diffed two maps, but the only difference are the epoch number and the > timestamp. > > # diff -u osdmap-183113.txt osdmap-183114.txt > --- osdmap-183113.txt 2021-11-08 12:44:24.421868492 +0100 > +++ osdmap-183114.txt 2021-11-08 12:44:28.302027930 +0100 > @@ -1,7 +1,7 @@ > -epoch 183113 > +epoch 183114 > fsid f064364a-fd27-4480-ba87-a89d8a665f76 > created 2019-04-15T10:00:34.723776+0200 > -modified 2021-11-08T12:41:22.871460+0100 > +modified 2021-11-08T12:41:24.083283+0100 > flags sortbitwise,recovery_deletes,purged_snapdirs,pglog_hardlimit > crush_version 211 > full_ratio 0.95 > > > Manuel > > > > On Fri, 5 Nov 2021 18:32:41 +0100 > Dan van der Ster <dan@xxxxxxxxxxxxxx> wrote: > > > Hi, > > > > You can get two adjacent osdmap epochs (ceph osd getmap <epoch> -o > > map.<epoch>) Then use osdmaptool to print those maps, hopefully > > revealing what is changing between the two epochs. > > > > Cheers, Dan > > > > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |