Personal tools
You are here: Home Issue tracker [zfs-fuse] assertion with runtest

#38 — [zfs-fuse] assertion with runtest

State Resolved
Version:
Area Functionality
Issue type Bug
Severity Low
Submitted by Laurent PETITJEAN
Submitted on May 05, 2010
Responsible Seth Heeren
Target release:
Return to tracker
Last modified on May 06, 2010 by Seth Heeren
I'm just installed the version from the repository
git clone http://git.zfs-fuse.net/official -o testing
and this test has crashed a the seventh test.

Software configuration
OS=Linux
distribution=CentOS-5.2
Steps to reproduce:
On a fresh CentOS 5.2 box, issue (as root)

yum install -y fuse-devel libattr-devel libaio-devel libacl-devel zlib-devel fuse-devel scons openssl-devel git-core

#optionally required, depending on repositories referenced (?)
wget -c 'http://downloads.sourceforg[…]noarch.rpm?use_mirror=ignum'
wget -c http://www.kernel.org/pub/software/scm/git/git-1.7.1.tar.gz

yum install curl-devel
tar xf git-1.7.1.tar.gz
(cd git-1.7.1 && ./configure && make install)
rpm -i scons-1.3.0-1.noarch.rpm

git clone http://git.zfs-fuse.net/official -b testing
cd official/src
scons -c
killall zfs-fuse
scons -j4 debug=2 install
cd ./cmd/ztest

# replace /mnt with a suitable location for vdev files
sh runtest.sh -v 25 -s 2048M -d 21 -T 300 -f /mnt



Attached:
zfs-test-failed.txt — Plain Text, 0Kb
Added by (anonymous) on May 05, 2010 12:02 PM
i'll try to have a look later.

in the meantime, please confirm the branch you were on (the -o option is unknown to me)

you might help us with 'git log -1' output
Added by Seth Heeren on May 05, 2010 05:42 PM
Severity: MediumLow
Responsible manager: (UNASSIGNED)sgheeren
I have tested on two cloud machines (since I don't run redhat)

You failed to mention 32 bit or 64 bit so I tested both.

No problems with debug=0 builds (which is the standard).

Attached are the outputs.
Attached:
output-i686.txt — Plain Text, 1Kb
Added by Seth Heeren on May 05, 2010 05:43 PM
And 64bit (attached)
Attached:
output-amd64.txt — Plain Text, 1Kb
Added by Seth Heeren on May 05, 2010 06:06 PM
I cannot reproduce this.

I have tested debug=2 builds as well, running for 300 seconds and with much larger specs in general. I have updated the original issue with /my/ steps to /not/ reproduce... I fear something may be wrong with your particular setup (mainly, any existing pools).

Did you remember to stop/kill any running zfs-fuse before launching the freshly-built zfs-fuse and ztest?

For completeness, I attach the output of the debug test runs
Attached:
output-i686-debug.txt — Plain Text, 1Kb
Added by Seth Heeren on May 05, 2010 06:07 PM
And 64bit again
Attached:
output-amd64-debug.txt — Plain Text, 1Kb
Added by (anonymous) on May 06, 2010 04:05 AM
I've obtained a clone of the repository with the option '-o' because the option '-b' is not available for git application under Ubuntu
Added by (anonymous) on May 06, 2010 04:08 AM
I confirm under CentOS-5.2 that when the zfs-fuse process is stopped, there isn't assertion() and the test runs.
Added by (anonymous) on May 06, 2010 04:13 AM
The following command 'git log -1' returns
commit b79138c93d33261003512c33c0a849668d9a9169
Author: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
Date: Fri Mar 12 23:52:57 2010 -0800

    Packaging fixes
Added by (anonymous) on May 06, 2010 04:33 AM
git clone -o is not equivalent

you are not on the right branch

you need to switch the branch

/tmp/official$ git checkout testing/testing
Note: moving to 'testing/testing' which isn't a local branch
If you want to create a new branch from this checkout, you may do so
(now or later) by using -b with the checkout command again. Example:
  git checkout -b <new_branch_name>
HEAD is now at 12d41f2... 0.6.9_beta

Be sure to stop zfs-fuse before relaunching ztest

Cheers
Added by Seth Heeren on May 06, 2010 04:36 AM
Issue state: unconfirmedresolved
closing