ceph osd down 的处理办法及新增加OSD

最新推荐文章于 2023-10-13 10:41:06 发布
置顶 最新推荐文章于 2023-10-13 10:41:06 发布
阅读量4.2k 收藏 4
点赞数 2
分类专栏： 分布式存储-ceph
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_40017427/article/details/106219200
版权

1: OSD 状态

 

有二个OSD down

[root@node-11 ~]#

[root@node-11 ~]#

[root@node-11 ~]# ceph osd tree

ID  CLASS WEIGHT  TYPE NAME        STATUS REWEIGHT PRI-AFF

-10             0 IDC rack01                              

 -1       0.05598 root IDC-01                             

 -3       0.01900     host node-10                        

  0   hdd 0.01900         osd.0        up  1.00000 1.00000

 -5       0.01900     host node-11                        

  1   hdd 0.01900         osd.1      down  1.00000 1.00000

 -7       0.01799     host node-12                        

  2   hdd 0.01799         osd.2      down        0 1.00000

[root@node-11 ~]#

2： Ceph集群显示状态异常

[root@node-11 ~]# ceph -s

  cluster:

    id:     e59a2590-37b2-4153-8d90-3a14dfdb8f43

    health: HEALTH_WARN

            1 filesystem is degraded

            1 MDSs report slow metadata IOs

            1 backfillfull osd(s)

            1 osds down

            1 host (1 osds) down

            10 pool(s) backfillfull

            3 pool(s) have non-power-of-two pg_num

            Reduced data availability: 249 pgs inactive

            Degraded data redundancy: 10078/15117 objects degraded (66.667%), 96 pgs degraded, 249 pgs undersized

            3 daemons have recently crashed

 

  services:

    mon: 3 daemons, quorum node-10,node-11,node-12 (age 14m)

    mgr: node-10(active, since 2h)

    mds: cephfs:1/1 {0=node-12=up:replay} 2 up:standby

    osd: 3 osds: 1 up (since 14m), 2 in (since 17m)

 

  data:

    pools:   10 pools, 249 pgs

    objects: 5.04k objects, 18 GiB

    usage:   38 GiB used, 594 MiB / 39 GiB avail

    pgs:     100.000% pgs not active

             10078/15117 objects degraded (66.667%)

             153 undersized+peered

             96  undersized+degraded+peered

 

[root@node-11 ~]#

3: OSD 删除前的确认操作

删除前，运行前面提到的ok-to-stop和safe-to-destroy命令，根据返回的结果来决定是否能够执行删除OSD操作。

 

[root@node-11 ~]# ceph osd ok-to-stop osd.1

OSD(s) 1 are ok to stop without reducing availability or risking data, provided there are no other concurrent failures or interventions.

0 PGs are likely to be degraded (but remain available) as a result.

[root@node-11 ~]# ceph osd ok-to-stop osd.2

OSD(s) 2 are ok to stop without reducing availability or risking data, provided there are no other concurrent failures or interventions.

0 PGs are likely to be degraded (but remain available) as a result.

[root@node-11 ~]#

[root@node-11 ~]#

 

[root@node-11 ~]# ceph osd safe-to-destroy osd.1

Error EAGAIN: OSD(s) 1 have no reported stats, and not all PGs are active+clean; we cannot draw any conclusions.

[root@node-11 ~]# ceph osd safe-to-destroy osd.2

Error EAGAIN: OSD(s) 2 have no reported stats, and not all PGs are active+clean; we cannot draw any conclusions.

[root@node-11 ~]#

 

4: 确认osd-0的Crush信息

[root@node-11 ~]# ceph osd crush ls osd.1

osd.1

[root@node-11 ~]# ceph osd crush ls osd.2

osd.2

[root@node-11 ~]#

5:获取osd-0相关的cephx信息

[root@node-11 ~]# ceph auth get osd.1

exported keyring for osd.1

[osd.1]

        key = AQAn0HleOu2nExAAyyyda7dOo/5z7wpr0Kx6cg==

        caps mgr = "allow profile osd"

        caps mon = "allow profile osd"

        caps osd = "allow *"

[root@node-11 ~]# ceph auth get osd.2

exported keyring for osd.2

[osd.2]

        key = AQBU0Hle8gNoFxAAQglVj1Y7QrU01xeSf6vw4g==

        caps mgr = "allow profile osd"

        caps mon = "allow profile osd"

        caps osd = "allow *"

