October 2019 - Dev - lists.ceph.io

Re: Leisure wear and sports wear inquire

by qiaocaidouping0

4 years, 6 months

1
0
0 0

Vstart error with option bluestore block path = {path to device}

by Yiming Zhang

Hi Sage, I have experienced an error when I tries to use vstart to create a cluster running on raw device. Here is my vstart command: sudo MON=1 OSD=1 MDS=0 ../src/vstart.sh -b -d -n -x -l -o 'bluestore block path = /dev/sda' -o 'bluestore fsck on mkfs = false' -o 'bluestore fsck on mount = false' -o 'bluestore fsck on umount = false' -o 'bluestore block db path = ' -o 'bluestore block wal path = ' -o 'bluestore block wal create = false' -o 'bluestore block db create = false' -o 'bluefs preextend wal files = true' And here is my error list: /users/ceph/build/bin/ceph-osd -i 0 -c /users/yzhan298/ceph/build/ceph.conf 7f34590d1d80 -1 Falling back to public interface 7f34590d1d80 -1 bdev(0x562ce4c72000 /users/yzhan298/ceph/build/dev/osd0/block) _lock flock failed on /users/yzhan298/ceph/build/dev/osd0/block 7f34590d1d80 -1 bdev(0x562ce4c72000 /users/yzhan298/ceph/build/dev/osd0/block) open failed to lock /users/yzhan298/ceph/build/dev/osd0/block: (11) Resource temporarily unavailable 7f34590d1d80 -1 osd.0 0 OSD:init: unable to mount object store 7f34590d1d80 -1 ** ERROR: osd init failed: (11) Resource temporarily unavailable I couldn’t find the reason for this error. Please help. Thanks, Yiming

4 years, 6 months

4
4
0 0

Past_interval start interval mismatch (last_clean_epoch reported)

by Huseyin Cotuk

Hi all, I also hit the bug #24866 in my test environment. According to the logs, the last_clean_epoch in the specified OSD/PG is 17703, but the interval starts with 17895. So the OSD fails to start. There are some other OSDs in the same status. 2019-10-14 18:22:51.908 7f0a275f1700 -1 osd.21 pg_epoch: 18432 pg[18.51( v 18388'4 lc 18386'3 (0'0,18388'4] local-lis/les=18430/18431 n=1 ec=295/295 lis/c 18430/17702 les/c/f 18431/17703/0 18428/18430/18421) [11,21]/[11,21,20] r=1 lpr=18431 pi=[17895,18430)/3 crt=18388'4 lcod 0'0 unknown m=1 mbc={}] 18.51 past_intervals [17895,18430) start interval does not contain the required bound [17703,18430) start The cause is pg 18.51 went clean in 17703 but 17895 is reported to the monitor. I am using the last stable version of Mimic (13.2.6). Any idea how to fix it? Is there any way to bypass this check or fix the reported epoch #? Thanks in advance. Best regards, Huseyin Cotuk hcotuk(a)gmail.com <mailto:hcotuk@gmail.com>

4 years, 6 months