On May 04, 2007, at 03:52:03, David Greaves wrote:
Kyle Moffett wrote:
On May 03, 2007, at 11:10:47, Pavel Machek wrote:
What happens if you try to boot and filesystems are frozen from
previous run?
If you're just doing a fresh boot then the filesystem is already
clean due to the dm freeze and so it mounts up normally. All you
need to do then is have a little startup script which purges the
saved image before you fsck or remount things read-write since
either case means the image is no longer safe to resume.
Wouldn't it be better if freeze wrote a freeze-ID to the fs and
returned it? This would naturally be kept in the image and a UUID
mismatch would be detectable - seems safer and more flexible than
'a script'.
"This isn't the freeze you're looking for, move along"
Possibly, but I was referring to the _current_ behavior of the device-
mapper freezing. While perhaps not ideal, it's currently very easily
usable.
Cheers,
Kyle Moffett
-
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]