util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anatoly Pugachev <matorola@gmail.com>
To: Karel Zak <kzak@redhat.com>, Mikulas Patocka <mpatocka@redhat.com>
Cc: util-linux <util-linux@vger.kernel.org>,
	Mike Snitzer <msnitzer@redhat.com>,
	Heinz Mauelshagen <heinzm@redhat.com>,
	dm-devel@redhat.com, lvm-devel@redhat.com
Subject: Re: [PATCH] blkid: retport block size of a filesystem
Date: Tue, 3 Sep 2019 15:36:46 +0300	[thread overview]
Message-ID: <CADxRZqwURQJMCCAkY8TvjBaQnCL9j1AHN3mY6b1q3bN-VCZRyA@mail.gmail.com> (raw)
In-Reply-To: <20190902105909.ah4pi4nwjefygskd@10.255.255.10>

On Mon, Sep 2, 2019 at 1:59 PM Karel Zak <kzak@redhat.com> wrote:
> Applied (with two small fixes), thanks!

Karel, Mikulas,

ts/blkid/low-probe started to fail on sparc64 with this patch:

        blkid: superblocks probing: [97] xfs-log             ... OK
        blkid: superblocks probing: [98] xfs                 ...
FAILED (blkid/low-probe-xfs)

but is "OK" on x86_64.

$ diff -u expected/blkid/low-probe-xfs output/blkid/low-probe-xfs
--- expected/blkid/low-probe-xfs        2019-09-03 12:45:18.779505561 +0300
+++ output/blkid/low-probe-xfs  2019-09-03 14:35:41.569815684 +0300
@@ -1,4 +1,4 @@
-ID_FS_BLOCK_SIZE=512
+ID_FS_BLOCK_SIZE=131072
 ID_FS_LABEL=test-xfs
 ID_FS_LABEL_ENC=test-xfs
 ID_FS_TYPE=xfs

$ md5sum output/blkid/images-fs/xfs.img
c4a59d4039b5ed5557e8502ca2906373  output/blkid/images-fs/xfs.img

(md5 is the same as on x86_64 test machine)

You can use gcc202 sparc64 machine from gcc compile farm for the test.

PS: can someone regenerate xfs.img(xz) with more recent XFS filesystem version?

$ xfs_info output/blkid/images-fs/xfs.img
xfs_info: V1 inodes unsupported. Please try an older xfsprogs.

$ dpkg -l xfsprogs
ii  xfsprogs       5.0.0-1      sparc64      Utilities for managing
the XFS filesystem

  reply	other threads:[~2019-09-03 12:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 15:52 [PATCH] blkid: retport block size of a filesystem Mikulas Patocka
2019-09-02 10:59 ` Karel Zak
2019-09-03 12:36   ` Anatoly Pugachev [this message]
2019-09-03 13:01     ` Karel Zak
2019-09-03 16:41       ` Anatoly Pugachev

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=CADxRZqwURQJMCCAkY8TvjBaQnCL9j1AHN3mY6b1q3bN-VCZRyA@mail.gmail.com \
    --to=matorola@gmail.com \
    --cc=dm-devel@redhat.com \
    --cc=heinzm@redhat.com \
    --cc=kzak@redhat.com \
    --cc=lvm-devel@redhat.com \
    --cc=mpatocka@redhat.com \
    --cc=msnitzer@redhat.com \
    --cc=util-linux@vger.kernel.org \
    /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).