March 2020 - ceph-users - lists.ceph.io

How can I fix "object unfound" error?
by Chad William Seys 04 Mar '20

04 Mar '20

Hi Simone, Maybe you've hit this bug: https://tracker.ceph.com/issues/44286 ? Chad.

1 0

Re: High memory ceph mgr 14.2.7
by Mark Lopez 04 Mar '20

04 Mar '20

I noticed the same - https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/thread/WS6OWKZ5NQX…. Out of curiosity, do you use the dashboard, and if so, does keeping the dashboard open cause the mgr RAM usage to increase overtime? Regards, Mark

1 0

Re: v14.2.8 Nautilus released
by kefu chai 04 Mar '20

04 Mar '20

On Wed, Mar 4, 2020 at 3:46 AM Kaleb Keithley <kkeithle(a)redhat.com> wrote: > > > Just FYI, 14.2.8 build fails on Fedora-32 on S390x. Other architectures build fine. > Kaleb, see https://github.com/ceph/ceph/pull/33716. hopefully we can get in the next release or probably you could include this patch in the rpm packaging? > Build log at https://kojipkgs.fedoraproject.org//work/tasks/6999/42146999/build.log > > On Tue, Mar 3, 2020 at 7:38 AM Abhishek Lekshmanan <abhishek(a)suse.com> wrote: >> >> >> This is the eighth update to the Ceph Nautilus release series. This release >> fixes issues across a range of subsystems. We recommend that all users upgrade >> to this release. Please note the following important changes in this >> release; as always the full changelog is posted at: >> https://ceph.io/releases/v14-2-8-nautilus-released >> >> Notable Changes >> --------------- >> >> * The default value of `bluestore_min_alloc_size_ssd` has been changed >> to 4K to improve performance across all workloads. >> >> * The following OSD memory config options related to bluestore cache autotuning can now >> be configured during runtime: >> >> - osd_memory_base (default: 768 MB) >> - osd_memory_cache_min (default: 128 MB) >> - osd_memory_expected_fragmentation (default: 0.15) >> - osd_memory_target (default: 4 GB) >> >> The above options can be set with:: >> >> ceph config set osd <option> <value> >> >> * The MGR now accepts `profile rbd` and `profile rbd-read-only` user caps. >> These caps can be used to provide users access to MGR-based RBD functionality >> such as `rbd perf image iostat` an `rbd perf image iotop`. >> >> * The configuration value `osd_calc_pg_upmaps_max_stddev` used for upmap >> balancing has been removed. Instead use the mgr balancer config >> `upmap_max_deviation` which now is an integer number of PGs of deviation >> from the target PGs per OSD. This can be set with a command like >> `ceph config set mgr mgr/balancer/upmap_max_deviation 2`. The default >> `upmap_max_deviation` is 1. There are situations where crush rules >> would not allow a pool to ever have completely balanced PGs. For example, if >> crush requires 1 replica on each of 3 racks, but there are fewer OSDs in 1 of >> the racks. In those cases, the configuration value can be increased. >> >> * RGW: a mismatch between the bucket notification documentation and the actual >> message format was fixed. This means that any endpoints receiving bucket >> notification, will now receive the same notifications inside a JSON array >> named 'Records'. Note that this does not affect pulling bucket notification >> from a subscription in a 'pubsub' zone, as these are already wrapped inside >> that array. >> >> * CephFS: multiple active MDS forward scrub is now rejected. Scrub currently >> only is permitted on a file system with a single rank. Reduce the ranks to one >> via `ceph fs set <fs_name> max_mds 1`. >> >> * Ceph now refuses to create a file system with a default EC data pool. For >> further explanation, see: >> https://docs.ceph.com/docs/nautilus/cephfs/createfs/#creating-pools >> >> * Ceph will now issue a health warning if a RADOS pool has a `pg_num` >> value that is not a power of two. This can be fixed by adjusting >> the pool to a nearby power of two:: >> >> ceph osd pool set <pool-name> pg_num <new-pg-num> >> >> Alternatively, the warning can be silenced with:: >> >> ceph config set global mon_warn_on_pool_pg_num_not_power_of_two false >> >> Getting Ceph >> ------------ >> >> * Git at git://github.com/ceph/ceph.git >> * Tarball at http://download.ceph.com/tarballs/ceph-14.2.8.tar.gz >> * For packages, see http://docs.ceph.com/docs/master/install/get-packages/ >> * Release git sha1: 2d095e947a02261ce61424021bb43bd3022d35cb >> >> -- >> Abhishek Lekshmanan >> SUSE Software Solutions Germany GmbH >> GF: Felix Imendörffer HRB 21284 (AG Nürnberg) >> _______________________________________________ >> Dev mailing list -- dev(a)ceph.io >> To unsubscribe send an email to dev-leave(a)ceph.io > > _______________________________________________ > Dev mailing list -- dev(a)ceph.io > To unsubscribe send an email to dev-leave(a)ceph.io -- Regards Kefu Chai

