From: Jan Kara <jack@suse.cz>
To: Paul Richards <paul.richards@gmail.com>
Cc: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org
Subject: Re: Query about ext4 commit interval vs dirty_expire_centisecs
Date: Wed, 18 Dec 2019 12:22:20 +0100 [thread overview]
Message-ID: <20191218112220.GA13668@quack2.suse.cz> (raw)
In-Reply-To: <CAMoswejK1bySFnT42aEA8e-MphktZzGLzr9WK0kkxBmg=3+Kng@mail.gmail.com>
On Wed 18-12-19 10:35:56, Paul Richards wrote:
> I found it here:
> https://www.kernel.org/doc/Documentation/filesystems/ext4.txt
>
> I think this might be the source, but I'm not sure:
> https://github.com/torvalds/linux/blame/master/Documentation/admin-guide/ext4.rst#L185-L187
Yes, that's it. Somehow my grep capabilities failed me :-| Thanks for the
pointer.
> While searching for this I also found a copy of the same `commit`
> documentation here:
> https://github.com/torvalds/linux/blob/master/Documentation/filesystems/ocfs2.txt
> I don't know if the same correction should be made for ocfs2 or not.
For OCFS2 it is somewhat different since it doesn't do delayed allocation.
So the text is actually correct for file creation. It is still incorrect
for file overwrites though on which commit interval has no effect.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2019-12-18 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 8:47 Query about ext4 commit interval vs dirty_expire_centisecs Paul Richards
2019-12-13 15:59 ` Jan Kara
2019-12-17 14:42 ` Paul Richards
2019-12-18 8:33 ` Jan Kara
2019-12-18 10:35 ` Paul Richards
2019-12-18 11:22 ` Jan Kara [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=20191218112220.GA13668@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=paul.richards@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox