linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Ext4 Mailing List <linux-ext4@vger.kernel.org>,
	Linux FS Maling List <linux-fsdevel@vger.kernel.org>,
	Linux Kernel Maling List <linux-kernel@vger.kernel.org>
Subject: Re: ext4 blocks up
Date: Mon, 02 Jul 2012 17:54:22 +0300	[thread overview]
Message-ID: <1341240862.2979.23.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20120702144444.GA18074@thunk.org>

[-- Attachment #1: Type: text/plain, Size: 1968 bytes --]

On Mon, 2012-07-02 at 10:44 -0400, Theodore Ts'o wrote:
> Can you tell me *which* xfstest this was blocking on?

Test 068 which runs fsstress.

$ ps axjf
  828   830   828   828 ?           -1 S      500   0:00  |   \_ sshd: dedekind@pts/0
  830   831   831   831 pts/0      972 Ss     500   0:00  |       \_ -bash
  831   972   972   831 pts/0      972 S+       0   0:00  |           \_ sudo env PATH=/home/dedekind/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin ./test-ext4.sh elog
  972   973   972   831 pts/0      972 S+       0   0:00  |               \_ /bin/sh -euf ./test-ext4.sh elog
  973   997   972   831 pts/0      972 S+       0   0:00  |                   \_ /bin/bash ./check -g auto
  997 14830   972   831 pts/0      972 S+       0   0:00  |                       \_ /bin/bash ./068
14830 15000   972   831 pts/0      972 S+       0   0:00  |                           \_ /bin/bash ./068
15000 15153 15153   831 pts/0      972 S        0   0:00  |                           |   \_ /home/dedekind/git/xfstests/ltp/fsstress -d /mnt/xfstests-disk-2/fsstress_test_dir -p 2 -n 200
15153 15154 15153   831 pts/0      972 D        0   0:00  |                           |       \_ /home/dedekind/git/xfstests/ltp/fsstress -d /mnt/xfstests-disk-2/fsstress_test_dir -p 2 -n 200
15153 15155 15153   831 pts/0      972 D        0   0:00  |                           |       \_ /home/dedekind/git/xfstests/ltp/fsstress -d /mnt/xfstests-disk-2/fsstress_test_dir -p 2 -n 200
14830 15170   972   831 pts/0      972 S+       0   0:00  |                           \_ /bin/sh -f /usr/sbin/xfs_freeze -u /mnt/xfstests-disk-2
15170 15174   972   831 pts/0      972 D+       0   0:00  |                           |   \_ /usr/sbin/xfs_io -F -r -p xfs_freeze -x -c thaw /mnt/xfstests-disk-2
14830 15171   972   831 pts/0      972 S+       0   0:00  |                           \_ tee -a 068.full

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-07-02 14:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02 12:15 ext4 blocks up Artem Bityutskiy
2012-07-02 14:44 ` Theodore Ts'o
2012-07-02 14:54   ` Artem Bityutskiy [this message]
2012-07-02 15:14     ` Theodore Ts'o
2012-07-02 16:45       ` Theodore Ts'o
2012-07-02 16:54         ` Eric Sandeen
2012-07-02 17:31           ` Jan Kara
2012-07-02 17:43             ` Theodore Ts'o
2012-07-02 17:53               ` Jan Kara
2012-07-02 18:14                 ` Theodore Ts'o
2012-07-02 16:55         ` Artem Bityutskiy
2012-07-02 16:54       ` Artem Bityutskiy

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=1341240862.2979.23.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).