1 0

MIgration from weight compat to pg_upmap
by Stefan Priebe - Profihost AG 04 Mar '20

04 Mar '20

Hello, is there any way to switch to pg_upmap without triggering heavy rebalancing two times? 1.) happens at: ceph osd crush weight-set rm-compat 2.) happens after running the balancer in pg_upmap mode Greets, Stefan

2 2

Deleting Multiparts stuck directly from rgw.data pool
by EDH - Manuel Rios 04 Mar '20

04 Mar '20

Hi, We're at 14.2.8, still got problems with abort multiparts. This night we created a full list of objects with the string multipart like 48efb8c3-693c-4fe0-bbe4-fdc16f590a82.3886182.8__multipart_MBS-a3d91785-9579-4b18-9635-f4694bd0db1c/CBB_SRVALFA/F$/Correo/Gmolins/Outlook/Outlook.pst$/20190702110014/Outlook.pst.2~nu6skEciSGZVSz3SlXZ-GMURki6wPB3.10 Total 5-6Millions parts Its secure delete rgw object directly from data pool? We tried with LC, it return list_multiparts -2, with AWS cli an error already reported in the tracker. I'm thinking about do a full bucket rewrite with radosgw-admin bucket rewrite but im not sure if this will solve something or generate more trash. Best Regards Manuel

1 0

14.2.8 Multipart delete still not working
by EDH - Manuel Rios 03 Mar '20

03 Mar '20

Hi, We have updated our cluster to 14.2.8 since we suffered the bug https://tracker.ceph.com/issues/43583, now life cycle policies give more information than before. In 14.2.7 they ended instantly so something we have advanced. But they are not yet able to eliminate multipart. Just a line of the error that return -2 1. 2020-03-03 18:13:19.361 7fb58bcfb6c0 5 lifecycle: ERROR: abort_multipart_upload failed, ret=-2009, meta:_multipart_MBS-0fc78b70-efa6-49ef-bdd2-fd3a4b4f2c84/CBB_BIM-AUTOLOG/CBB_DiskImage/Disk_00000000-0000-0000-0000-000000000000/Volume_NTFS_00000000-0000-0000-0000-000000000001$/20190315230135/160.cbrevision.2~5nOv_6K_GZVwAJNqmEZ RrmE4lMs_-91.meta 2. 2020-03-03 18:13:19.361 7fb58bcfb6c0 20 obj_has_expired(): mtime=2019-03-16 00:53:58.0.940346s days=1 base_time=2020-03-03 00:00:00.000000 timediff=3.0496e+07 cmp=86400 3. 2020-03-03 18:13:19.362 7fb58bcfb6c0 20 abort_multipart_upload: list_multipart_parts returned -2 LC Applied <?xml version="1.0" ?> <LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <Rule> <ID>Incomplete Multipart Uploads</ID> <Prefix/> <Status>Enabled</Status> <AbortIncompleteMultipartUpload> <DaysAfterInitiation>1</DaysAfterInitiation> </AbortIncompleteMultipartUpload> </Rule> </LifecycleConfiguration> Suggestion ? Regards Manuel

