Comment 0 for bug 1859827

The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.

The i386 kernel has gone away, only amd64 is available:

- The i386 kernel build is dropped as of 5.3.0-16.17:
  * Drop i386 build for 19.10 (LP: #1845714)

- Only linux-libc-dev:i386 is still built as of 5.3.0-17.18
  * Re-enable linux-libc-dev build on i386 (LP: #1846508)

The last passing autopkgtests for gfs2-utils:i386 are on 5.3.0-13.14 built for i386.
The same kernel version built for amd64 _fails_.
(so it's potentially user/kernel interface, or kernel-only.)

- i386/i686)

# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:43:47 UTC 2019 i686

root@sf256930ei:~# gfs2_jadd -j 1 /mnt
Filesystem: /mnt
Old journals: 2
New journals: 3

- amd64/x86_64)

# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64

# gfs2_jadd -j 1 /mnt
GETFLAGS: Inappropriate ioctl for device