From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
"Jeff Layton" <jlayton@redhat.com>,
"Alan Cox" <gnomes@lxorguk.ukuu.org.uk>,
焦晓冬 <milestonejxd@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: POSIX violation by writeback error
Date: Tue, 25 Sep 2018 18:17:30 +0200 [thread overview]
Message-ID: <20180925161730.GA32709@BitWizard.nl> (raw)
In-Reply-To: <20180925154627.GC2933@thunk.org>
On Tue, Sep 25, 2018 at 11:46:27AM -0400, Theodore Y. Ts'o wrote:
> (Especially since you can get most of the functionality by
> using some naming convention for files that in the process of being
> written, and then teach some program that is regularly scanning the
> entire file system, such as updatedb(2) to nuke the files from a cron
> job. It won't be as efficient, but it would be much easier to
> implement.)
It is MUCH easier to have a per-application cleanup job. You can run
that at boot-time.
#/etc/init.d/myname startup script
rm /var/run/myname/unfinished.*
Simple things should be kept simple.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
The plan was simple, like my brother-in-law Phil. But unlike
Phil, this plan just might work.
next prev parent reply other threads:[~2018-09-25 22:25 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJDTihx2yaR-_-9Ks1PoFcrKNZgUOoLdN-wRTTMV76Jg_dCLrw@mail.gmail.com>
2018-09-04 10:56 ` POSIX violation by writeback error Jeff Layton
2018-09-24 23:30 ` Alan Cox
2018-09-25 11:15 ` Jeff Layton
2018-09-25 15:46 ` Theodore Y. Ts'o
2018-09-25 16:17 ` Rogier Wolff [this message]
2018-09-25 16:39 ` Alan Cox
2018-09-25 16:41 ` Jeff Layton
2018-09-25 22:30 ` Theodore Y. Ts'o
2018-09-26 18:10 ` Alan Cox
2018-09-26 21:49 ` Theodore Y. Ts'o
2018-09-27 22:48 ` Alan Cox
2018-09-27 7:18 ` Rogier Wolff
2018-09-27 12:43 ` Jeff Layton
2018-09-27 14:27 ` Theodore Y. Ts'o
2018-09-25 17:35 ` Adam Borowski
2018-09-25 22:46 ` Theodore Y. Ts'o
2018-09-04 6:32 焦晓冬
2018-09-04 7:53 ` Rogier Wolff
2018-09-04 8:58 ` 焦晓冬
2018-09-04 9:29 ` Rogier Wolff
2018-09-04 10:45 ` 焦晓冬
2018-09-04 11:09 ` Jeff Layton
2018-09-04 14:56 ` 焦晓冬
2018-09-04 15:44 ` Jeff Layton
2018-09-04 16:12 ` J. Bruce Fields
2018-09-04 16:23 ` Rogier Wolff
2018-09-04 18:54 ` J. Bruce Fields
2018-09-04 20:18 ` Jeff Layton
2018-09-04 20:35 ` Vito Caputo
2018-09-04 21:02 ` Matthew Wilcox
2018-09-05 0:51 ` Dave Chinner
2018-09-05 8:24 ` 焦晓冬
2018-09-05 10:55 ` Jeff Layton
2018-09-05 12:07 ` Rogier Wolff
2018-09-06 2:57 ` Dave Chinner
2018-09-06 9:17 ` Rogier Wolff
2018-09-24 23:09 ` Alan Cox
2018-09-05 13:53 ` J. Bruce Fields
2018-09-05 7:08 ` Rogier Wolff
2018-09-05 7:39 ` Martin Steigerwald
2018-09-05 8:04 ` Rogier Wolff
2018-09-05 8:37 ` 焦晓冬
2018-09-05 12:07 ` Austin S. Hemmelgarn
2018-09-05 12:46 ` Rogier Wolff
2018-09-05 9:32 ` Martin Steigerwald
2018-09-05 7:37 ` Martin Steigerwald
2018-09-05 11:42 ` Jeff Layton
2018-09-05 8:09 ` 焦晓冬
2018-09-05 13:08 ` Theodore Y. Ts'o
2018-09-24 23:21 ` Alan Cox
2018-09-06 7:28 ` 焦晓冬
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=20180925161730.GA32709@BitWizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=milestonejxd@gmail.com \
--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).