[root@node-11 ~]#

6:如果是替换现有OSD-0的磁盘，则执行destro

y操作，你会发现只有OSD-0的keyring被删除。

[root@node-11 ~]# ceph osd destroy osd.1 --yes-i-really-mean-it

destroyed osd.1

[root@node-11 ~]# ceph osd destroy osd.2 --yes-i-really-mean-it

destroyed osd.2

[root@node-11 ~]#

 

[root@node-11 ~]# ceph osd tree

ID  CLASS WEIGHT  TYPE NAME        STATUS    REWEIGHT PRI-AFF

-10             0 IDC rack01                                 

 -1       0.05598 root IDC-01                                

 -3       0.01900     host node-10                           

  0   hdd 0.01900         osd.0           up  1.00000 1.00000

 -5       0.01900     host node-11                           

  1   hdd 0.01900         osd.1    destroyed  1.00000 1.00000

 -7       0.01799     host node-12                           

  2   hdd 0.01799         osd.2    destroyed        0 1.00000

[root@node-11 ~]#

 

[root@node-11 ~]# ceph osd crush ls osd.1

osd.1

[root@node-11 ~]# ceph osd crush ls osd.2

osd.2

[root@node-11 ~]# ceph auth get osd.1

Error ENOENT: failed to find osd.1 in keyring

[root@node-11 ~]# ceph auth get osd.2

Error ENOENT: failed to find osd.2 in keyring

[root@node-11 ~]#

7:如果是彻底删除OSD-0，则执行purge操作，你会发现所有OSD-0关联的信息都被删除。

[root@node-11 ~]#

[root@node-11 ~]# systemctl stop ceph-osd@1

[root@node-11 ~]# systemctl stop ceph-osd@2

[root@node-11 ~]# ceph osd purge osd.1 --yes-i-really-mean-it

purged osd.1

[root@node-11 ~]# ceph osd purge osd.2 --yes-i-really-mean-it

purged osd.2

[root@node-11 ~]# ceph osd tree

ID  CLASS WEIGHT  TYPE NAME        STATUS REWEIGHT PRI-AFF

-10             0 IDC rack01                              

 -1       0.01900 root IDC-01                             

 -3       0.01900     host node-10                        

  0   hdd 0.01900         osd.0        up  1.00000 1.00000

 -5             0     host node-11                        

 -7             0     host node-12                        

[root@node-11 ~]#

 

[root@node-11 ~]# ceph osd crush ls osd.1

Error ENOENT: node 'osd.1' does not exist

[root@node-11 ~]# ceph osd crush ls osd.2

Error ENOENT: node 'osd.2' does not exist

[root@node-11 ~]# ceph auth get osd.1

Error ENOENT: failed to find osd.1 in keyring

[root@node-11 ~]# ceph auth get osd.2

Error ENOENT: failed to find osd.2 in keyring

[root@node-11 ~]#

8:最后如果你需要清理原来OSD-0对应数

据盘的数据，可以执行以下命令

[root@node-11 ~]# lsblk

NAME                                                                                                  MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT

sda                                                                                                     8:0    0   50G  0 disk

├─sda1                                                                                                  8:1    0    1G  0 part /boot

└─sda2                                                                                                  8:2    0 48.9G  0 part

  └─centos-root                                                                                       253:0    0 48.9G  0 lvm  /

sdb                                                                                                     8:16   0   19G  0 disk

└─ceph--83bde6e7--155e--4f2c--ab98--b03b9538f0cb-osd--block--4bd18b82--5285--41ff--bed3--08f3d26c2f39 253:1    0   19G  0 lvm 

[root@node-11 ~]#

 

[root@node-11 ~]#

[root@node-11 ~]# ceph-volume lvm zap --destroy /dev/sdb

--> Zapping: /dev/sdb

Running command: /usr/bin/dd if=/dev/zero of=/dev/sdb bs=1M count=10 conv=fsync

 stderr: 10+0 records in

10+0 records out

10485760 bytes (10 MB) copied

 stderr: , 0.0186076 s, 564 MB/s

--> Zapping successful for: <Raw Device: /dev/sdb>

[root@node-11 ~]#

 

[root@node-12 ~]#

[root@node-12 ~]#

[root@node-12 ~]# ceph-volume lvm zap --destroy /dev/sdb

--> Zapping: /dev/sdb

