Project

General

Profile

Bug #3975

librbd: xfstests 008 failed inside qemu

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

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

0%

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

Description

From xfstests output in ubuntu@teuthology:/a/teuthology-2013-01-29_20:00:/qemu/client.0/test.log:

meta-data=/dev/vdb               isize=256    agcount=4, agsize=655360 blks
         =                       sectsz=512   attr=2, projid32bit=0
data     =                       bsize=4096   blocks=2621440, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=8 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
meta-data=/dev/vdc               isize=256    agcount=4, agsize=655360 blks
         =                       sectsz=512   attr=2, projid32bit=0
data     =                       bsize=4096   blocks=2621440, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=8 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
/var/lib/xfstests /
FSTYP         -- xfs (non-debug)
PLATFORM      -- Linux/x86_64 test 3.2.0-32-virtual
MKFS_OPTIONS  -- -f -l su=32k /dev/vdc
MOUNT_OPTIONS -- /dev/vdc /tmp/cephtest/scratch_mnt.VmtHV7raTe

001      3s
002      0s
003      0s
004      6s
005      0s
006      2s
007      1s
008      - output mismatch (see 008.out.bad)
--- 008.out     2013-01-31 01:34:11.128439057 +0000
+++ 008.out.bad 2013-01-31 01:35:00.648439057 +0000
@@ -2,7 +2,8 @@

 randholes.1 : -l FSIZE -c 50 -b PGSIZE
 ------------------------------------------
-holes is in range
+holes has value of 42
+holes is NOT in range 45. .. 55.

 randholes.2 : -l FSIZE -c 100 -b PGSIZE
 ------------------------------------------
@@ -14,7 +15,8 @@

 randholes.4 : -d -l FSIZE -c 50 -b PGSIZE
 ------------------------------------------
-holes is in range
+holes has value of 43
+holes is NOT in range 45. .. 55.

 randholes.5 : -d -l FSIZE -c 100 -b PGSIZE
 ------------------------------------------

This was the task:

kernel:
  kdb: true
  sha1: 0fa6ebc600bc8e830551aee47a0e929e818a1868
nuke-on-error: true
overrides:
  ceph:
    conf:
      global:
        ms inject socket failures: 5000
    fs: btrfs
    log-whitelist:
    - slow request
    sha1: 5a7c5088cc8f57f75eb594a21bf5fb6661e50978
  s3tests:
    branch: bobtail
  workunit:
    sha1: 5a7c5088cc8f57f75eb594a21bf5fb6661e50978
roles:
- - mon.a
  - mon.c
  - osd.0
  - osd.1
  - osd.2
- - mon.b
  - mds.a
  - osd.3
  - osd.4
  - osd.5
- - client.0
task:
- ceph:
    conf:
      client:
        rbd cache: true
        rbd cache max dirty: 0
tasks:
- chef: null
- clock: null
- ceph: null
- qemu:
    all:
      num_rbd: 2
      test: https://raw.github.com/ceph/ceph/master/qa/run_xfstests_qemu.sh
      type: block

History

#1 Updated by Alex Elder about 11 years ago

  • Status changed from New to Rejected

This one's not a problem. This test pokes random holes in a
file (or maybe fills random spots). And when done it should
have around 50 holes. If it's outside the range of 45-55 it
reports an error. Something close to that is fine, though.

Also available in: Atom PDF