Hello, Steve
thank you for a clear explanation.
For example, there are four extents to truncate in a
file. Maybe two transacions (each transaction for two
extents deletion) will occur.
If there is a crash in the middle of two transactions
(the one : incore log was logged to disk log, and the
other : incore log was not logged to disk log),
doesn't the other work?
I mean that the one worked, and the other didn't work.
How can I understand this?
--- Steve Lord <lord@xxxxxxx> wrote:
> On Mon, 2003-07-14 at 06:50, jin hee park wrote:
> > Hello~
> >
> > I have a question about transaction in XFS.
> >
> > Are transactions (which are chained using
> > xfs_trans_dup function) atomic?
> > I wonder that such transactions are like one
> > transacion idea(all or nothing).
> > please, let me know..
> >
> > thank you.
> > - JinHee
> >
>
> These transactions are not atomic, each one records
> sufficient
> information to rebuild a consistent filesystem after
> a crash.
>
> An example use of chained transactions is deleting
> extents in a
> file, the amount of log space this needs is
> unbounded - a function
> of the number of extents in the file. We cannot do
> the whole
> sequence in one transaction, so we use a chain of
> them.
>
> Steve
>
>
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
|