From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH] btrfs-porgs: fix xfstest btrfs/023 random failure
Date: Thu, 17 Jul 2014 17:28:24 +0800 [thread overview]
Message-ID: <1405589304-7174-1-git-send-email-anand.jain@oracle.com> (raw)
xfstest btrfs/023 which does the following tests
create_group_profile "raid0"
check_group_profile "RAID0"
create_group_profile "raid1"
check_group_profile "RAID1"
create_group_profile "raid10"
check_group_profile "RAID10"
create_group_profile "raid5"
check_group_profile "RAID5"
create_group_profile "raid6"
check_group_profile "RAID6"
fails randomly with the error as below
ERROR: device scan failed '/dev/sde' - Invalid argument
since failure is at random group profile it indicates to me that
btrfs kernel did not see the newly created btrfs on the device
To note: I have the following patch on the kernel which
is not yet integrated, but its not related to this bug.
btrfs: RFC: code optimize use btrfs_get_bdev_and_sb() at btrfs_scan_one_device
btrfs: looping 'mkfs.btrfs -f <dev>' may fail with EBUSY
btrfs: check generation as replace duplicates devid+uuid
This patch calls fsync() at btrfs_prepare_device().
With this btrfs/023 has NOT failed consistently for several long
iterations.
Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
utils.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/utils.c b/utils.c
index fbc5bde..e144dfd 100644
--- a/utils.c
+++ b/utils.c
@@ -741,6 +741,8 @@ int btrfs_prepare_device(int fd, char *file, int zero_end, u64 *block_count_ret,
}
*block_count_ret = block_count;
+ fsync(fd);
+
zero_dev_error:
if (ret < 0) {
fprintf(stderr, "ERROR: failed to zero device '%s' - %s\n",
--
2.0.0.153.g79dcccc
next reply other threads:[~2014-07-17 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 9:28 Anand Jain [this message]
2014-07-29 12:57 ` [PATCH] btrfs-porgs: fix xfstest btrfs/023 random failure David Sterba
2014-07-31 7:07 ` Anand Jain
2014-07-31 12:01 ` David Sterba
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=1405589304-7174-1-git-send-email-anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
/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).