Project

General

Profile

Actions

Bug #11075

closed

librbd: fsx failure - read zeroes when data was expected

Added by Josh Durgin about 9 years ago. Updated about 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

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

Description

fsx command was:

ceph_test_librbd_fsx -d -W -R -p 100 -r 1 -w 1 -t 1 -h 1 -l 250000000 -S 773 -N 100000 rbd foo4
6412 trunc      from 0xc5b5895 to 0x19cb031
6413 clone      63 order 20 su 524288 sc 10
truncating image foo4-clone62 from 0x19cb031 (overlap 0x19cb031) to 0x5289a3
checking clone #61, image foo4-clone61 against file ./fsx-foo4-parent62
READ BAD DATA: offset = 0x0, size = 0x1c6c38, fname = foo4
OFFSET  GOOD    BAD     RANGE
0x48000 0x3fc8  0x0000  0x    0
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x48001 0xc83f  0x0000  0x    1
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x48002 0x3f36  0x0000  0x    2
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x48003 0x363f  0x0000  0x    3
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x48004 0x3f95  0x0000  0x    4
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x48005 0x953f  0x0000  0x    5
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x48006 0x3fc3  0x0000  0x    6
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x48007 0xc33f  0x0000  0x    7
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x48008 0x3f63  0x0000  0x    8
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x48009 0x633f  0x0000  0x    9
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x4800a 0x3f45  0x0000  0x    a
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x4800b 0x453f  0x0000  0x    b
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x4800c 0x3f02  0x0000  0x    c
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x4800d 0x023f  0x0000  0x    d
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x4800e 0x3fb9  0x0000  0x    e
...

Full client logs with debug rbd = 20, debug ms = 1 will be attached


Files

fsx.log (273 KB) fsx.log fsx output Josh Durgin, 03/09/2015 09:40 PM
Actions #2

Updated by Josh Durgin about 9 years ago

  • Status changed from New to In Progress
  • Assignee set to Josh Durgin
Actions #3

Updated by Josh Durgin about 9 years ago

  • Priority changed from Urgent to Normal

does not affect hammer or master, just present when other cleanups are there

Actions #4

Updated by Josh Durgin about 9 years ago

  • Status changed from In Progress to Rejected

the branch that caused this isn't worth merging

Actions

Also available in: Atom PDF