From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 209039] xfs_fsr skips most of the files as no improvement will be made
Date: Wed, 26 Aug 2020 11:04:37 +0000 [thread overview]
Message-ID: <bug-209039-201763-BNwTvHz8PU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209039-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209039
--- Comment #2 from mgutt (marc@gutt.it) ---
Ok. This means as my filesystem has a blocksize (bsize) of 4 KiB (4096 bytes):
xfs_info /dev/md1
meta-data=/dev/md1 isize=512 agcount=11, agsize=268435455
blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=0
= reflink=1
data = bsize=4096 blocks=2929721331, imaxpct=5
= 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
each extend can't be bigger than 8GB as mentioned in the docs:
https://xfs.org/docs/xfsdocs-xml-dev/XFS_Filesystem_Structure//tmp/en-US/html/Data_Extents.html
>If a file is zero bytes long, it will have no extents, di_nblocks and
>di_nexents will be zero. Any file with data will have at least one extent, and
>each extent can use from 1 to over 2 million blocks (221) on the filesystem.
>For a default 4KB block size filesystem, a single extent can be up to 8GB in
>length.
Good to know. Maybe this information should be part of xfs_fsr output? At the
moment it creates the impression with "ideal 674" and "can_save=3" that it
could be more defragmentated.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-08-26 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 7:40 [Bug 209039] New: xfs_fsr skips most of the files as no improvement will be made bugzilla-daemon
2020-08-26 10:33 ` Brian Foster
2020-08-26 10:33 ` [Bug 209039] " bugzilla-daemon
2020-08-26 11:04 ` bugzilla-daemon [this message]
2020-08-26 16:27 ` bugzilla-daemon
2020-09-01 7:50 ` 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-209039-201763-BNwTvHz8PU@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