qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Thomas Huth <thuth@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: Mon, 6 May 2019 12:44:56 -0500	[thread overview]
Message-ID: <20f1aecc-02b4-781c-9ada-7ac6c73892a3@redhat.com> (raw)
In-Reply-To: <22933e94-18da-257c-7931-da511bc5a602@redhat.com>

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

On 5/4/19 1:51 AM, Thomas Huth wrote:

>> 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
> 

# tune2fs -l /dev/mapper/fedora-home
tune2fs 1.44.6 (5-Mar-2019)
Filesystem volume name:   home
Last mounted on:          /home
Filesystem UUID:          3ef45c0b-b2a0-43da-a1d3-c4f726097eda
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index
filetype needs_recovery extent 64bit flex_bg sparse_super large_file
huge_file dir_nlink extra_isize metadata_csum
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              13107200
Block count:              52428800
Reserved block count:     2621440
Free blocks:              27184765
Free inodes:              12049129
First block:              0
Block size:               4096
Fragment size:            4096
Group descriptor size:    64
Reserved GDT blocks:      1024
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Thu Dec  6 16:17:23 2018
Last mount time:          Wed Apr  3 10:19:05 2019
Last write time:          Wed Apr  3 10:19:05 2019
Mount count:              12
Maximum mount count:      -1
Last checked:             Thu Dec  6 16:17:23 2018
Check interval:           0 (<none>)
Lifetime writes:          1962 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          256
Required extra isize:     32
Desired extra isize:      32
Journal inode:            8
First orphan inode:       5248434
Default directory hash:   half_md4
Directory Hash Seed:      d1bbea0e-dd2e-4df7-b7f0-f7300c524cc9
Journal backup:           inode blocks
Checksum type:            crc32c
Checksum:                 0x3a8a8676

I'm definitely seeing some differences in the two configs (such as your
block size of 1k vs. mine at 4k), but not sure which are the most
important, nor how to easily recreate a setup that matches yours.

> 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...
> 

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org


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

  parent reply	other threads:[~2019-05-06 17:58 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       ` [Qemu-devel] " Thomas Huth
2019-05-04  6:51         ` Thomas Huth
2019-05-06 17:44         ` Eric Blake [this message]
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=20f1aecc-02b4-781c-9ada-7ac6c73892a3@redhat.com \
    --to=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 \
    --cc=thuth@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).