--> Zapping lvm member /dev/sdb. lv_path is /dev/ceph-e67c2622-46d5-4a96-af51-fa634d57b052/osd-block-163b7415-368c-40e9-b324-5f310789440e

--> Unmounting /var/lib/ceph/osd/ceph-2

Running command: /usr/bin/umount -v /var/lib/ceph/osd/ceph-2

 stderr: umount: /var/lib/ceph/osd/ceph-2 (tmpfs) unmounted

Running command: /usr/bin/dd if=/dev/zero of=/dev/ceph-e67c2622-46d5-4a96-af51-fa634d57b052/osd-block-163b7415-368c-40e9-b324-5f310789440e bs=1M count=10 conv=fsync

 stderr: 10+0 records in

10+0 records out

10485760 bytes (10 MB) copied

 stderr: , 0.0758462 s, 138 MB/s

--> Only 1 LV left in VG, will proceed to destroy volume group ceph-e67c2622-46d5-4a96-af51-fa634d57b052

Running command: /usr/sbin/vgremove -v -f ceph-e67c2622-46d5-4a96-af51-fa634d57b052

 stderr: Removing ceph--e67c2622--46d5--4a96--af51--fa634d57b052-osd--block--163b7415--368c--40e9--b324--5f310789440e (253:1)

 stderr: Archiving volume group "ceph-e67c2622-46d5-4a96-af51-fa634d57b052" metadata (seqno 17).

 stderr: Releasing logical volume "osd-block-163b7415-368c-40e9-b324-5f310789440e"

 stderr: Creating volume group backup "/etc/lvm/backup/ceph-e67c2622-46d5-4a96-af51-fa634d57b052" (seqno 18).

 stdout: Logical volume "osd-block-163b7415-368c-40e9-b324-5f310789440e" successfully removed

 stderr: Removing physical volume "/dev/sdb" from volume group "ceph-e67c2622-46d5-4a96-af51-fa634d57b052"

 stdout: Volume group "ceph-e67c2622-46d5-4a96-af51-fa634d57b052" successfully removed

Running command: /usr/bin/dd if=/dev/zero of=/dev/sdb bs=1M count=10 conv=fsync

 stderr: 10+0 records in

10+0 records out

10485760 bytes (10 MB) copied

 stderr: , 0.0153976 s, 681 MB/s

--> Zapping successful for: <Raw Device: /dev/sdb>

[root@node-12 ~]#

[root@node-12 ~]#

[root@node-12 ~]# lsblk

NAME            MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT

sda               8:0    0   50G  0 disk

├─sda1            8:1    0    1G  0 part /boot

└─sda2            8:2    0 48.9G  0 part

  └─centos-root 253:0    0 48.9G  0 lvm  /

sdb               8:16   0   18G  0 disk

[root@node-12 ~]#

9: 新增OSD

格式化磁盘

[root@node-10 cluster]# ceph-deploy disk zap node-11 /dev/sdb

[root@node-10 cluster]# ceph-deploy disk zap node-12 /dev/sdb

 

创建OSD，如在每个节点上我们都有一块磁盘，分别为sdb

 

[root@node-11 ~]# ceph-volume lvm create --data /dev/sdb

[root@node-11 ~]#

[root@node-11 ~]# lsblk

NAME                                                                                                  MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT

sda                                                                                                     8:0    0   50G  0 disk

├─sda1                                                                                                  8:1    0    1G  0 part /boot

└─sda2                                                                                                  8:2    0 48.9G  0 part

  └─centos-root                                                                                       253:0    0 48.9G  0 lvm  /

sdb                                                                                                     8:16   0   19G  0 disk

└─ceph--481d09c0--5bbd--491e--8f0e--bd5b136e2e2c-osd--block--2454cf36--8f92--435b--9177--200a0f261e03 253:1    0   19G  0 lvm 

[root@node-11 ~]#

[root@node-11 ~]#  ceph-volume lvm list

 

 

====== osd.1 =======

 

  [block]       /dev/ceph-481d09c0-5bbd-491e-8f0e-bd5b136e2e2c/osd-block-2454cf36-8f92-435b-9177-200a0f261e03

 

      block device              /dev/ceph-481d09c0-5bbd-491e-8f0e-bd5b136e2e2c/osd-block-2454cf36-8f92-435b-9177-200a0f261e03

      block uuid                A1Rwg0-xID5-Y6Py-2F3d-UNzS-S7Zs-i1AK6r

      cephx lockbox secret     

      cluster fsid              e59a2590-37b2-4153-8d90-3a14dfdb8f43

      cluster name              ceph

      crush device class        None

      encrypted                 0

      osd fsid                  2454cf36-8f92-435b-9177-200a0f261e03

      osd id                    1

      type                      block

      vdo                       0

      devices                   /dev/sdb