1 0

e5 failed to get devid for : udev_device_new_from_subsystem_sysname failed on ''
by Matthias Leopold 03 Mar '20

03 Mar '20

Hi, I installed a basic three host cluster with ceph-deploy for development today and I'm seeing messages like mon.somehost@2(electing) e5 failed to get devid for : udev_device_new_from_subsystem_sysname failed on '' in monitor logs when monitor starts up. What is this? I found this: https://tracker.ceph.com/issues/42053, but I wasn't using ceph-ansible. Cluster has 3 nodes, 3 monitors (all have that message), 2 managers and is healthy Ceph version is 14.2.8 on CentOS 7 thx Matthias

1 0

leftover: spilled over 128 KiB metadata after adding db device
by Stefan Priebe - Profihost AG 03 Mar '20

03 Mar '20

Hello, i added a db device to my osds running nautilus. The DB data migratet over some days from the hdd to ssd (db device). But now it seems all are stuck at: # ceph health detail HEALTH_WARN BlueFS spillover detected on 8 OSD(s) BLUEFS_SPILLOVER BlueFS spillover detected on 8 OSD(s) osd.0 spilled over 128 KiB metadata from 'db' device (12 GiB used of 185 GiB) to slow device osd.1 spilled over 3.4 MiB metadata from 'db' device (12 GiB used of 185 GiB) to slow device osd.2 spilled over 128 KiB metadata from 'db' device (12 GiB used of 185 GiB) to slow device osd.3 spilled over 128 KiB metadata from 'db' device (12 GiB used of 185 GiB) to slow device osd.4 spilled over 128 KiB metadata from 'db' device (12 GiB used of 185 GiB) to slow device osd.5 spilled over 128 KiB metadata from 'db' device (12 GiB used of 185 GiB) to slow device osd.6 spilled over 128 KiB metadata from 'db' device (12 GiB used of 185 GiB) to slow device osd.7 spilled over 128 KiB metadata from 'db' device (12 GiB used of 185 GiB) to slow device any idea how to force ceph to move the last 128kb to the db device? Greets, Stefan

3 5

Nautilus 14.2.8
by Fyodor Ustinov 03 Mar '20

03 Mar '20

