From: Wang Yugui <wangyugui@e16-tech.com>
To: fdmanana@gmail.com
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: 'ls /mnt/scratch/' freeze(deadlock?) when run xfstest(btrfs/232)
Date: Wed, 21 Apr 2021 23:57:34 +0800 [thread overview]
Message-ID: <20210421235733.9C11.409509F4@e16-tech.com> (raw)
In-Reply-To: <CAL3q7H6V+x_Pu=bxTFGsuZLHf2mh_DOcthJx7HCSYCL79rjzxw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
Hi,
> That's the problem, qgroup flushing triggers writeback for an inode
> for which we have a page dirtied and locked.
> This should fix it: https://pastebin.com/raw/U9GUZiEf
>
> Try it out and I'll write a changelog later.
> Thanks.
we run xfstest on two server with this patch.
one passed the tests.
but one got a btrfs/232 error.
btrfs/232 32s ... _check_btrfs_filesystem: filesystem on /dev/nvme0n1p1 is inconsistent
(see /usr/hpc-bio/xfstests/results//btrfs/232.full for details)
...
[4/7] checking fs roots
root 5 inode 337 errors 400, nbytes wrong
ERROR: errors found in fs roots
...
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2021/04/21
[-- Attachment #2: 232.full --]
[-- Type: application/octet-stream, Size: 3558 bytes --]
wrote 943718400/943718400 bytes at offset 0
900 MiB, 230400 ops; 0.5758 sec (1.526 GiB/sec and 400076.4035 ops/sec)
quota rescan started
_check_btrfs_filesystem: filesystem on /dev/nvme0n1p1 is inconsistent
*** fsck.btrfs output ***
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space tree
[4/7] checking fs roots
root 5 inode 337 errors 400, nbytes wrong
ERROR: errors found in fs roots
Opening filesystem to check...
Checking filesystem on /dev/nvme0n1p1
UUID: 7d0c105c-a709-4d31-b5e9-2f520a5e2f13
found 1325080576 bytes used, error(s) found
total csum bytes: 1091660
total tree bytes: 9912320
total fs tree bytes: 7733248
total extent tree bytes: 458752
btree space waste bytes: 5394987
file data blocks allocated: 2033995776
referenced 1373466624
*** end fsck.btrfs output
*** mount output ***
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=98963756k,nr_inodes=24740939,mode=755,inode64)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755,inode64)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755,inode64)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
none on /sys/kernel/tracing type tracefs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/sda1 on / type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=37,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=50652)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/sdg1 on /archive type btrfs (rw,noatime,space_cache=v2,subvolid=5,subvol=/)
/dev/sdg1 on /nodetmp type btrfs (rw,noatime,space_cache=v2,subvolid=257,subvol=/nodetmp)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=19801996k,mode=700,inode64)
*** end mount output
next prev parent reply other threads:[~2021-04-21 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 0:31 'ls /mnt/scratch/' freeze(deadlock?) when run xfstest(btrfs/232) Wang Yugui
2021-04-21 12:17 ` Wang Yugui
2021-04-21 13:29 ` Filipe Manana
2021-04-21 15:57 ` Wang Yugui [this message]
2021-04-21 16:03 ` Filipe Manana
2021-04-21 23:19 ` Qu Wenruo
2021-04-21 23:43 ` Qu Wenruo
2021-04-22 0:32 ` Wang Yugui
2021-04-22 0:57 ` Qu Wenruo
2021-04-22 1:25 ` Wang Yugui
2021-04-22 4:16 ` Wang Yugui
2021-04-22 11:06 ` Filipe Manana
2021-04-22 10:59 ` Filipe Manana
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=20210421235733.9C11.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@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