From: "Theodore Ts'o" <tytso@mit.edu>
To: Dan Behman <dbehman@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6: marking individual directories as synchronous?
Date: Sat, 19 Jul 2003 20:31:41 -0400 [thread overview]
Message-ID: <20030720003141.GB1085@think> (raw)
In-Reply-To: <Law14-F4339RtMXxIGC0001edbb@hotmail.com>
On Thu, Jul 17, 2003 at 04:59:20PM -0400, Dan Behman wrote:
> Hi,
>
> I'm reading through Joseph Pranevich's great document "Wonderful World of
> Linux 2.6" and I came across something that I'd love to learn more about.
> In the "Block Device Support" -> "Filesystems" section, reference is made
> to "Individual directories can now be marked as synchronous so that all
> changes (additional files, etc.) will be atomic". I searched through the
> update info at kernelnewbies but
> couldn't find any more information on this - could someone please elaborate
> on this? What is it and how does it work? Is there any design
> documentation for this?
He is is probably referring to "chattr +S". See the man page for
chattr for more information. Note that strictly speaking this does
not necessarily give you "atomic changes". It does mean that changes
are scheduled to be immediately written to disk, but that does not
guarantee atomicity, at least not for all filesystems and for all
operations. You *can* be guaranteed that system calls will not return
until the changes are on disk; note though that this does have has
some significant performance impacts.
- Ted
next prev parent reply other threads:[~2003-07-20 2:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 20:59 2.6: marking individual directories as synchronous? Dan Behman
2003-07-20 0:31 ` Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-22 13:20 Carl Spalletta
2003-07-22 18:57 Carl Spalletta
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=20030720003141.GB1085@think \
--to=tytso@mit.edu \
--cc=dbehman@hotmail.com \
--cc=linux-kernel@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