qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Eric Blake <eblake@redhat.com>,
	Qemu-block <qemu-block@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
	Nir Soffer <nirsof@gmail.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] Failing QEMU iotest 175
Date: Sat, 4 May 2019 08:51:17 +0200	[thread overview]
Message-ID: <22933e94-18da-257c-7931-da511bc5a602@redhat.com> (raw)
In-Reply-To: <67a38513-89af-7f54-2fc8-05b5777983ca@redhat.com>

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

On 03/05/2019 22.21, Eric Blake wrote:
> On 5/2/19 11:37 PM, Thomas Huth wrote:
>> On 02/05/2019 23.56, Eric Blake wrote:
>>> On 4/28/19 10:18 AM, Thomas Huth wrote:
>>>> QEMU iotest 175 is failing for me when I run it with -raw:
>>>>
>>>>  == creating image with default preallocation ==
>>>>  Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=1048576
>>>> -size=1048576, blocks=0
>>>> +size=1048576, blocks=2
>>>
>>> What filesystem?
>>
>> ext4
> 
> Hmm, it's passing for me on ext4, but that probably means we have
> different configuration parameters. I'm not sure how to easily show what
> parameters a particular ext4 partition uses to compare the differences
> between your setup and mine (mine is tuned to whatever defaults Fedora's
> installer chose on my behalf), so maybe someone else can chime in.

$ sudo tune2fs -l /dev/mapper/Home
tune2fs 1.42.9 (28-Dec-2013)
Filesystem volume name:   <none>
Last mounted on:          /home
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr dir_index filetype
needs_recovery meta_bg extent 64bit flex_bg sparse_super large_file
huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              36700160
Block count:              146800640
Reserved block count:     5873663
Free blocks:              56266267
Free inodes:              35403275
First block:              1
Block size:               1024
Fragment size:            1024
Group descriptor size:    64
Blocks per group:         8192
Fragments per group:      8192
Inodes per group:         2048
Inode blocks per group:   256
First meta block group:   258
Flex block group size:    16
Filesystem created:       Thu Apr 19 18:34:33 2018
Last mount time:          Sat May  4 08:20:36 2019
Last write time:          Sat May  4 08:20:36 2019
Mount count:              224
Maximum mount count:      -1
Last checked:             Thu Apr 19 18:34:33 2018
Check interval:           0 (<none>)
Lifetime writes:          1826 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          128
Journal inode:            8
First orphan inode:       11076944
Default directory hash:   half_md4
Directory Hash Seed:      08e1be04-c3a3-4c37-a059-cf54af5c4bc0
Journal backup:           inode blocks

IIRC I talked to stefanha on IRC about this some weeks ago already, and
he was able to reproduce the problem when using a certain parameter to
create the file system. However, I fail to remember which parameter it
was. Maybe Stefan still remembers...

 Thomas


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Huth <thuth@redhat.com>
To: Eric Blake <eblake@redhat.com>,
	Qemu-block <qemu-block@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Nir Soffer <nirsof@gmail.com>, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] Failing QEMU iotest 175
Date: Sat, 4 May 2019 08:51:17 +0200	[thread overview]
Message-ID: <22933e94-18da-257c-7931-da511bc5a602@redhat.com> (raw)
Message-ID: <20190504065117.wsuWrAn7qdlt7eieq371Ox6xjhGLCRj4fWDaVWqjsJM@z> (raw)
In-Reply-To: <67a38513-89af-7f54-2fc8-05b5777983ca@redhat.com>

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

On 03/05/2019 22.21, Eric Blake wrote:
> On 5/2/19 11:37 PM, Thomas Huth wrote:
>> On 02/05/2019 23.56, Eric Blake wrote:
>>> On 4/28/19 10:18 AM, Thomas Huth wrote:
>>>> QEMU iotest 175 is failing for me when I run it with -raw:
>>>>
>>>>  == creating image with default preallocation ==
>>>>  Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=1048576
>>>> -size=1048576, blocks=0
>>>> +size=1048576, blocks=2
>>>
>>> What filesystem?
>>
>> ext4
> 
> Hmm, it's passing for me on ext4, but that probably means we have
> different configuration parameters. I'm not sure how to easily show what
> parameters a particular ext4 partition uses to compare the differences
> between your setup and mine (mine is tuned to whatever defaults Fedora's
> installer chose on my behalf), so maybe someone else can chime in.

$ sudo tune2fs -l /dev/mapper/Home
tune2fs 1.42.9 (28-Dec-2013)
Filesystem volume name:   <none>
Last mounted on:          /home
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr dir_index filetype
needs_recovery meta_bg extent 64bit flex_bg sparse_super large_file
huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              36700160
Block count:              146800640
Reserved block count:     5873663
Free blocks:              56266267
Free inodes:              35403275
First block:              1
Block size:               1024
Fragment size:            1024
Group descriptor size:    64
Blocks per group:         8192
Fragments per group:      8192
Inodes per group:         2048
Inode blocks per group:   256
First meta block group:   258
Flex block group size:    16
Filesystem created:       Thu Apr 19 18:34:33 2018
Last mount time:          Sat May  4 08:20:36 2019
Last write time:          Sat May  4 08:20:36 2019
Mount count:              224
Maximum mount count:      -1
Last checked:             Thu Apr 19 18:34:33 2018
Check interval:           0 (<none>)
Lifetime writes:          1826 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          128
Journal inode:            8
First orphan inode:       11076944
Default directory hash:   half_md4
Directory Hash Seed:      08e1be04-c3a3-4c37-a059-cf54af5c4bc0
Journal backup:           inode blocks

IIRC I talked to stefanha on IRC about this some weeks ago already, and
he was able to reproduce the problem when using a certain parameter to
create the file system. However, I fail to remember which parameter it
was. Maybe Stefan still remembers...

 Thomas


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2019-05-04  6:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-28 15:18 [Qemu-devel] Failing QEMU iotest 175 Thomas Huth
2019-04-28 15:18 ` Thomas Huth
2019-05-02 21:56 ` Eric Blake
2019-05-02 21:56   ` Eric Blake
2019-05-03  4:37   ` Thomas Huth
2019-05-03  4:37     ` Thomas Huth
2019-05-03 20:21     ` Eric Blake
2019-05-03 20:21       ` Eric Blake
2019-05-03 21:31       ` Nir Soffer
2019-05-03 21:31         ` Nir Soffer
2019-05-10 21:15         ` [Qemu-devel] [Qemu-block] " Nir Soffer
2019-05-04  6:51       ` Thomas Huth [this message]
2019-05-04  6:51         ` [Qemu-devel] " Thomas Huth
2019-05-06 17:44         ` Eric Blake
2019-05-15 14:56           ` Stefan Hajnoczi
2019-05-10 13:54 ` Max Reitz
2019-05-10 16:42   ` Thomas Huth
2019-05-10 17:39     ` Max Reitz

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=22933e94-18da-257c-7931-da511bc5a602@redhat.com \
    --to=thuth@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=nirsof@gmail.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).