On Tue, 3 Jul 2007 01:28:57 -0400
"Xin Zhao" <[email protected]> wrote:
> Hi,
>
>
> If a file is already opened when snapshot command is issued, the file
> itself could be in an inconsistent state already. Before the file is
> closed, maybe part of the file contains old data, the rest contains
> new data.
> How does a versioning filesystem guarantee that the file snapshot is
> in a consistent state in this case?
>
> I googled it but didn't find any answer. Can someone explain it a
> little bit?
It's the same answer as in most filesystem related questions...it
depends ;) Consistent state means many different things. It may mean
that the metadata accurately reflects the space on disk allocated to
the file and that all data for the file is properly on disk (ie from an
fsync).
But, even this is less than useful because very few files on the
filesystem stand alone. Applications spread their state across a
number of files and so consistent means something different to
every application.
Getting a snapshot that is useful with respect to application data
requires help from the application. The app needs to be shutdown or
paused prior to the snapshot and then started up again after the
snapshot is taken.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
