From: "Xin Zhao" <uszhaoxin@gmail.com>
To: "Bryan Henderson" <hbryan@us.ibm.com>
Cc: "Chris Mason" <chris.mason@oracle.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: how do versioning filesystems take snapshot of opened files?
Date: Tue, 3 Jul 2007 12:31:49 -0400 [thread overview]
Message-ID: <4ae3c140707030931u14119061m5d5dc69834292847@mail.gmail.com> (raw)
In-Reply-To: <OF10F7FD22.6E0117BF-ON8825730D.00597431-8825730D.005A1FBE@us.ibm.com>
That's a good point!
But this sounds hopeless to take a real consistent snapshot from app
perspective unless you shutdown the computer. Right?
Thanks.
On 7/3/07, Bryan Henderson <hbryan@us.ibm.com> wrote:
> > Consistent state means many different things.
>
> And, significantly, open/close has nothing to do with any of them
> (assuming we're talking about the system calls). open/close does not
> identify a transaction; a program may open and close a file multiple times
> the course of making a "single" update. Also, data and metadata updates
> remain buffered at the kernel level after a close. And don't forget that
> a single update may span multiple files.
>
> --
> Bryan Henderson IBM Almaden Research Center
> San Jose CA Filesystems
>
>
next prev parent reply other threads:[~2007-07-03 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 5:28 how do versioning filesystems take snapshot of opened files? Xin Zhao
[not found] ` <778391c50707022236v5157a933qea1994cf4cbce879@mail.gmail.com>
2007-07-03 5:44 ` Xin Zhao
2007-07-03 13:09 ` Chris Mason
2007-07-03 16:12 ` Xin Zhao
2007-07-03 16:35 ` Bryan Henderson
2007-07-03 16:24 ` Bryan Henderson
2007-07-03 16:31 ` Xin Zhao [this message]
2007-07-03 17:04 ` Chris Mason
2007-07-03 17:15 ` Xin Zhao
2007-07-03 17:38 ` Chris Mason
2007-07-03 21:06 ` Bryan Henderson
2007-07-03 21:17 ` Xin Zhao
2007-07-03 22:02 ` Neil Brown
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=4ae3c140707030931u14119061m5d5dc69834292847@mail.gmail.com \
--to=uszhaoxin@gmail.com \
--cc=chris.mason@oracle.com \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@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).