-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 16 Jul 2002, Thunder from the hill wrote:

> Hi,
> 
> On Tue, 16 Jul 2002, Matthias Andree wrote:
> > > or the blockdevice-level snapshots already implemented in Linux..
> > 
> > That would require three atomic steps:
> > 
> > 1. mount read-only, flushing all pending updates
> > 2. take snapshot
> > 3. mount read-write
> > 
> > and then backup the snapshot. A snapshots of a live file system won't
> > do, it can be as inconsistent as it desires -- if your corrupt target is
> > moving or not, dumping it is not of much use.
> 
> Well, couldn't we just kindof lock the file system so that while backing 
> up no writes get through to the real filesystem? This will possibly 
> require a lot of memory (or another space to write to), but it might be 
> done?

But you would want to backup a consistent file system, so when entering
the freeze or snapshot mode, you must flush all pending data in such a
way that the snapshot is consistent (i. e. needs not fsck action
whatsoever).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9NIrfFmbjPHp/pcMRAkAyAJ4wQhTUafOHDrmmA2DGrFKn9NEOHwCdHM3Q
UdlrkGbhUynS86ogxstbdQM=
=vK/f
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/