[root@node-11 ~]#

 

[root@node-12 ~]# lsblk

NAME            MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT

sda               8:0    0   50G  0 disk

├─sda1            8:1    0    1G  0 part /boot

└─sda2            8:2    0 48.9G  0 part

  └─centos-root 253:0    0 48.9G  0 lvm  /

sdb               8:16   0   18G  0 disk

[root@node-12 ~]# ceph-volume lvm create --data /dev/sdb

Running command: /usr/bin/ceph-authtool --gen-print-key

Running command: /usr/bin/ceph --cluster ceph --name client.bootstrap-osd --keyring /var/lib/ceph/bootstrap-osd/ceph.keyring -i - osd new ae9f5273-0bbe-4818-84a7-291fe17fde6b

Running command: /usr/sbin/vgcreate --force --yes ceph-6fac2b4c-6c25-4ac4-a844-0568fc77022d /dev/sdb

 stdout: Physical volume "/dev/sdb" successfully created.

 stdout: Volume group "ceph-6fac2b4c-6c25-4ac4-a844-0568fc77022d" successfully created

Running command: /usr/sbin/lvcreate --yes -l 100%FREE -n osd-block-ae9f5273-0bbe-4818-84a7-291fe17fde6b ceph-6fac2b4c-6c25-4ac4-a844-0568fc77022d

 stdout: Logical volume "osd-block-ae9f5273-0bbe-4818-84a7-291fe17fde6b" created.

Running command: /usr/bin/ceph-authtool --gen-print-key

Running command: /usr/bin/mount -t tmpfs tmpfs /var/lib/ceph/osd/ceph-2

Running command: /usr/sbin/restorecon /var/lib/ceph/osd/ceph-2

Running command: /usr/bin/chown -h ceph:ceph /dev/ceph-6fac2b4c-6c25-4ac4-a844-0568fc77022d/osd-block-ae9f5273-0bbe-4818-84a7-291fe17fde6b

Running command: /usr/bin/chown -R ceph:ceph /dev/dm-1

Running command: /usr/bin/ln -s /dev/ceph-6fac2b4c-6c25-4ac4-a844-0568fc77022d/osd-block-ae9f5273-0bbe-4818-84a7-291fe17fde6b /var/lib/ceph/osd/ceph-2/block

Running command: /usr/bin/ceph --cluster ceph --name client.bootstrap-osd --keyring /var/lib/ceph/bootstrap-osd/ceph.keyring mon getmap -o /var/lib/ceph/osd/ceph-2/activate.monmap

 stderr: 2020-05-19 16:52:45.735 7fb0a78c5700 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.bootstrap-osd.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory

2020-05-19 16:52:45.735 7fb0a78c5700 -1 AuthRegistry(0x7fb0a0064fe8) no keyring found at /etc/ceph/ceph.client.bootstrap-osd.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,, disabling cephx

 stderr: got monmap epoch 1

Running command: /usr/bin/ceph-authtool /var/lib/ceph/osd/ceph-2/keyring --create-keyring --name osd.2 --add-key AQBcnsNeEwATGRAA/L/9X86ilMkZVN2dM8qbIA==

 stdout: creating /var/lib/ceph/osd/ceph-2/keyring

added entity osd.2 auth(key=AQBcnsNeEwATGRAA/L/9X86ilMkZVN2dM8qbIA==)

Running command: /usr/bin/chown -R ceph:ceph /var/lib/ceph/osd/ceph-2/keyring

Running command: /usr/bin/chown -R ceph:ceph /var/lib/ceph/osd/ceph-2/

Running command: /usr/bin/ceph-osd --cluster ceph --osd-objectstore bluestore --mkfs -i 2 --monmap /var/lib/ceph/osd/ceph-2/activate.monmap --keyfile - --osd-data /var/lib/ceph/osd/ceph-2/ --osd-uuid ae9f5273-0bbe-4818-84a7-291fe17fde6b --setuser ceph --setgroup ceph

