Linux Test Project
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] mkfs: print more info for debugging
Date: Tue, 20 Apr 2021 09:09:58 -0400 (EDT)	[thread overview]
Message-ID: <1716161919.8919863.1618924198482.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAEemH2fcEjre5xd1KuXsAkYzZG6tGaCttE8x3zbjxamVHfUUng@mail.gmail.com>



----- Original Message -----
> On Tue, Apr 20, 2021 at 8:17 PM Jan Stancek <jstancek@redhat.com> wrote:
> >
> >
> >
> > ----- Original Message -----
> > > We can NOT reproduce the problem by manual with both ppc64le and s390x,
> > > so let's print more useful info from test when getting fail.
> >
> > It's mkfs_verify_size, test expects to find 90% blocks (of device size),
> > but lately we miss that by ~1-2%:
> >
> > # mkfs.ext3 /dev/loop0 16000
> > mke2fs 1.46.2 (28-Feb-2021)
> 
> Thanks for the info.
> 
> How reproducible of this issue, and which arch/platform you used?

It seemed pretty consistent with Fedora-Rawhide-20210415.n.0 on power9 ppc64le (9006-22P, J:5279637)

> Or, can you reproduce it with a downgrade e2fsprogs version?

Not immediately, I lost reservation of the machine.

> 
> 
> > /dev/loop0 contains a ext3 file system
> >         created on Fri Apr 16 05:09:23 2021
> > Proceed anyway? (y,N) y
> > Discarding device blocks: done
> > Creating filesystem with 16000 1k blocks and 4000 inodes
> > Filesystem UUID: d66c4c37-13ce-41df-b3c4-345ec1641e1f
> > Superblock backups stored on blocks:
> >         8193
> >
> > Allocating group tables: done
> > Writing inode tables: done
> > Creating journal (1024 blocks): done
> > Writing superblocks and filesystem accounting information: done
> >
> >  mount /dev/loop0  /mnt/test
> > # df -T
> > Filesystem                           Type      1K-blocks      Used
> > Available Use% Mounted on
> > /dev/loop0                           ext3          14343        19
> > 13524   1% /mnt/test
> >
> >
> > >
> > >  mkfs01 1 TPASS: 'mkfs -t ext4  /dev/loop0 ' passed.
> > >  mkfs01 2 TFAIL: 'mkfs -t ext4  /dev/loop0 16000' failed, not expected.
> > >  mkfs01 3 TPASS: 'mkfs -t ext4 -c /dev/loop0 ' passed.
> > >  mkfs01 4 TPASS: 'mkfs -V   ' passed.
> > >  mkfs01 5 TPASS: 'mkfs -h   ' passed.
> > >
> > > Signed-off-by: Li Wang <liwang@redhat.com>
> > > ---
> > >  testcases/commands/mkfs/mkfs01.sh | 6 ++++--
> > >  1 file changed, 4 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/testcases/commands/mkfs/mkfs01.sh
> > > b/testcases/commands/mkfs/mkfs01.sh
> > > index 90368190d..55296c8df 100755
> > > --- a/testcases/commands/mkfs/mkfs01.sh
> > > +++ b/testcases/commands/mkfs/mkfs01.sh
> > > @@ -128,7 +128,8 @@ mkfs_test()
> > >       if [ -n "$device" ]; then
> > >               mkfs_verify_type "$fs_type" "$device"
> > >               if [ $? -ne 0 ]; then
> > > -                     tst_res TFAIL "'${mkfs_cmd}' failed, not expected."
> > > +                     tst_res TFAIL "'${mkfs_cmd}' failed, not expected
> > > type."
> > > +                     cat temp
> > >                       return
> > >               fi
> > >       fi
> > > @@ -136,7 +137,8 @@ mkfs_test()
> > >       if [ -n "$size" ]; then
> > >               mkfs_verify_size "$fs_type" "$size"
> > >               if [ $? -ne 0 ]; then
> > > -                     tst_res TFAIL "'${mkfs_cmd}' failed, not expected."
> > > +                     tst_res TFAIL "'${mkfs_cmd}' failed, not expected
> > > size."
> > > +                     cat temp
> > >                       return
> > >               fi
> > >       fi
> > > --
> > > 2.30.2
> > >
> > >
> > > --
> > > Mailing list info: https://lists.linux.it/listinfo/ltp
> > >
> > >
> >
> 
> 
> --
> Regards,
> Li Wang
> 
> 


  reply	other threads:[~2021-04-20 13:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20  7:53 [LTP] [PATCH] mkfs: print more info for debugging Li Wang
2021-04-20  8:22 ` Petr Vorel
2021-04-20  8:39   ` Li Wang
2021-04-20 12:17 ` Jan Stancek
2021-04-20 13:01   ` Li Wang
2021-04-20 13:09     ` Jan Stancek [this message]
2021-04-21 10:46     ` Jan Stancek

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=1716161919.8919863.1618924198482.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox