mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rong Chen <rong.a.chen@intel.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: David Sterba <dsterba@suse.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	lkp@01.org
Subject: Re: [btrfs] 3ae92b3782: xfstests.generic.269.fail
Date: Wed, 4 Sep 2019 08:54:10 +0800	[thread overview]
Message-ID: <d288921c-af80-0623-60eb-ff8c24d92985@intel.com> (raw)
In-Reply-To: <20190903132531.ojllcte3au7ipggd@MacBook-Pro-91.local>

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]



On 9/3/19 9:25 PM, Josef Bacik wrote:
> On Tue, Sep 03, 2019 at 04:06:33PM +0800, kernel test robot wrote:
>> FYI, we noticed the following commit (built with gcc-7):
>>
>> commit: 3ae92b3782182d282a92573abe95c96d34ca6e73 ("btrfs: change the minimum global reserve size")
>> https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git master
>>
>> in testcase: xfstests
>> with following parameters:
>>
>> 	disk: 4HDD
>> 	fs: btrfs
>> 	test: generic-group13
>>
>> test-description: xfstests is a regression test suite for xfs and other files ystems.
>> test-url: git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
>>
>>
>> on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
>>
>> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>>
>>
> It would help if you could capture generic/269.full, but this is likely a
> problem with fsck that I fixed a few weeks ago where we're seeing nbytes of an
> inode is wrong, but there's an orphan item so it doesn't matter.  This patch
> just made it more likely for us to have a still being iput'ed inode after a
> transaction commit.  Thanks,
>
> Josef

Hi Josef,

I enclose the generic/269.full file for your reference.

Best Regards,
Rong Chen

[-- Attachment #2: 269.full --]
[-- Type: text/plain, Size: 4551 bytes --]

btrfs-progs v4.7.3
See http://btrfs.wiki.kernel.org for more information.

Label:              (null)
UUID:               
Node size:          16384
Sector size:        4096
Filesystem size:    512.00MiB
Block group profiles:
  Data:             single            8.00MiB
  Metadata:         DUP              32.00MiB
  System:           DUP               8.00MiB
SSD detected:       no
Incompat features:  extref, skinny-metadata
Number of devices:  1
Devices:
   ID        SIZE  PATH
    1   512.00MiB  /dev/vdb

fsstress -p128 -n999999999 -f setattr=1 -ffsync=0 -fsync=0 -ffdatasync=0 -d /fs/scratch/fsstress.2854
dd: error writing '/fs/scratch/SPACE_CONSUMER': No space left on device
34+0 records in
33+0 records out
dd: failed to open '/fs/scratch/SPACE_CONSUMER': No space left on device
dd: failed to open '/fs/scratch/SPACE_CONSUMER': No space left on device
dd: failed to open '/fs/scratch/SPACE_CONSUMER': No space left on device
dd: failed to open '/fs/scratch/SPACE_CONSUMER': No space left on device
dd: failed to open '/fs/scratch/SPACE_CONSUMER': No space left on device
dd: failed to open '/fs/scratch/SPACE_CONSUMER': No space left on device
dd: failed to open '/fs/scratch/SPACE_CONSUMER': No space left on device
dd: failed to open '/fs/scratch/SPACE_CONSUMER': No space left on device
dd: failed to open '/fs/scratch/SPACE_CONSUMER': No space left on device
Killing fsstress process...
_check_btrfs_filesystem: filesystem on /dev/vdb is inconsistent
*** fsck.btrfs output ***
checking extents
checking free space cache
checking fs roots
root 5 inode 1551 errors 400, nbytes wrong
Checking filesystem on /dev/vdb
UUID: f5ee8129-b434-4217-a8fb-bae2bf4c0062
found 461627392 bytes used err is 1
total csum bytes: 267348
total tree bytes: 9715712
total fs tree bytes: 7602176
total extent tree bytes: 1540096
btree space waste bytes: 1712570
file data blocks allocated: 1012891648
 referenced 399106048
*** end fsck.btrfs output
*** mount output ***
rootfs on / type rootfs (rw)
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=1729372k,nr_inodes=432343,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
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)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
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/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=38289)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmp on /tmp type tmpfs (rw,relatime)
inn:/result on /inn/result type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.1,mountvers=3,mountport=60631,mountproto=udp,local_lock=none,addr=192.168.1.1)
*** end mount output

      reply	other threads:[~2019-09-04  0:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03  8:06 kernel test robot
2019-09-03 13:25 ` Josef Bacik
2019-09-04  0:54   ` Rong Chen [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=d288921c-af80-0623-60eb-ff8c24d92985@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=sfr@canb.auug.org.au \
    /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

all inboxes | Powered by JetHome®