public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Manish Aggarwal <mani.iitb@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: auto group failing on kernel v2.6.38.5
Date: Wed, 15 Jun 2011 10:03:25 -0500	[thread overview]
Message-ID: <4DF8C9BD.6020104@sandeen.net> (raw)
In-Reply-To: <BANLkTi=pgOCvn_2tdKXM6sLx_JKhzbrcEw@mail.gmail.com>

On 6/15/11 4:24 AM, Manish Aggarwal wrote:
> Hi I am running xfstest suite using command
> 
> ./check -xfs -g auto
> 
> PC x86 machine with Kernel version 2.6.38.5
> XFS Tests Suite dated 2011-05-11 (http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfstests.git;a=summary)
> 
> 
> Many of the test cases are failing , please let me know thatt am I missing something?

Most are failing with something like "+umount: /home/manish/Projects/xfstests/sdb4: device is busy."

You should investigate to find out why that might be the case ...

> +umount: /home/manish/Projects/xfstests/sdb4: device is busy.
> +        (In some cases useful info about processes that use
> +         the device is found by lsof(8) or fuser(1))

-Eric

> Regards,
> Manish
> 
> 
> FSTYP         -- xfs (non-debug)
> PLATFORM      -- Linux/i686 mannuDesk 2.6.38.5
> MKFS_OPTIONS  -- -f -bsize=4096 /dev/sda6
> MOUNT_OPTIONS -- /dev/sda6 /home/manish/Projects/xfstests/sdb4
> 
> 001 4s ... 5s
> 002 0s ... 0s
> 003 0s ... 0s
> 004 1s ... 1s
> 005 0s ... 0s
> 006 35s ... 36s
> 007 58s ... 58s
> 008 1s ... 1s
> 009 1s ... 1s
> 010     [not run] dbtest was not built for this platform
> 011 43s ... 45s
> 012 1s ... 2s
> 013 145s ... 158s
> 014 53s ... 51s
> 015 1s ... - output mismatch (see 015.out.bad)
> --- 015.out    2011-05-11 22:32:24.000000000 +0530
> +++ 015.out.bad    2011-06-15 14:34:36.561351828 +0530
> @@ -4,4 +4,8 @@
>  check free space:
>  delete fill:
>  check free space:
> -   !!! free space is in range
> +   !!! free space has value of 20
> +free space is NOT in range 43306.56 .. 44181.44
> +umount: /home/manish/Projects/xfstests/sdb4: device is busy.
> +        (In some cases useful info about processes that use
> +         the device is found by lsof(8) or fuser(1))

... snip

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2011-06-15 15:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15  9:24 auto group failing on kernel v2.6.38.5 Manish Aggarwal
2011-06-15 14:59 ` ***** SUSPECTED SPAM ***** " Dave Chinner
2011-06-15 15:03 ` Eric Sandeen [this message]
     [not found]   ` <BANLkTimmEHrxONk-bm354sPnnLyc-0eQ-w@mail.gmail.com>
2011-06-16 14:46     ` Eric Sandeen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DF8C9BD.6020104@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=mani.iitb@gmail.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox