From: Dave Chinner <david@fromorbit.com>
To: Shawn <neutronsharc@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Do I have to fsync after aio_write finishes (with fallocate preallocation) ?
Date: Sat, 26 Aug 2023 13:48:48 +1000 [thread overview]
Message-ID: <ZOl2IHacyqSUFgfi@dread.disaster.area> (raw)
In-Reply-To: <CAB-bdyQw7hRpRPn9JTnpyJt1sA9vPDTVsUTmrhke-EMmGfaHBA@mail.gmail.com>
On Mon, Aug 21, 2023 at 12:01:27PM -0700, Shawn wrote:
> Hello Dave,
> Thank you for your detailed reply. That fallocate() thing makes a lot of sense.
>
> I want to figure out the default extent size in my evn. But
> "xfs_info" doesn't seem to output it? (See below output)
extent size hints are an inode property, not a filesystem geometry
property. xfs_info only queries the later, it knows nothing about
the former.
# xfs_io -c 'stat' </path/to/mnt>
will tell you what the default extent size hint that will be
inherited by newly created sub-directories and files
(fsxattr.extsize).
>
> Also, I want to use this cmd to set the default extent size hint, is
> this correct?
> $ sudo mkfs.xfs -d extszinherit=256 <== the data block is 4KB, so
> 256 is 1MB.
Yes.
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2023-08-26 3:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 19:20 Do I have to fsync after aio_write finishes (with fallocate preallocation) ? Shawn
2022-11-29 21:17 ` Darrick J. Wong
2022-11-29 21:34 ` Dave Chinner
2023-08-21 19:01 ` Shawn
2023-08-26 3:48 ` Dave Chinner [this message]
2023-08-27 1:09 ` Shawn
2023-08-28 1:01 ` Dave Chinner
2023-09-01 1:06 ` Shawn
2023-09-01 3:47 ` Dave Chinner
2023-09-01 23:50 ` Shawn
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=ZOl2IHacyqSUFgfi@dread.disaster.area \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=neutronsharc@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.