На Thu, 24 Jan 2008 16:20:15 -0500 Joey Hess <[EMAIL PROTECTED]> записано:
> Alexander GQ Gerasiov wrote: > > lvm update this information every time you change lvm partitioning. > > When you do so, it stores new configuration in backup and moves old > > configuration from backup to archive. On host, where I use lvm > > snapshots for every-day backup, I see many of such archives. > > > > Lets see what is backup files: that's just a _copy_ of metadata, > > which could be used in some rear cases. E.g. you lost all your lvm's > > metadata. Or to restore the same partitioning on new, replaced > > drive. Do we need history for it? Yes (e.g. to restore suddenly > > deleted volume), but lvm tracks enough copies of old metadata in > > archive dir. So keeping them in git don't needed. > > git should automatically notice that the file was renamed from archive > to backup, and only save one copy of the file. May be, but what for do we need to keep them in vcs? lvm already stores every past version there. And every file there should normally have only one revision. > > My question is, what if I deleted my current /etc and used etckeeper > to check out a new copy from git. Would lvm transparently recreate > those lvm files as needed, or would it be better if the new /etc > checkout included them? I don't understand exactly what do you mean. But lvm don't use those files for it's normal work. They are only some backups for admin, to allow him restore some past lvm configuration. If you check out something from vcs lvm would not use this files. -- Best regards, Alexander GQ Gerasiov Contacts: e-mail: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] Homepage: http://gq.net.ru ICQ: 7272757 PGP fingerprint: 0628 ACC7 291A D4AA 6D7D 79B8 0641 D82A E3E3 CE1D
signature.asc
Description: PGP signature
