All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: "Andreas Schäfer" <gentryx@gmx.de>
Cc: reiserfs-list@namesys.com
Subject: Re: somewhat OT query on journalling
Date: Fri, 21 Jul 2006 16:53:54 -0500	[thread overview]
Message-ID: <44C14CF2.4080401@slaphack.com> (raw)
In-Reply-To: <20060721212611.GA13453@wintermute>

Andreas Schäfer wrote:
>> Don't get too excited -- the transactions probably aren't done yet. Without those, no filesystem that claims to journal data is really any better than a filesystem which only journals metadata.  Even once 
>> they are implemented (or even if they are already), applications have to support them directly.
> 
> Actually, I think transactions in a filesystem context are a bit
> different from the transactions you know form databases. Generally

Yes, generally speaking, you're entirely right.  But in the case of 
Reiser4, at least for a single file, you can perform a number of writes 
and declare them a single transaction.

I believe there are some other oddities, such as:  The FS doesn't always 
do the rollback, sometimes it delegates to the app for that, and it may 
be possible to perform transactions on a number of files.  I don't 
believe transactions imply locking, only serialization -- that is, the 
last transaction that goes through is the one that counts, and 
overwrites any transactions that completed before, even if they were 
started after.  So:

Alice opens foo
Alice starts writing
Bob opens foo
Bob starts writing
Alice writes some more
Bob writes more
Bob closes foo
Alice closes foo

Even though Bob opened foo last, and did the last write, Alice was the 
last to close a transaction.  If you want to avoid this situation, you 
use locking.  Locking isn't mandatory, but neither are transactions.

But I could be entirely wrong also.

  reply	other threads:[~2006-07-21 21:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 15:27 somewhat OT query on journalling Payal Rathod
2006-07-19 17:30 ` Toby Thain
2006-07-19 17:30   ` Toby Thain
2006-07-19 19:09     ` David Masover
2006-07-19 19:19 ` David Masover
2006-07-19 20:28 ` Hans Reiser
2006-07-21 12:45   ` Payal Rathod
2006-07-21 18:54     ` David Masover
2006-07-21 21:26       ` Andreas Schäfer
2006-07-21 21:53         ` David Masover [this message]
2006-07-22  0:54           ` Hans Reiser

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=44C14CF2.4080401@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=gentryx@gmx.de \
    --cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.