cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs2-utils: mkfs segfault with 4.16 kernel
Date: Fri, 4 May 2018 11:27:35 +0100	[thread overview]
Message-ID: <c9bf80bf-7b44-edf2-c319-6d63b735b437@redhat.com> (raw)
In-Reply-To: <20180504102140.GQ4608@gavran.carpriv.carnet.hr>

On 04/05/18 11:21, Valentin Vidic wrote:
> On Fri, May 04, 2018 at 11:06:59AM +0100, Andrew Price wrote:
>> Can you reproduce it with the master branch? Also, what is the size of your
>> test file? And what architecture is this on?
> 
> Master branch seems to fail too.  Test file was 200 MB on amd64.
> Also attaching testsuite.log now in case it helps.

Ok thanks, I'll look into it.

One other thing to check is whether ./configure was re-run after 
gfs2_ondisk.h was upgraded.

Andy

> 
> ## ----------------------------- ##
> ## gfs2-utils master test suite. ##
> ## ----------------------------- ##
> 
> mkfs.gfs2 tests
> 
>    1: Locking protocol validation                     ok
>    2: Resource group size validation                  ok
>    3: Journal size validation                         ok
>    4: Block count validation                          ok
>    5: Quota change file size validation               ok
>    6: Locking protocols                               FAILED (mkfs.at:36)
>    7: Valid block sizes 512-4096                      FAILED (mkfs.at:42)
>    8: Max. blocks, min. block size                    FAILED (mkfs.at:50)
>    9: Max. blocks, max. block size                    FAILED (mkfs.at:55)
>   10: Max. resource group size                        FAILED (mkfs.at:60)
>   11: Min. resource group size                        FAILED (mkfs.at:65)
>   12: Max. resource group size, min. block size       FAILED (mkfs.at:70)
>   13: Max. journal size                               FAILED (mkfs.at:75)
>   14: Min. journal size                               FAILED (mkfs.at:80)
>   15: Max. quota change file size                     FAILED (mkfs.at:85)
>   16: Min. quota change file size                     FAILED (mkfs.at:90)
>   17: Lock table validation                           FAILED (mkfs.at:98)
>   18: Device i/o limits handling                      FAILED (mkfs.at:114)
>   19: Resource group alignment                        FAILED (mkfs.at:122)
>   20: Values of rg_skip                               FAILED (mkfs.at:129)
>   21: Values of rg_data0, rg_data, rg_bitbytes        FAILED (mkfs.at:145)
>   22: Small filesystems                               FAILED (mkfs.at:162)
> 
> fsck.gfs2 tests
> 
>   23: Conflicting options                             ok
>   24: Fix invalid block sizes                         FAILED (fsck.at:17)
>   25: Fix invalid goal blocks                         FAILED (fsck.at:26)
>   26: Fix bad resource group #0                       FAILED (fsck.at:31)
>   27: Fix bad resource group #1                       FAILED (fsck.at:36)
>   28: Fix bad rindex entry #1                         FAILED (fsck.at:46)
>   29: Rebuild bad journal                             FAILED (fsck.at:52)
> 
> gfs2_edit tests
> 
>   30: Save/restoremeta, defaults                      FAILED (edit.at:7)
>   31: Save/restoremeta, no compression                FAILED (edit.at:20)
>   32: Save/restoremeta, min. block size               FAILED (edit.at:30)
>   33: Save/restoremeta, 4 journals                    FAILED (edit.at:40)
>   34: Save/restoremeta, min. block size, 4 journals   FAILED (edit.at:50)
> 
> libgfs2 unit tests
> 
>   35: meta.c                                          FAILED (libgfs2.at:4)
>   36: rgrp.c                                          ok
> 
> ## ------------- ##
> ## Test results. ##
> ## ------------- ##
> 
> ERROR: All 36 tests were run,
> 29 failed unexpectedly.
> ## -------------------------- ##
> ## testsuite.log was created. ##
> ## -------------------------- ##
> 
> Please send `tests/testsuite.log' and all information you think might
> help:
> 
>     To: <linux-cluster@redhat.com>
>     Subject: [gfs2-utils master] testsuite: 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 24 25 26 27 28 29 30 31 32 33 34 35 failed
> 



  reply	other threads:[~2018-05-04 10:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04  9:42 [Cluster-devel] gfs2-utils: mkfs segfault with 4.16 kernel Valentin Vidic
2018-05-04  9:50 ` Valentin Vidic
2018-05-04 10:06   ` Andrew Price
2018-05-04 10:21     ` Valentin Vidic
2018-05-04 10:27       ` Andrew Price [this message]
2018-05-04 10:42         ` Valentin Vidic
2018-05-04 10:46           ` Andrew Price
2018-05-04 10:54             ` Valentin Vidic
2018-05-04 11:07               ` Andrew Price
2018-05-04 12:01                 ` Valentin Vidic
2018-05-04 13:01                   ` Andrew Price
2018-05-04 13:16                     ` Andrew Price
2018-05-04 14:00                       ` Valentin Vidic
2018-05-09 16:53                         ` Andrew Price
2018-05-10 19:47                           ` Valentin Vidic
2018-05-13  9:13                           ` Valentin Vidic
2018-05-14 13:24                             ` Andrew Price
2018-05-14 13:48                               ` Valentin Vidic

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=c9bf80bf-7b44-edf2-c319-6d63b735b437@redhat.com \
    --to=anprice@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).