From: Hubert Bahr <hab@hbahr.org>
To: linux-ext4@vger.kernel.org
Subject: extremely long delays are they possible?
Date: Sat, 16 Oct 2010 01:02:12 -0500 [thread overview]
Message-ID: <4CB93FE4.6030005@hbahr.org> (raw)
In reality I would prefer writes only occur to an ssd if the FS write
cache is overflowing. The application is package rebuilding. The
package is brought in from nfs expanded built (compiled etc) then the
results written back to an nfs mount and the log written to Cluster Head
then everything erased. However, if there are build problems the
expanded file system and results are left intact. My Memory Size is
large enough (16GB) to buffer the whole process except when a build
problem occur's. Since this can be hours into a build I would prefer to
capture. This is part of a cluster batch process that is only examined
at the expected end of the total batch process. Capturing the problems
precludes using only a ramfs, but I would like to avoid needless writes
to the ssd. I am afraid that embedded fsyncs may blow this anyway.
Maybe I could use some on error mv but I prefer the dynamic memory
sharing rather than a fixed ramfs. The longest single package build I
have observed is 11.5 hours and it also took the most space.
would fstab options like ext4
commit=50000,noatime,delalloc,data=writeback give me the desired action?
Thanks
Hubert
reply other threads:[~2010-10-16 6:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CB93FE4.6030005@hbahr.org \
--to=hab@hbahr.org \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).