From: Boaz Harrosh <openosd@gmail.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>, Paul Menzel <pmenzel@molgen.mpg.de>
Cc: linux-fsdevel@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Donald Buczek <buczek@molgen.mpg.de>
Subject: Re: File system for scratch space (in HPC cluster)
Date: Thu, 24 Oct 2019 18:01:05 +0300 [thread overview]
Message-ID: <70755c40-b800-8ba0-a0df-4206f6b8c8d4@gmail.com> (raw)
In-Reply-To: <20191024145504.GD1124@mit.edu>
On 24/10/2019 17:55, Theodore Y. Ts'o wrote:
> On Thu, Oct 24, 2019 at 12:43:40PM +0200, Paul Menzel wrote:
>>
>> In our cluster, we offer scratch space for temporary files. As
>> these files are temporary, we do not need any safety
>> requirements – especially not those when the system crashes or
>> shuts down. So no `sync` is for example needed.
>>
>> Are there file systems catering to this need? I couldn’t find
>> any? Maybe I missed some options for existing file systems.
>
> You could use ext4 in nojournal mode. If you want to make sure that
> fsync() doesn't force a cache flush, you can mount with the nobarrier
> mount option.
>
And open the file with O_TMPFILE|O_EXCL so there is no metadata as well.
I think xfs for O_TMPFILE|O_EXCL does not do any fsync, but I'm
not sure
> - Ted
>
next prev parent reply other threads:[~2019-10-24 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 10:43 File system for scratch space (in HPC cluster) Paul Menzel
2019-10-24 14:55 ` Theodore Y. Ts'o
2019-10-24 15:01 ` Boaz Harrosh [this message]
2019-10-24 20:34 ` Theodore Y. Ts'o
2019-10-25 8:33 ` Paul Menzel
2019-10-24 17:51 ` Andreas Dilger
2019-10-25 8:35 ` Paul Menzel
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=70755c40-b800-8ba0-a0df-4206f6b8c8d4@gmail.com \
--to=openosd@gmail.com \
--cc=buczek@molgen.mpg.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=tytso@mit.edu \
/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).