From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] 56cbb429d9: ltp.fs_fill.fail
Date: Thu, 25 Jul 2019 15:26:27 +0200 [thread overview]
Message-ID: <20190725132617.GA23135@rei.lan> (raw)
In-Reply-To: <20190725110944.GA22106@shao2-debian>
Hi!
> tst_test.c:1161: INFO: Testing on vfat
> tst_mkfs.c:90: INFO: Formatting /dev/loop0 with vfat opts='' extra opts=''
> mkfs.vfat: unable to open /dev/loop0: Device or resource busy
> tst_mkfs.c:101: BROK: mkfs.vfat:1: tst_test.c failed with 741
This looks like mkfs.vfat got EBUSY after the loop device was
succesfully umounted.
We do run the test in a loop for several filesystems and the loop
generally does:
next:
mkfs
mount
test
umount
goto next;
--
Cyril Hrubis
chrubis@suse.cz
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: lkp@lists.01.org
Subject: Re: [LTP] 56cbb429d9: ltp.fs_fill.fail
Date: Thu, 25 Jul 2019 15:26:27 +0200 [thread overview]
Message-ID: <20190725132617.GA23135@rei.lan> (raw)
In-Reply-To: <20190725110944.GA22106@shao2-debian>
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
Hi!
> tst_test.c:1161: INFO: Testing on vfat
> tst_mkfs.c:90: INFO: Formatting /dev/loop0 with vfat opts='' extra opts=''
> mkfs.vfat: unable to open /dev/loop0: Device or resource busy
> tst_mkfs.c:101: BROK: mkfs.vfat:1: tst_test.c failed with 741
This looks like mkfs.vfat got EBUSY after the loop device was
succesfully umounted.
We do run the test in a loop for several filesystems and the loop
generally does:
next:
mkfs
mount
test
umount
goto next;
--
Cyril Hrubis
chrubis(a)suse.cz
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
lkp@01.org, Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
ltp@lists.linux.it
Subject: Re: [LTP] 56cbb429d9: ltp.fs_fill.fail
Date: Thu, 25 Jul 2019 15:26:27 +0200 [thread overview]
Message-ID: <20190725132617.GA23135@rei.lan> (raw)
In-Reply-To: <20190725110944.GA22106@shao2-debian>
Hi!
> tst_test.c:1161: INFO: Testing on vfat
> tst_mkfs.c:90: INFO: Formatting /dev/loop0 with vfat opts='' extra opts=''
> mkfs.vfat: unable to open /dev/loop0: Device or resource busy
> tst_mkfs.c:101: BROK: mkfs.vfat:1: tst_test.c failed with 741
This looks like mkfs.vfat got EBUSY after the loop device was
succesfully umounted.
We do run the test in a loop for several filesystems and the loop
generally does:
next:
mkfs
mount
test
umount
goto next;
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-07-25 13:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 11:09 [LTP] 56cbb429d9: ltp.fs_fill.fail kernel test robot
2019-07-25 11:09 ` kernel test robot
2019-07-25 11:09 ` kernel test robot
2019-07-25 13:26 ` Cyril Hrubis [this message]
2019-07-25 13:26 ` [LTP] " Cyril Hrubis
2019-07-25 13:26 ` Cyril Hrubis
2019-07-25 16:32 ` Linus Torvalds
2019-07-25 16:32 ` Linus Torvalds
2019-07-25 16:32 ` Linus Torvalds
2019-07-25 18:04 ` Al Viro
2019-07-25 18:04 ` Al Viro
2019-07-25 18:04 ` Al Viro
2019-07-26 0:00 ` Al Viro
2019-07-26 0:00 ` Al Viro
2019-07-26 0:00 ` Al Viro
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=20190725132617.GA23135@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.