Project

General

Profile

Bug #1848

osd got zeroed out fsid

Added by Josh Durgin almost 12 years ago. Updated almost 12 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
v0.40
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

From teuthology:~/log/osd.0.log.gz:

2011-12-20 04:13:17.830524 7f2c418f7780 journal _open /tmp/cephtest/data/osd.0.journal fd 14: 104857600 bytes, block size 4096 bytes, directio = 1
2011-12-20 04:13:17.830567 7f2c418f7780 journal read_entry 4096 : seq 1 229 bytes
2011-12-20 04:13:17.830595 7f2c418f7780 journal _open /tmp/cephtest/data/osd.0.journal fd 14: 104857600 bytes, block size 4096 bytes, directio = 1
2011-12-20 04:13:31.304178 7f2c35846700 osd.0 0 handle_osd_map fsid 94992fd9-2df9-4453-a1d6-499f16c62161 != 00000000-0000-0000-0000-000000000000

Not sure if this is a problem with teuthology or the OSD, but it seems possibly related to wip-osd-fsid that was merged yesterday.

Associated revisions

Revision 05cc4eb9 (diff)
Added by Sage Weil almost 12 years ago

monc: get latest monmap during authentication

Tell the monitor which monmap version we have in our initial auth message.
Make the monitor send the latest monmap if it has something newer. This
ensures that once authentication completes the monclient has the latest
monmap and a valid fsid.

Fixes: #1848
Signed-off-by: Sage Weil <>

History

#1 Updated by Josh Durgin almost 12 years ago

Happened again in teuthology:~/log/osd.1.log.gz and teuthology:~/log/osd.0.log.gz, with a similar error in monitor logs:

2011-12-28 13:40:08.284602 7fa8e6727700 mon.0@0(leader).pg v3 handle_statfs on fsid 00000000-0000-0000-0000-000000000000 != c1bad416-6892-4a8b-9ecd-c5c7720ec087

2011-12-28 13:44:25.454028 7f884ebea700 mon.0@0(leader).pg v2 handle_statfs on fsid 00000000-0000-0000-0000-000000000000 != a511a590-f4d6-4360-a5ad-8733632b6d11
2011-12-28 13:44:26.445296 7f884ebea700 mon.0@0(leader).osd e2 e2: 1 osds: 1 up, 1 in
2011-12-28 13:44:26.571627 7f884ebea700 log [INF] : osd.1 10.3.14.190:6800/17296 boot
2011-12-28 13:44:28.919427 7f884ebea700 mon.0@0(leader).osd e3 e3: 1 osds: 1 up, 1 in
2011-12-28 13:44:30.988943 7f884ebea700 mon.0@0(leader) e1 handle_command mon_command(mds set_max_mds 1 v 0) v1
2011-12-28 13:44:32.817475 7f884ebea700 mon.0@0(leader).mds e3 adding standby 10.3.14.133:6803/24958 as mds.0
2011-12-28 13:44:33.317557 7f884ebea700 log [INF] : mds.? 10.3.14.133:6803/24958 up:boot
2011-12-28 13:44:33.359474 7f884ebea700 mon.0@0(leader).osd e4 e4: 2 osds: 2 up, 2 in
2011-12-28 13:44:33.510493 7f884ebea700 log [INF] : osd.0 10.3.14.133:6800/24952 boot
2011-12-28 13:44:33.812671 7f884ebea700 mon.0@0(leader).pg v5 handle_statfs on fsid 00000000-0000-0000-0000-000000000000 != a511a590-f4d6-4360-a5ad-8733632b6d11

#3 Updated by Sage Weil almost 12 years ago

  • Status changed from New to Resolved

Also available in: Atom PDF