Bug #2522
closed
Added by Sage Weil almost 12 years ago.
Updated over 10 years ago.
Description
2012-06-05T18:43:48.505 INFO:teuthology.orchestra.run.out:219 - output mismatch (see 219.out.bad)
2012-06-05T18:43:48.509 INFO:teuthology.orchestra.run.out:--- 219.out 2012-06-05 17:54:42.023801052 -0700
2012-06-05T18:43:48.509 INFO:teuthology.orchestra.run.out:+++ 219.out.bad 2012-06-05 18:43:48.505881687 -0700
2012-06-05T18:43:48.509 INFO:teuthology.orchestra.run.out:@@ -46,4 +46,6 @@
2012-06-05T18:43:48.509 INFO:teuthology.orchestra.run.out: File: "SCRATCH_MNT/mmap"
2012-06-05T18:43:48.510 INFO:teuthology.orchestra.run.out: Size: 49152 Filetype: Regular File
2012-06-05T18:43:48.510 INFO:teuthology.orchestra.run.out: Mode: (0644/-rw-r--r--) Uid: (1) Gid: (2)
2012-06-05T18:43:48.510 INFO:teuthology.orchestra.run.out:-Usage OK (type=g)
2012-06-05T18:43:48.510 INFO:teuthology.orchestra.run.out:+./219: line 66: [: : integer expression expected
2012-06-05T18:43:48.510 INFO:teuthology.orchestra.run.out:+./219: line 69: [: : integer expression expected
2012-06-05T18:43:48.510 INFO:teuthology.orchestra.run.out:+Bad number of inodes used (type=g)
2012-06-05T18:43:55.733 INFO:teuthology.orchestra.run.out:220 5s
ubuntu@teuthology:/a/nightly_coverage_2012-06-05-a
seen this before,too..
ubuntu@teuthology:/a/nightly_coverage_2012-06-05-b
- Priority changed from Normal to High
- Priority changed from High to Urgent
The problem here appears to be that the output of the repquota
command is not what's expected. I think the group quota info
is not what it should be--meaning it is not reporting the number
of blocks and/or inodes used that the test expects at a particular
point.
Without investing some more time (hours, probably a day or more)
I can't really say why this is occurring. It could be related to
updated OS environments (from oneiric to precise). It could also
be related to updates to XFS, or the quota system, or the xfstests.
I do expect it should pass, though I don't think this trouble is
related to something wrong with RBD.
The absolute easiest way to "fix" this is to remove 219 from the
set of tests run. And I'm OK with that, but it's headed in the
wrong direction.
We need a task to try to push it the other way, enabling tests
that have been found in the past to fail after understanding why
and fixing it.
- Priority changed from Urgent to Low
Sigh.. took a quick look and it's non-obvious why the repquota output doesn't match. Disabling this for now, but leaving this open as a low priority item so we don't forget about it.
My target system shows this for repquota version:
ubuntu@plana49:~$ repquota --version
Quota utilities version 4.00.
Compiled with: USE_LDAP_MAIL_LOOKUP EXT2_DIRECT HOSTS_ACCESS ALT_FORMAT RPC RPCR
Bugs to jack@suse.cz
ubuntu@plana49:~$
Dave Chinner says that he doesn't see the problem with
quota utilities version 4.01. So upgrading the quota
package may be enough to make this problem go away.
- Project changed from Linux kernel client to rbd
- Status changed from 12 to Closed
Also available in: Atom
PDF