Project

General

Profile

Bug #2750

1.14 scrub stat mismatch, got 4/4 objects, 0/0 clones, 8138/7467 bytes." in cluster

Added by Samuel Just over 11 years ago. Updated over 11 years ago.

Status:
Won't Fix
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

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

Description

lavor: basic
owner: scheduled_sage@metropolis
success: false
ubuntu@teuthology:/a/sage-2012-07-06_11:03:15-regression-master-testing-basic/6883$ ls
ceph-sha1 config.yaml owner pid remote summary.yaml teuthology.log
ubuntu@teuthology:/a/sage-2012-07-06_11:03:15-regression-master-testing-basic/6883$ cat config.yaml
kernel: &id001
kdb: true
sha1: 5a73ba3314ee1ac094ab1cb19b91c7e876861606
nuke-on-error: true
overrides:
ceph:
fs: btrfs
log-whitelist:
- slow request
sha1: 668ce00a559b1a7512ed4539e706e4e2dc4c7c28
roles:
- - mon.a
- mon.c
- osd.0
- osd.1
- osd.2
- - mon.b
- mds.a
- osd.3
- osd.4
- osd.5
- - client.0
targets:
: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDE4lTHELBl2d+BXuaxMKtJX4r3GN2qSaxHTfewZxutqEC+rSNbD5Otiqwm16GtmCYklbYJL0yr6mizCZ0KzL3lVwNSczb/CxfvLTLegmBv9YzPRvoL1ymxdHggPIw47JTNRg6+UO9EConQpp7LOktT7fYf3AFx/BS9Ux6UeKyxifkb/1GUlzVT2rk1D39frBhI7AcPHovvbd/6uHvamrpUS3wSDWdz6BNRTQDaK307TJS9LPva6Cj6WAgmTZZesjWB4mOpWywrA9sva7GqSrnTMGKnIHPcsI6U57CALwHS1g/zIz73QuolZA2NkbhA7jjrfsUaWYJorE9dynIga9pf
: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCuvUzb6iEIx1l/b1TF9O/aQ6XFUW/Fn4mri84Q7QfyMBc1NLDkFBBPBfvXv44bYooG1E5VBXTawmVgOtANyGArqXVNYmHxbIoAkKibn2eIUDb2UzrQHsSWK/aqeEPe7AdcBC2FM07hw1DxEQvept1Ou1kLFMumMY11W2HQ7xnMI8v3VJ+MVgxfp2GdFeNfmDCjFLF19s1mKYjbqlEhNJQ8kg1oHOHsTPn5PLeYntgtRfJzOgOOUyG3Vnw8XtOPBOg9BG248jzdqZQxsHC9ZR1TM8xbq88Uz2JU5XKng6pf6mtL82opCZBYsqBIKkbyCLRKtErkQ/LB3o81kme0P+Dz
: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDAZtaJPPhGrqcL1tRUHvgMMykh4hU2IdrX9cC2hYhotYVpzeejuA2TkmRdFhno54E6BM4dRIh3Wqv95YXpsToxOvzGp46lmRl3aNrLeWEEE5KxwgwTWuK72vMpZTuD/8XClj/faeFYuKvdiFFK0jGiX+j74HBOOrl3A3WdCi+/xFJZ/b5vZUJRFZxEkAkpy868iebiMgMHWDzs9A8GVb35MGf8nQGwFtPQlHEtgQNK51Wm7rj3qJM1tP1ZL2ghtrck9mdLBUzo6Fj1YTifewKt/PhteEZ1aP8lMpakOoRrJWawM27XQ7XJZDldZcI4REvF3suJLbiQHzdGArUTG3oz
tasks:
- internal.lock_machines: 3
- internal.save_config: null
- internal.check_lock: null
- internal.connect: null
- internal.check_conflict: null
- kernel: *id001
- internal.base: null
- internal.archive: null
- internal.coredump: null
- internal.syslog: null
- internal.timer: null
- chef: null
- clock: null
- ceph: null
- kclient: null
- workunit:
clients:
all:
- suites/pjd.sh

History

#1 Updated by Samuel Just over 11 years ago

Ok, so this is actually caused by not updating the backfill peer's partial stats while recovering the backfill portion from the log. There isn't really a natural way of recovering that information, unfortunately. One option would be extending push to do the relevant updates. Another would be annotating the log updates with the stat diffs. However, since this only affects the accuracy of the degraded object counts during backfill, I'm going to simply remove the loud warnings for now.

#2 Updated by Greg Farnum over 11 years ago

Remove the loud warnings? Like, the mismatch warnings?

#3 Updated by Samuel Just over 11 years ago

  • Status changed from New to Won't Fix

67a5e75ed6a9b3689a984d6f7eb6a18e1242125e

Also available in: Atom PDF