Date: Sat, 26 May 2007 15:25:07 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Svein Halvor Halvorsen <svein.h@lvor.halvorsen.cc> Cc: questions@freebsd.org Subject: Re: Restore UFS snapshot Message-ID: <44odk7fkvg.fsf@Lowell-Desk.lan> In-Reply-To: <465884E3.5000500@lvor.halvorsen.cc> (Svein Halvor Halvorsen's message of "Sat\, 26 May 2007 21\:05\:07 %2B0200") References: <465864F4.7060500@lvor.halvorsen.cc> <20070526180336.GB34660@slackbox.xs4all.nl> <465884E3.5000500@lvor.halvorsen.cc>
next in thread | previous in thread | raw e-mail | index | archive | help
Svein Halvor Halvorsen <svein.h@lvor.halvorsen.cc> writes: > This is also beyond the point, although I appreciate that you > suggest alternative ways to meet my objectives. dump/restore would > also require additional disk space. Not as elegant as your idea, but you can always dump from the snapshot and restore back on the filesystem. You can't use a "pristine" restore(8), and you need the extra space on the same filesystem, but it will work. Your basic idea seems quite workable as far as I can see, so it would be a Simple Matter of Programming to get it to work. [Note that since the copy-on-write mapping only goes one way, the code to do this will have to walk the whole snapshot filesystem, rebuilding inode status (and cleaning up ones that didn't exist in the snapshot) as it goes. A fair amount of work, even if nothing is tricky in theory.] Be well.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44odk7fkvg.fsf>