Hi! Again. New version in repository without announce. :( I wonder who needs to write a letter and complain that there would always be an announcement, and then a new version in the repository? WBR, Fyodor.

3 3

Restrict client access to a certain rbd pool with seperate metadata and data pool
by Rainer Krienke 03 Mar '20

03 Mar '20

Hello, I do not know how to restrict a client.user to a certain rbd pool where this pool has a replicated metadata pool pool.rbd and an erasure coded data pool named pool.ec . I am running ceph nautilus. I tried this for a client.user: # ceph auth caps client.user mon 'profile rbd' osd 'profile rbd pool=pool.rbd' # ceph auth get client.user > ./client.user # rbd -n client.user -k ./client.user create pool.rbd/test --size=1G --data-pool=pool.ec 2020-03-03 15:54:43.813 7f2817fff700 -1 librbd::image::ValidatePoolRequest: handle_read_rbd_info: failed to read RBD info: (1) Operation not permitted 2020-03-03 15:54:43.813 7f2817fff700 -1 librbd::image::CreateRequest: 0x563421cf4730 handle_validate_data_pool: failed to validate pool: (1) Operation not permitted rbd: create error: (1) Operation not permitted If I remove the "... pool=pool.rbd" -section in "ceph auth caps ..." call from above everything works. Any idea how I can get this setup to work? Thanks Rainer -- Rainer Krienke, Uni Koblenz, Rechenzentrum, A22, Universitaetsstrasse 1 56070 Koblenz, Tel: +49261287 1312 Fax +49261287 100 1312 Web: http://userpages.uni-koblenz.de/~krienke PGP: http://userpages.uni-koblenz.de/~krienke/mypgp.html

3 2

building ceph Nautilus for Debian Stretch
by Stefan Priebe - Profihost AG 03 Mar '20

03 Mar '20

Hello list, does anybody have a guide to build ceph Nautilus for Debian stretch? I wasn't able to find a backported gcc-8 for stretch. Otherwise i would start one. Greets, Stefan

2 2

How can I fix "object unfound" error?
by Simone Lazzaris 03 Mar '20

03 Mar '20

Hi there; I've got a ceph cluster with 4 nodes, each with 9 4TB drives. Last night a disk failed, and unfortunately this lead to a kernel panic on the hosting server (supermicro: never again). One reboot later, the cluster rebalances. This morning, I'm in this situation: root@s3:~# ceph status cluster: id: 9ec27b0f-acfd-40a3-b35d-db301ac5ce8c health: HEALTH_ERR 1/13122293 objects unfound (0.000%) Possible data damage: 1 pg backfill_unfound Degraded data redundancy: 1 pg undersized 27 slow ops, oldest one blocked for 68 sec, osd.5 has slow ops services: mon: 3 daemons, quorum s1,s2,s3 (age 11h) mgr: s1(active, since 6w), standbys: s2, s3 osd: 36 osds: 35 up (since 11h), 35 in (since 11h); 21 remapped pgs rgw: 3 daemons active (s1, s2, s3) data: pools: 10 pools, 1200 pgs objects: 13.12M objects, 41 TiB usage: 63 TiB used, 65 TiB / 127 TiB avail pgs: 186357/39366879 objects misplaced (0.473%) 1/13122293 objects unfound (0.000%) 1179 active+clean 11 active+remapped+backfilling 9 active+remapped+backfill_wait 1 active+backfill_unfound+undersized+remapped io: client: 42 KiB/s rd, 5.2 MiB/s wr, 43 op/s rd, 11 op/s wr recovery: 163 MiB/s, 48 objects/s One PG is in "backfill_unfound" status. The PG is the 6.36a, which is on server 1; the failed disk is the OSD.5, on server 3 (which was rebooted after the panic) so I don't understand the relation. This is the unfound object: root@s3:~# ceph pg 6.36a list_unfound { "num_missing": 1, "num_unfound": 1, "objects": [ { "oid": { "oid": "8a257939-05c9-4ba8-9fd3-fb8504226607.4332.4__shadow_.H5AtB0LjzRSbUWy- hnVSLf4fs884okG_1", "key": "", "snapid": -2, "hash": 961006442, "max": 0, "pool": 6, "namespace": "" }, "need": "263'18213", "have": "0'0", "flags": "none", "locations": [] } ], "more": false } How can I handle this error? The docs are not much comforting, as far as I can see the only thing to do is to mark the missing object as lost and try to cope with that. I'd prefer not. Any ideas? *Simone Lazzaris* *Qcom S.p.A.* simone.lazzaris(a)qcom.it[1] | www.qcom.it[2] * LinkedIn[3]* | *Facebook*[4] -------- [1] mailto:simone.lazzaris@qcom.it [2] https://www.qcom.it [3] https://www.linkedin.com/company/qcom-spa [4] http://www.facebook.com/qcomspa

2 2

Octopus release announcement
by Alex Chalkias 03 Mar '20

03 Mar '20

Hello, I was looking for an official announcement for Octopus release, as the latest update (back in Q3/2019) on the subject said it was scheduled for March 1st. Any updates on that? BR, -- Alex Chalkias *Product Manager* alex.chalkias(a)canonical.com +33 766599367 *Canonical | **Ubuntu*

3 3

Expected Mgr Memory Usage
by m＠silvenga.com 02 Mar '20

02 Mar '20

Hello all, I'm maintaining a small Nautilus 12 OSD cluster (36TB raw). My mon nodes have the mgr/mds collocated/stacked with the mon. Each are allocated 10gb of RAM. During a recent single disk failure and corresponding recovery, I noticed my mgr/mon's were starting to get OOM killed/restarted every 5ish hours - the mgr using around 6.5GB on all my nodes. My monitoring shows an interesting sawtooth pattern with network usage (100MB/s at max), disk storage usage, and disk IO (up to 300MB/s against SSD's at max) usage increasing in parallel with memory usage. I know the docs for hardware recommendations say: > Monitor and manager daemon memory usage generally scales with the size of the cluster. For small clusters, 1-2 GB is generally sufficient. For large clusters, you should provide more (5-10 GB). Now, I would like to think my cluster is on the small size of things, so I was hoping 10gb is enough for the mgr and mon (my OSD nodes are only allocated 32GB of ram), but that assumption appears to be false. So I was wondering how mgr's (and to a lesser extent mon's) are expected to scale in terms of memory. Is it the osd count, or the osd's size, number of pg's, etc.? And if there's a way to limit the amount of RAM used by these mgr's (it seems the mon_osd_cache_size and rocksdb_cache_size settings are for mons if I'm not mistaken). Regards, Mark

1 0

I have different bluefs formatted labels
by Marc Roos 02 Mar '20

02 Mar '20

I have some osd's having a bluefs label formatted like this: { "/dev/sdc2": { "osd_uuid": "cfb2eaa3-1811-4108-b9bb-aad49555246c", "size": 4000681099264, "btime": "2017-07-14 14:58:09.627614", "description": "main", "require_osd_release": "14" } } And I have some osd's having a bluefs label formatted like this: { "/dev/sdd2": { "osd_uuid": "d8912a1b-696c-4668-9337-c740ec47e0d0", "size": 8001457295360, "btime": "2018-06-01 18:27:47.760695", "description": "main", "bluefs": "1", "ceph_fsid": "0f1701f5-453a-4a3b-928d-f652a2bbbcb0", "kv_backend": "rocksdb", "magic": "ceph osd volume v026", "mkfs_done": "yes", "ready": "ready", "require_osd_release": "14", "whoami": "18" } } I assume this is a version difference? What are the implications of having this? How to upgrade?

1 0

HEALTH_WARN 1 pools have many more objects per pg than average
by Marcel Ceph 02 Mar '20

02 Mar '20

Hi We have a new mimic (13.2.6, will upgrade to nautilus next month) cluster where the rados gateway pool has currently many more objects per PG then the other pools. This leads to a warning with ceph status 1 pools have many more objects per pg than average I tries to get rid of this warning by setting on the commandline ceph config set mgr mon_pg_warn_max_object_skew 0 I recall that it leaded to HEALTH_OK but some time later it was at HEALTH_WARN again with the same message. I tried setting the value to -1 as well, restarting mon and mgr daemons. Unfortunately the message stays. Setting in ceph.conf does not help either I know that in the future the number of objects per PG increase for the other pools but in the meantime monitoring for another incoming health warn issue is hard to automate so we aim to always have a HEALTH_OK state Anyone any luck in getting rid of the warning by setting mon_pg_warn_max_object_skew? Thx Marcel

1 0

scan_links crashing
by Guilherme Geronimo 02 Mar '20

02 Mar '20

Hey guys, I'm trying to solve some Lost+Found errors, but when I try to run the "scan_link" command, it crashes. Any tip? Cheers! ceph cluster version 13.2.6 (7b695f835b03642f85998b2ae7b6dd093d9fbce4) mimic (stable) cephfs-data-scan version 14.2.7 (3d58626ebeec02d8385a4cefb92c6cbc3a45bfe8) nautilus (stable) root@deployer:/etc/ceph# cephfs-data-scan scan_links 2020-03-02 01:52:42.876 7fda150fa700 -1 NetHandler create_socket couldn't create socket (97) Address family not supported by protocol 2020-03-02 01:52:43.664 7fda23d26f40 -1 datascan.scan_links: Error getting omap from '10000af78b3.00000000': (2) No such file or directory Error ((2) No such file or directory) root@deployer:/etc/ceph# cephfs-data-scan --version ceph version 14.2.7 (3d58626ebeec02d8385a4cefb92c6cbc3a45bfe8) nautilus (stable)

1 0

MAX AVAIL and RAW AVAIL
by konstantin.ilyasov＠mediascope.net 01 Mar '20

01 Mar '20

We have some inexplicable situation. We have ceph cluster on 14.2.4. About 14 nodes with 12 disks (4Tb) in each node. But command ceph df returns for us next report: # ceph df RAW STORAGE: CLASS SIZE AVAIL USED RAW USED %RAW USED hdd 611 TiB 155 TiB 455 TiB 456 TiB 74.60 TOTAL 611 TiB 155 TiB 455 TiB 456 TiB 74.60 POOLS: POOL ID STORED OBJECTS USED %USED MAX AVAIL poolera01 20 238 TiB 84.59M 362 TiB 76.39 75 TiB poolera01md 21 17 GiB 58.33k 17 GiB 0.01 37 TiB poolera02dt 25 71 TiB 24.56M 92 TiB 45.02 90 TiB poolera02md 26 749 MiB 42.23k 1.2 GiB 0 37 TiB poolera01 - pool Erasure-coded 4+2 poolera02dt - pool Erasure-coded 8+2 poolera01md and poolera02md - both replicated size 3 We are using 2 cephfs. It seems, that all our pools can only utilize about 111TiB raw capacity. But we have 155 TiB! We have enabled balancer with mode upmap # ceph balancer status { "active": true, "plans": [], "mode": "upmap" } Can someone explain why ceph df show less MAX AVAIL than possible from AVAIL 155 TiB?

1 0

Re: Is it ok to add a luminous ceph-disk osd to nautilus still?
by Marc Roos 01 Mar '20

01 Mar '20

I did not have time to convert all drives to lvm yet, so I would like to stick to the use of the partition until I have time to change everything. -----Original Message----- Sent: 01 March 2020 18:17 Subject: Re: [ceph-users] Is it ok to add a luminous ceph-disk osd to nautilus still? So use ceph-volume. ?? The nautilus release notes explain why. > On Mar 1, 2020, at 9:02 AM, Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > > ceph-disk is not available in Nautilus.elease > > why scrub first? It is a new disk not having any data yet. Scrubbing > is verifying pg's not? > > I just created a vm on the ceph node where I want to add this osd. Did > a passthru of the disk and installed a few rpm's with nodeps to get > the ceph-disk command. > > > > -----Original Message----- > Sent: 01 March 2020 17:47 > Subject: Re: [ceph-users] Is it ok to add a luminous ceph-disk osd to > nautilus still? > > Ensure that it gets scrubbed at least once by Luminous first. But how > and why are you doing this ? Why not use Nautilus binaries ? > >>> On Mar 1, 2020, at 8:36 AM, Marc Roos <M.Roos(a)f1-outsourcing.eu> >> wrote: >> >> >> If I create and osd with luminous 12.0.3 binaries, can I just add it >> to an existing Nautilus cluster? >> >> I sort of did this already, just wondered if there are any drawbacks. >> >> >> [@test2 software]# ceph-disk prepare --bluestore --zap-disk /dev/sdb >> Creating new GPT entries. >> GPT data structures destroyed! You may now partition the disk using >> fdisk or other utilities. >> Creating new GPT entries. >> The operation has completed successfully. >> Setting name! >> partNum is 0 >> REALLY setting name! >> The operation has completed successfully. >> Setting name! >> partNum is 1 >> REALLY setting name! >> The operation has completed successfully. >> The operation has completed successfully. >> meta-data=/dev/sdb1 isize=2048 agcount=4, agsize=6400 >> blks >> = sectsz=512 attr=2, projid32bit=1 >> = crc=1 finobt=0, sparse=0 >> data = bsize=4096 blocks=25600, imaxpct=25 >> = sunit=0 swidth=0 blks >> naming =version 2 bsize=4096 ascii-ci=0 ftype=1 >> log =internal log bsize=4096 blocks=864, version=2 >> = sectsz=512 sunit=0 blks, > lazy-count=1 >> realtime =none extsz=4096 blocks=0, rtextents=0 >> The operation has completed successfully. >> >> _______________________________________________ >> ceph-users mailing list -- ceph-users(a)ceph.io To unsubscribe send an >> email to ceph-users-leave(a)ceph.io > >

1 0

Re: Is it ok to add a luminous ceph-disk osd to nautilus still?
by Marc Roos 01 Mar '20

01 Mar '20

ceph-disk is not available in Nautilus. why scrub first? It is a new disk not having any data yet. Scrubbing is verifying pg's not? I just created a vm on the ceph node where I want to add this osd. Did a passthru of the disk and installed a few rpm's with nodeps to get the ceph-disk command. -----Original Message----- Sent: 01 March 2020 17:47 Subject: Re: [ceph-users] Is it ok to add a luminous ceph-disk osd to nautilus still? Ensure that it gets scrubbed at least once by Luminous first. But how and why are you doing this ? Why not use Nautilus binaries ? > On Mar 1, 2020, at 8:36 AM, Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > > If I create and osd with luminous 12.0.3 binaries, can I just add it > to an existing Nautilus cluster? > > I sort of did this already, just wondered if there are any drawbacks. > > > [@test2 software]# ceph-disk prepare --bluestore --zap-disk /dev/sdb > Creating new GPT entries. > GPT data structures destroyed! You may now partition the disk using > fdisk or other utilities. > Creating new GPT entries. > The operation has completed successfully. > Setting name! > partNum is 0 > REALLY setting name! > The operation has completed successfully. > Setting name! > partNum is 1 > REALLY setting name! > The operation has completed successfully. > The operation has completed successfully. > meta-data=/dev/sdb1 isize=2048 agcount=4, agsize=6400 > blks > = sectsz=512 attr=2, projid32bit=1 > = crc=1 finobt=0, sparse=0 > data = bsize=4096 blocks=25600, imaxpct=25 > = sunit=0 swidth=0 blks > naming =version 2 bsize=4096 ascii-ci=0 ftype=1 > log =internal log bsize=4096 blocks=864, version=2 > = sectsz=512 sunit=0 blks, lazy-count=1 > realtime =none extsz=4096 blocks=0, rtextents=0 > The operation has completed successfully. > > _______________________________________________ > ceph-users mailing list -- ceph-users(a)ceph.io To unsubscribe send an > email to ceph-users-leave(a)ceph.io

1 0

Is it ok to add a luminous ceph-disk osd to nautilus still?
by Marc Roos 01 Mar '20

01 Mar '20

If I create and osd with luminous 12.0.3 binaries, can I just add it to an existing Nautilus cluster? I sort of did this already, just wondered if there are any drawbacks. [@test2 software]# ceph-disk prepare --bluestore --zap-disk /dev/sdb Creating new GPT entries. GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. Creating new GPT entries. The operation has completed successfully. Setting name! partNum is 0 REALLY setting name! The operation has completed successfully. Setting name! partNum is 1 REALLY setting name! The operation has completed successfully. The operation has completed successfully. meta-data=/dev/sdb1 isize=2048 agcount=4, agsize=6400 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=0, sparse=0 data = bsize=4096 blocks=25600, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=864, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 The operation has completed successfully.

1 0