--> ceph-volume lvm prepare successful for: /dev/sdb

Running command: /usr/bin/chown -R ceph:ceph /var/lib/ceph/osd/ceph-2

Running command: /usr/bin/ceph-bluestore-tool --cluster=ceph prime-osd-dir --dev /dev/ceph-6fac2b4c-6c25-4ac4-a844-0568fc77022d/osd-block-ae9f5273-0bbe-4818-84a7-291fe17fde6b --path /var/lib/ceph/osd/ceph-2 --no-mon-config

Running command: /usr/bin/ln -snf /dev/ceph-6fac2b4c-6c25-4ac4-a844-0568fc77022d/osd-block-ae9f5273-0bbe-4818-84a7-291fe17fde6b /var/lib/ceph/osd/ceph-2/block

Running command: /usr/bin/chown -h ceph:ceph /var/lib/ceph/osd/ceph-2/block

Running command: /usr/bin/chown -R ceph:ceph /dev/dm-1

Running command: /usr/bin/chown -R ceph:ceph /var/lib/ceph/osd/ceph-2

Running command: /usr/bin/systemctl enable ceph-volume@lvm-2-ae9f5273-0bbe-4818-84a7-291fe17fde6b

 stderr: Created symlink from /etc/systemd/system/multi-user.target.wants/ceph-volume@lvm-2-ae9f5273-0bbe-4818-84a7-291fe17fde6b.service to /usr/lib/systemd/system/ceph-volume@.service.

Running command: /usr/bin/systemctl enable --runtime ceph-osd@2

Running command: /usr/bin/systemctl start ceph-osd@2

--> ceph-volume lvm activate successful for osd ID: 2

--> ceph-volume lvm create successful for: /dev/sdb

[root@node-12 ~]#

[root@node-12 ~]#

[root@node-12 ~]# lsblk

NAME                                                                                                  MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT

sda                                                                                                     8:0    0   50G  0 disk

├─sda1                                                                                                  8:1    0    1G  0 part /boot

└─sda2                                                                                                  8:2    0 48.9G  0 part

  └─centos-root                                                                                       253:0    0 48.9G  0 lvm  /

sdb                                                                                                     8:16   0   18G  0 disk

└─ceph--6fac2b4c--6c25--4ac4--a844--0568fc77022d-osd--block--ae9f5273--0bbe--4818--84a7--291fe17fde6b 253:1    0   18G  0 lvm 

[root@node-12 ~]#

 

[root@node-12 ~]#  ceph-volume lvm list

 

 

====== osd.2 =======

 

  [block]       /dev/ceph-6fac2b4c-6c25-4ac4-a844-0568fc77022d/osd-block-ae9f5273-0bbe-4818-84a7-291fe17fde6b

 

      block device              /dev/ceph-6fac2b4c-6c25-4ac4-a844-0568fc77022d/osd-block-ae9f5273-0bbe-4818-84a7-291fe17fde6b

      block uuid                99rJJe-jiiL-FVfK-6d0T-fYUx-SLAa-wU8k0S

      cephx lockbox secret     

      cluster fsid              e59a2590-37b2-4153-8d90-3a14dfdb8f43

      cluster name              ceph

      crush device class        None

      encrypted                 0

      osd fsid                  ae9f5273-0bbe-4818-84a7-291fe17fde6b

      osd id                    2

      type                      block

      vdo                       0

      devices                   /dev/sdb

[root@node-12 ~]#

 

[root@node-12 ~]# ceph osd tree

ID  CLASS WEIGHT  TYPE NAME        STATUS REWEIGHT PRI-AFF

-10             0 IDC rack01                              

 -1       0.05518 root IDC-01                             

 -3       0.01900     host node-10                        

  0   hdd 0.01900         osd.0        up  1.00000 1.00000

 -5       0.01859     host node-11                        

  1   hdd 0.01859         osd.1        up  1.00000 1.00000

 -7       0.01759     host node-12                        

  2   hdd 0.01759         osd.2        up  1.00000 1.00000

[root@node-12 ~]#

Ceph Pg重组，数据回拷

