From: Petr Vorel <pvorel@suse.cz>
To: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Jan Kara <jack@suse.cz>, Hannes Reinecke <hare@suse.de>,
linux-xfs@vger.kernel.org
Subject: Re: LTP test df01.sh detected different size of loop device in v5.19
Date: Fri, 12 Aug 2022 15:24:14 +0200 [thread overview]
Message-ID: <YvZUfq+3HYwXEncw@pevik> (raw)
In-Reply-To: <YvZTpQFinpkB06p9@pevik>
> Hi all,
> LTP test df01.sh found different size of loop device in v5.19.
> Test uses loop device formatted on various file systems, only XFS fails.
> It randomly fails during verifying that loop size usage changes:
> grep ${TST_DEVICE} output | grep -q "${total}.*${used}" [1]
> How to reproduce:
> # PATH="/opt/ltp/testcases/bin:$PATH" df01.sh -f xfs # it needs several tries to hit
> df saved output:
> Filesystem 1024-blocks Used Available Capacity Mounted on
> ...
> /dev/loop0 256672 16208 240464 7% /tmp/LTP_df01.1kRwoUCCR7/mntpoint
> df output:
> Filesystem 1024-blocks Used Available Capacity Mounted on
> ...
> tmpfs 201780 0 201780 0% /run/user/0
> /dev/loop0 256672 15160 241512 6% /tmp/LTP_df01.1kRwoUCCR7/mntpoint
> => different size
> df01 4 TFAIL: 'df -k -P' failed, not expected.
> Also 'df -T -P' fails.
> It might be a false positive / bug in the test, but it's at least a changed behavior.
> I was able to reproduce it on v5.19 distro kernels (openSUSE, Debian).
> I haven't bisected (yet), nor checked Jens' git tree (maybe it has been fixed).
Forget to note dmesg "operation not supported error" warning on *each* run (even
successful) on affected v5.19:
[ 5097.594021] loop0: detected capacity change from 0 to 524288
[ 5097.658201] operation not supported error, dev loop0, sector 262192 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 0
[ 5097.675670] XFS (loop0): Mounting V5 Filesystem
[ 5097.681668] XFS (loop0): Ending clean mount
[ 5097.956445] XFS (loop0): Unmounting Filesystem
Kind regards,
Petr
> Kind regards,
> Petr
> [1] https://github.com/linux-test-project/ltp/blob/f42f6f3b4671f447b743afe8612917ba4362b8a6/testcases/commands/df/df01.sh#L103-L110
next prev parent reply other threads:[~2022-08-12 13:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 13:20 LTP test df01.sh detected different size of loop device in v5.19 Petr Vorel
2022-08-12 13:24 ` Petr Vorel [this message]
2022-08-12 14:00 ` Petr Vorel
2022-08-12 14:00 ` [LTP] " Petr Vorel
2022-08-14 22:44 ` Dave Chinner
2022-08-14 22:44 ` [LTP] " Dave Chinner
2022-08-15 9:31 ` Petr Vorel
2022-08-15 9:31 ` [LTP] " Petr Vorel
2022-08-15 20:09 ` Eric Sandeen
2022-08-15 20:09 ` [LTP] " Eric Sandeen
2022-08-18 15:25 ` Petr Vorel
2022-08-18 15:25 ` [LTP] " Petr Vorel
2022-08-18 16:05 ` Eric Sandeen
2022-08-18 16:05 ` [LTP] " Eric Sandeen
2022-08-18 16:27 ` Darrick J. Wong
2022-08-18 16:27 ` [LTP] " Darrick J. Wong
2022-08-18 17:01 ` Petr Vorel
2022-08-18 17:01 ` [LTP] " Petr Vorel
2022-08-18 21:19 ` Eric Sandeen
2022-08-18 21:19 ` [LTP] " Eric Sandeen
2022-08-19 16:00 ` Petr Vorel
2022-08-19 16:00 ` [LTP] " Petr Vorel
2022-08-19 16:06 ` Bird, Tim
2022-08-19 16:06 ` Bird, Tim
2022-08-19 19:30 ` Petr Vorel
2022-08-19 19:30 ` Petr Vorel
2022-08-18 21:02 ` Dave Chinner
2022-08-18 21:02 ` [LTP] " Dave Chinner
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=YvZUfq+3HYwXEncw@pevik \
--to=pvorel@suse.cz \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.