From: Zdenek Kabelac <zkabelac@redhat.com>
To: Heming Zhao <heming.zhao@suse.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] It looks wrong for the timeout when lvm test running
Date: Mon, 9 Dec 2019 12:36:49 +0100 [thread overview]
Message-ID: <47ab183b-3a61-24f1-77e8-1d3aa2cf3c29@redhat.com> (raw)
In-Reply-To: <efb74841-6424-aa2d-0067-019b31240bd8@suse.com>
Dne 09. 12. 19 v 11:58 Heming Zhao napsal(a):
> Hello Zdenek,
>
> Please check the compressed file in attachment.
>
>>
> On 12/9/19 5:40 PM, Zdenek Kabelac wrote:
>> Dne 09. 12. 19 v 10:20 Heming Zhao napsal(a):
>>> Hello List,
>>>
>>> The lvm test default timeout (--timeout) default value is 180.
>>> But I met below condition when running testcase (in virtual machine):
>>> ```
>>> make check_local T=shell/snapshot-merge.sh
>>> ���� ... ...
>>> ###������ passed: [ndev-vanilla] shell/snapshot-merge.sh 665
>>> ���� ... ...
>>> ```
Hi
So your test seems to be very slow in 'mkfs.ext4':
[ 0:03] Creating journal (4096 blocks): done
[ 1:30] Writing superblocks and filesystem accounting information: done
....
[ 1:34] Creating journal (4096 blocks): done
[ 3:03] Writing superblocks and filesystem accounting information: done
....
[ 3:07] Creating journal (4096 blocks): done
[ 4:37] Writing superblocks and filesystem accounting information: done
....
[ 4:40] Creating journal (4096 blocks): done
[ 6:08] Writing superblocks and filesystem accounting information: done
....
This looks certainly seriously like a very slow (possibly doing TRIM) ??
Any idea why ?
The test seems to be using loop device created in backend file in your /tmp
(i.e.: losetup /dev/loop0 /tmp/LVMTEST11574.cJtNfnlPrj/test.img)
So any idea why your virtual machine is that slow with handling this case ?
One idea - aren't you using a storage with very slow discard processing
(i.e. ATM VDO) ?
You can setup different backend device or different location of test dir
(see 'make help' in test subdir)
Regards
Zdenek
next prev parent reply other threads:[~2019-12-09 11:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 9:20 [linux-lvm] It looks wrong for the timeout when lvm test running Heming Zhao
2019-12-09 9:40 ` Zdenek Kabelac
2019-12-09 10:58 ` Heming Zhao
2019-12-09 11:36 ` Zdenek Kabelac [this message]
2019-12-10 3:23 ` Heming Zhao
2019-12-10 9:03 ` Zdenek Kabelac
2019-12-10 9:11 ` Heming Zhao
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=47ab183b-3a61-24f1-77e8-1d3aa2cf3c29@redhat.com \
--to=zkabelac@redhat.com \
--cc=heming.zhao@suse.com \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).