[root@node-10 cluster]# ceph -s

  cluster:

    id:     e59a2590-37b2-4153-8d90-3a14dfdb8f43

    health: HEALTH_WARN

            1 backfillfull osd(s)

            10 pool(s) backfillfull

            3 pool(s) have non-power-of-two pg_num

            Reduced data availability: 15 pgs inactive

            Degraded data redundancy: 2473/15117 objects degraded (16.359%), 48 pgs degraded, 34 pgs undersized

            16 daemons have recently crashed

 

  services:

    mon: 3 daemons, quorum node-10,node-11,node-12 (age 44m)

    mgr: node-10(active, since 2h)

    mds: cephfs:1 {0=node-12=up:active} 2 up:standby

    osd: 3 osds: 3 up (since 4m), 3 in (since 4m); 33 remapped pgs

    rgw: 1 daemon active (node-10)

 

  data:

    pools:   10 pools, 249 pgs

    objects: 5.04k objects, 18 GiB

    usage:   50 GiB used, 7.2 GiB / 57 GiB avail

    pgs:     6.024% pgs not active

             2473/15117 objects degraded (16.359%)

             194 active+clean

             19  active+recovery_wait+undersized+degraded+remapped

             14  active+recovery_wait+degraded

             14  undersized+degraded+remapped+backfill_wait+peered

             7   active+recovery_wait

             1   undersized+degraded+remapped+backfilling+peered

 

  io:

    client:   383 B/s rd, 0 B/s wr, 17 op/s rd, 0 op/s wr

    recovery: 68 MiB/s, 18 objects/s

 

[root@node-10 cluster]#

