linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 202441] Possibly vfs cache related replicable xfs regression since 4.19.0  on sata hdd:s
Date: Tue, 29 Jan 2019 00:29:38 +0000	[thread overview]
Message-ID: <bug-202441-201763-xDT6Dzv60A@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202441-201763@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=202441

--- Comment #3 from Dave Chinner (david@fromorbit.com) ---
On Mon, Jan 28, 2019 at 11:26:32PM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=202441
> 
> --- Comment #2 from Roger (rogan6710@gmail.com) ---
> 
> Hello Dave !
> Thanks for the really fast reply :)
> Here is most of the (rather lengthy) system information:
> 
> Single "eight" core processor:
> 
> rogan@trooper:~$ uname -a
> Linux trooper.morgoth.org 4.19.18 #2 SMP Sat Jan 26 13:43:16 CST 2019 x86_64
> AMD FX(tm)-9590 Eight-Core Processor AuthenticAMD GNU/Linux
> 
> root@trooper:~# xfs_repair -V
> xfs_repair version 4.19.0
> 
> root@trooper:~# cat /proc/meminfo 
> MemTotal:       24645396 kB
> MemFree:          358452 kB
> MemAvailable:   22044292 kB
> Buffers:            3152 kB
> Cached:         22005216 kB
> SwapCached:            0 kB
> Active:          1713092 kB
> Inactive:       21824100 kB
> Active(anon):    1157816 kB
> Inactive(anon):   555736 kB
> Active(file):     555276 kB
> Inactive(file): 21268364 kB
....
> Slab:             565012 kB
> SReclaimable:     502684 kB

Ok, so memory is completely used by the page cache, and there is
some inode/dentry cache overhead in the slab caches.

Nothing unusual in the rest of the output , either.

>  xfs_info /dev/sdc1
> xfs_info: /dev/sdc1 contains a mounted filesystem
> 
> fatal error -- couldn't initialize XFS library
> 
> hmm ?

$ man xfs_info
...
        xfs_info [ -t mtab ] mount-point
...
        [...] The mount-point argument is the pathname of the
        directory where the filesystem is mounted. [...]

$ sudo mount /dev/vdc /mnt/scratch
$ sudo xfs_info /dev/vdc
xfs_info: /dev/vdc contains a mounted filesystem

fatal error -- couldn't initialize XFS library
$ sudo xfs_info /mnt/scratch
meta-data=/dev/vdc               isize=512    agcount=500, agsize=268435455
blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=0
data     =                       bsize=4096   blocks=134217727500, imaxpct=1
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=521728, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
$

> I'll do a quick run and give you some dmesg

OK, that'll be interesting :)

Cheers,

Dave.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2019-01-29  0:29 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28 20:41 [Bug 202441] New: Possibly vfs cache related replicable xfs regression since 4.19.0 on sata hdd:s bugzilla-daemon
2019-01-28 22:00 ` Dave Chinner
2019-01-28 22:00 ` [Bug 202441] " bugzilla-daemon
2019-01-28 23:26 ` bugzilla-daemon
2019-01-29  0:29   ` Dave Chinner
2019-01-29  0:29 ` bugzilla-daemon [this message]
2019-01-29  0:43 ` bugzilla-daemon
2019-01-29  1:23   ` Dave Chinner
2019-01-29  0:47 ` bugzilla-daemon
2019-01-29  1:23 ` bugzilla-daemon
2019-01-29  3:36 ` bugzilla-daemon
2019-01-29  9:09 ` bugzilla-daemon
2019-01-29  9:11 ` bugzilla-daemon
2019-01-29  9:27 ` bugzilla-daemon
2019-01-29  9:29 ` bugzilla-daemon
2019-01-29 17:55 ` bugzilla-daemon
2019-01-29 21:41   ` Dave Chinner
2019-01-29 21:19 ` bugzilla-daemon
2019-01-29 21:44   ` Dave Chinner
2019-01-29 21:41 ` bugzilla-daemon
2019-01-29 21:53   ` Dave Chinner
2019-01-29 21:44 ` bugzilla-daemon
2019-01-29 21:53 ` bugzilla-daemon
2019-01-29 22:07 ` bugzilla-daemon
2019-01-29 22:19 ` bugzilla-daemon
2019-01-29 22:23 ` bugzilla-daemon
2019-01-29 22:39 ` bugzilla-daemon
2019-01-29 23:03 ` bugzilla-daemon
2019-01-29 23:28   ` Dave Chinner
2019-01-29 23:28 ` bugzilla-daemon
2019-01-29 23:35 ` bugzilla-daemon
2019-01-30 10:50 ` bugzilla-daemon
2019-01-30 12:00 ` bugzilla-daemon
2019-02-01 21:59 ` bugzilla-daemon
2019-02-03  8:12 ` bugzilla-daemon
2021-11-23 15:43 ` bugzilla-daemon

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=bug-202441-201763-xDT6Dzv60A@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.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 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).