From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [ClusterLabs] gfs2-utils 3.5.0 released
Date: Mon, 13 Feb 2023 09:58:43 +0000 [thread overview]
Message-ID: <27e6ad15-381b-12b9-3c3a-310bd886a94a@redhat.com> (raw)
In-Reply-To: <Y+fNfux8S615OSqd@valentin-vidic.from.hr>
On 11/02/2023 17:16, Valentin Vidi? wrote:
> On Thu, Feb 09, 2023 at 01:12:58PM +0000, Andrew Price wrote:
>> gfs2-utils contains the tools needed to create, check, modify and inspect
>> gfs2 filesystems along with support scripts needed on every gfs2 cluster
>> node.
>
> Hi,
>
> Some tests seem to be failing for the new version in Debian:
>
> gfs2_edit tests
>
> 37: Save/restoremeta, defaults FAILED (edit.at:14)
> 38: Save/restoremeta, no compression FAILED (edit.at:24)
> 39: Save/restoremeta, min. block size FAILED (edit.at:34)
> 40: Save/restoremeta, 4 journals FAILED (edit.at:44)
> 41: Save/restoremeta, min. block size, 4 journals FAILED (edit.at:54)
> 42: Save metadata to /dev/null ok
>
> It seems this is all on 32-bit architectures, more info here:
>
> https://buildd.debian.org/status/fetch.php?pkg=gfs2-utils&arch=armel&ver=3.5.0-1&stamp=1676127480&raw=0
> https://buildd.debian.org/status/fetch.php?pkg=gfs2-utils&arch=armhf&ver=3.5.0-1&stamp=1676127632&raw=0
> https://buildd.debian.org/status/fetch.php?pkg=gfs2-utils&arch=i386&ver=3.5.0-1&stamp=1676127477&raw=0
> https://buildd.debian.org/status/fetch.php?pkg=gfs2-utils&arch=mipsel&ver=3.5.0-1&stamp=1676130593&raw=0
>
> Can you check?
>
The smoking gun is
"stderr:
Error: File system is too small to restore this metadata.
File system is 524287 blocks. Restore block = 537439"
It's caused by size_t being used for a variable relating to file size
and it's too small in 32-bit environments.
It should be fixed by this commit:
https://pagure.io/fork/andyp/gfs2-utils/c/a3f3aadc789f214cd24606808f5d8a6608e10219
It's waiting for the CI queue to flush after last week's outage but it
should be in main shortly.
I doubt we have any users on 32-bit architectures but perhaps we can get
a 32-bit test runner added to the CI pool to prevent these issues
slipping through anyway.
Are you happy to carry the patch or do you think this is worth a 3.5.1?
Thanks,
Andy
next prev parent reply other threads:[~2023-02-13 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 13:12 [Cluster-devel] gfs2-utils 3.5.0 released Andrew Price
2023-02-11 17:16 ` [Cluster-devel] [ClusterLabs] " Valentin Vidić
2023-02-13 9:58 ` Andrew Price [this message]
2023-02-13 16:54 ` Andrew Price
2023-02-13 23:52 ` Valentin Vidic
2023-02-14 5:18 ` Fabio M. Di Nitto
2023-02-14 20:17 ` Valentin Vidic
2023-02-15 4:55 ` Fabio M. Di Nitto
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=27e6ad15-381b-12b9-3c3a-310bd886a94a@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).