wx_doitroot
关注
专栏目录
Ceph入门到精通-ceph故障处理 - osd down处理
隔壁老瓦的专栏
04-27 1675
来看一下是哪两块登录对应机器确认下是哪块盘2.我们发现盘还在，首先尝试能否重启ceph-osd服务 ，这里已经拉起来了3.如果重启无望或者盘漂移，重新卸载安装3.1 看看日志 是不是有磁盘报错3.2.直接踢掉3.3.重新格式化再添加。
ceph osd down 分析处理
最新发布
Pro_jhf的博客
09-09 738
当 Ceph OSD 出现down状态时，可能由多种原因引起，包括硬件故障、网络问题、配置错误等。通过系统化的排查流程，结合日志分析和硬件检查，可以准确定位问题并采取合适的处理措施。处理完问题后，建议通过 Ceph 的监控工具持续监控 OSD 状态，确保集群的稳定性和高可用性。
ceph修复osd为down的情况
weixin_33737134的博客
05-02 1073
尝试一、直接重新激活所有osd 1、查看osd树 root@ceph01:~# ceph osd tree ID WEIGHT TYPE NAME UP/DOWN REWEIGHT PRIMARY-AFFINITY -1 0.29279 root default -2 0.14639 host c...
Ceph OSD Down
Tomstrong_369的专栏
03-15 2990
CEPH集群跑了一段时间后有几个OSD变成down的状态了,但是我用这个命令去activate也不行 ceph-deploy osd activate osd1:/dev/sdb2:/dev/sdb1 只能把osd从集群中移除，然后再重建了，这个过程必须在ceph重新把数据同步完成才可以做，保证down掉的数据在其他osd中恢复。 在集群中删除一个osd硬盘 #
【ceph故障排查】ceph集群添加了一个osd之后，该osd的状态始终为down
运维少年
09-10 5377
背景 ceph集群添加了一个osd之后，该osd的状态始终为down。 错误提示 状态查看如下 1、查看osd tree [root@node1 Asia]# ceph osd tree ID WEIGHT TYPE NAME UP/DOWN REWEIGHT PRIMARY-AFFINITY -1 0.05388 root default ...
Ceph：ceph修复osd为down的情况
那个那个
03-09 4682
ceph修复osd为down的情况 今天巡检发现ceph集群有一个osds Down了 通过dashboard 查看： ceph修复osd为down的情况： 点击查看详情 可以看到是哪个节点Osds Down 了 通过命令查看Osds状态 ①、查看集群状态： [root@ceph01 ~]# ceph -s cluster: id: 240a5732-02e5-11eb-8f5a-000c2945a4b1 health: HEALTH_WARN Deg
Ceph OSD为DOWN时修复
热门推荐
夜雨狂歌如梦
05-15 2万+
本文所使用Ceph版本为luminous(不同版本删除OSD基本操作相同），当出现Ceph OSD为down的情况时，可以通过以下方法解决（假设ceph-admin节点OSD.1 Down，该OSD对应磁盘为/dev/sdb）： 1.首先尝试能否重启ceph-osd服务 近期在维护ceph集群时，发现一些新的情况： （1）ceph osd down掉之后（这里假设osd.1 down），去到...
osd down
wangerzheng
06-12 291
ceph -s ceph osd tree | grep down ceph osd find 1 service ceph status ps -ef | grep "ceph-osd" | grep "\-i 1\b" mount | grep "ceph-1\b" lsblk | grep ceph "ceph-1\b" umount /dev/sda2 lsblk | gr...
CEPH 添加OSD操作
weixin_34348174的博客
09-14 405
[talen@ceph_admin ~]$ ceph-deploy osd prepare ceph_monitor:/osd [ceph_deploy.conf][DEBUG ] found configuration file at: /home/talen/.cephdeploy.conf [ceph_deploy.cli][INFO...
ceph(版本10.2.10)添加OSD的步骤
01-30
ceph(版本10.2.10),在现有集群中，新添加OSD的步骤。。
【ceph】ceph OSD状态及常用命令
小鱼菜鸟的博客
07-22 538
OSD进程的启动停止：https://blog.csdn.net/bandaoyu/article/details/119894927 1. OSD概念 OSD：Object Storage Device，主要负责响应客户端请求返回具体数据的守护进程，一般一个集群会有多个OSD，每一块盘都会对应一个OSD。 2. OSD 状态 [root@dat...
ceph osd pg 状态介绍
DoloresOOO的博客
06-25 1611
导读： 1.从零部署一个ceph集群 2.ceph block device与cephfs快速入门 3.ceph 对象存储快速入门 4.Ceph存储集群&配置 5.centos7 通过cephadm部署ceph octopus版本 6.ceph集群状态检查常用命令 OSD in/out 、up/down OSD状态应处于集群内(in)、集群外(out)，并且处于运行(up)或关闭(down)。如果OSD处于up，他可能位于集群中(可以读写数据)，也可能不在集群中。如果OSD原本在集群中但是最近被移除
ceph OSD状态及常用命令
Be_Nice的博客
05-26 1万+
1. OSD概念 OSD：Object Storage Device，主要负责响应客户端请求返回具体数据的守护进程，一般一个集群会有多个OSD，每一块盘都会对应一个OSD。 2. OSD 状态 [root@data1 ~]# ceph osd stat 4 osds: 3 up (since 23m), 3 in (since 13m); epoch: e345 OSD状态说明： a. 集群内（in） b. 集群外（out） c. 活着且在运行（up） d. 挂了且不再运行（down） .
ceph osd down
mixboot
08-27 444
# ceph --version ceph version 12.2.13 luminous (stable) ceph osd tree
ceph 添加osd 扩容
weixin_30318645的博客
07-17 697
注1：如果是在已有的osd节点加盘扩容 Step1: 登录到admin节点，切换到/root/ceph-deploy Step2: ceph-deploy disk list node-131 #查看新加节点为node-131的盘符信息 Step3: ceph-deploy disk zap node-131:sdb #格式化sdb盘 Step4: ceph-deploy ...
ceph手动添加osd
wuxingge的博客
08-09 3387
简单版ceph-disk： ceph-disk prepare /dev/sdb ceph-disk activate --mark-init systemd --mount /dev/sdb 详细 生成uuid uuidgen 4c0a02e2-e577-4778-b775-8b636926bb2d 创建OSD ceph osd create 4c0a02e2-e577-4778-b775-8b636926bb2d 创建OSD目录 mkdir -p /var/lib/ceph/osd/ceph-0
ceph集群osd down 故障处理
Rocky
06-03 2093
（1）查看集群状态，发现2个osd 状态为down [root@node140 /]# ceph -s cluster: id: 58a12719-a5ed-4f95-b312-6efd6e34e558 health: HEALTH_ERR noout flag(s) set 2 osds down 1 scrub errors Possible data damage: 1 pg
【个人记录】Ceph添加OSD
喵呜
10-13 513
【代码】【个人记录】Ceph添加OSD节点
ceph osd down了怎么解决
04-11
这个问题的意思是如何解决 "ceph osd down" 的问题。要解决这个问题，你需要先确定导致 "ceph osd down" 的原因，可能是硬件故障、网络问题等。一旦确定了问题的原因，就可以针对性地采取解决方法，比如更换硬件、调整网络设置等。此外，还可以通过ceph的监控工具来定位和解决问题。
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值