All of lore.kernel.org
 help / color / mirror / Atom feed
From: yebin <yebin@huaweicloud.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: djwong@kernel.org, linux-xfs@vger.kernel.org,
	chandan.babu@oracle.com, dchinner@redhat.com, yebin10@huawei.com
Subject: Re: [PATCH 0/2] Fix two issues about swapext
Date: Tue, 16 Dec 2025 17:31:06 +0800	[thread overview]
Message-ID: <694126DA.5010203@huaweicloud.com> (raw)
In-Reply-To: <aUAbXIkQ_LfYuPJc@infradead.org>



On 2025/12/15 22:29, Christoph Hellwig wrote:
> On Mon, Dec 15, 2025 at 03:19:43PM +0800, yebin wrote:
>> First, we encountered the issue described in
>> https://access.redhat.com/solutions/6095011 in our production
>
> That's behind a paywall unfortunately.
>
In fact, the root cause of the problem was not identified.
>>> Any chance you could add a reproducer to xfstests?
>>>
>> Yes, this issue is quite reproducible. It occurs inevitably when following
>> certain steps. This problem has existed for a long time. I think the reason
>> it's not easily detected is that the XFS_IOC_SWAPEXT IOCTL command is
>> generally used during defragmentation. Therefore, it is almost never
>> included in typical log replay scenarios.
>
> Can you send out an xfstests for this?  Or at least a shell script
> fragment?
>
You can reproduce issue as follow steps:
mkfs.xfs -f /dev/sdb
mount  /dev/sdb /home/test
fallocate -l1m  /home/test/file1
for i in `seq 1 127`;do fallocate -p -o $((8192*i)) -l 4096 
/home/test/file1;done
fallocate -l1m  /home/test/file2
for i in `seq 1 127`;do fallocate -p -o $((8192*i)) -l 4096 
/home/test/file2;done
umount /home/test
mount /dev/sdb /home/test
xfs_io -c "swapext /home/test/file1" /home/test/file2
truncate -s 81920 /home/test/file1
truncate -s 81920 /home/test/file2
// wait for iclog submit to disk
echo offline > /sys/class/scsi_disk/0\:0\:0\:1/device/state && umount 
/home/test
echo running > /sys/class/scsi_disk/0\:0\:0\:1/device/state
mount /dev/sdb /home/test  //will trigger issue


      reply	other threads:[~2025-12-16  9:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-13  3:59 [PATCH 0/2] Fix two issues about swapext Ye Bin
2025-12-13  3:59 ` [PATCH 1/2] xfs: fix checksum error when call xfs_recover_inode_owner_change() Ye Bin
2025-12-13  3:59 ` [PATCH 2/2] xfs: fix xfs_recover_inode_owner_change() failed Ye Bin
2025-12-15  5:37 ` [PATCH 0/2] Fix two issues about swapext Christoph Hellwig
2025-12-15  7:19   ` yebin
2025-12-15 14:29     ` Christoph Hellwig
2025-12-16  9:31       ` yebin [this message]

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=694126DA.5010203@huaweicloud.com \
    --to=yebin@huaweicloud.com \
    --cc=chandan.babu@oracle.com \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=yebin10@huawei.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 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.