From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: "swadmin - levigo.de" <swadmin@levigo.de>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Mounting xfs filesystem takes long time
Date: Tue, 19 Jun 2018 09:18:19 -0700 [thread overview]
Message-ID: <20180619161819.GD21698@magnolia> (raw)
In-Reply-To: <2a9a023d-fa37-59dc-caf2-c7c4167d3c75@levigo.de>
On Tue, Jun 19, 2018 at 02:27:29PM +0200, swadmin - levigo.de wrote:
> Hi @all
> I have a problem with mounting a large XFS filesystem which takes about
> 8-10 minutes.
>
>
>
> :~# df -h /graylog_data
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/vgdata-graylog_data 11T 5.0T 5.1T 50% /graylog_data
>
> ----
>
> :~# xfs_info /dev/mapper/vgdata-graylog_data
> meta-data=/dev/mapper/vgdata-graylog_data isize=512 agcount=40805,
> agsize=65792 blks
41,000 AGs is a lot of metadata to load. Did someone growfs a 1G fs
into a 11T fs?
--D
> = sectsz=512 attr=2, projid32bit=1
> = crc=1 finobt=1 spinodes=0 rmapbt=0
> = reflink=0
> data = bsize=4096 blocks=2684612608, imaxpct=25
> = sunit=0 swidth=0 blks
> naming =version 2 bsize=4096 ascii-ci=0 ftype=1
> log =internal bsize=4096 blocks=2560, version=2
> = sectsz=512 sunit=0 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
>
> ----
>
> :~# strace -f mount /dev/mapper/vgdata-graylog_data /graylog_data >
> /root/mount 2>&1
>
> [...]
>
> stat("/sbin/mount.xfs", 0x7ffe36bcfe80) = -1 ENOENT (No such file or
> directory)
> stat("/sbin/fs.d/mount.xfs", 0x7ffe36bcfe80) = -1 ENOENT (No such file
> or directory)
> stat("/sbin/fs/mount.xfs", 0x7ffe36bcfe80) = -1 ENOENT (No such file or
> directory)
> getuid() = 0
> geteuid() = 0
> getgid() = 0
> getegid() = 0
> prctl(PR_GET_DUMPABLE) = 1
> stat("/run", {st_mode=S_IFDIR|0755, st_size=720, ...}) = 0
> lstat("/run/mount/utab", {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
> open("/run/mount/utab", O_RDWR|O_CREAT|O_CLOEXEC, 0644) = 3
> close(3) = 0
> mount("/dev/mapper/vgdata-graylog_data", "/graylog_data", "xfs",
> MS_MGC_VAL, NULL
>
>
> [here is where the 10 minutes happen]
>
>
> ) = 0
> --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
> close(1) = 0
> close(2) = 0
> exit_group(0) = ?
> +++ exited with 0 +++
>
> [Now the mount is ok]
>
>
> can anyone help me or know a kind of these problem. What else to try out?
>
> BR
> Sascha
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-06-19 16:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 12:27 Mounting xfs filesystem takes long time swadmin - levigo.de
2018-06-19 16:00 ` Emmanuel Florac
2018-06-19 16:18 ` Darrick J. Wong [this message]
2018-06-19 19:21 ` Eric Sandeen
2018-06-21 19:15 ` Luis R. Rodriguez
2018-06-21 19:19 ` Eric Sandeen
2018-06-21 21:50 ` Chris Murphy
2018-06-21 22:19 ` Dave Chinner
2018-06-22 3:19 ` Chris Murphy
2018-06-22 4:02 ` Dave Chinner
2018-06-27 23:23 ` Luis R. Rodriguez
2018-06-27 23:37 ` Eric Sandeen
2018-06-28 2:05 ` Dave Chinner
2018-06-28 8:19 ` Carlos Maiolino
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=20180619161819.GD21698@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=swadmin@levigo.de \
/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).