[ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
bapt at freebsd.org
Fri Mar 25 15:41:55 UTC 2011
2011/3/25 Pietro Cerutti <gahr at freebsd.org>:
> On 2011-Mar-25, 15:03, Julien Laffaye wrote:
>> >>> What about DB corruption/loss? Do you keep the /var/db/pkg/<package>/xxx
>> >>> files even with pkgng and only use the DB as a way to speed up some work
>> >>> (so
>> >>> the DB corruption just requires to run pkg2ng), or are you lost of the DB
>> >>> is
>> >>> lost?
>> >> Nothing is done about DB corruption/loss, I am not sure we need to do
>> >> something.
>> >> Maybe.
>> > I would say "for sure". Info: In Solaris 10 sqlite is used for the service
>> > managenemt framework (SMF). It is possible that the DB is corrupt in some
>> > bad situations. In this case you have to rebuild the DB (script provided,
>> > been there, had to use it).
>> If sqlite is properly used with transactions, it is very hard to
>> corrupt the database. But if hardware lies to us and say that the data
>> is on disk whereas it isnt... what can we do?
>> Another potential problem is fsync(), but if it is broken on FreeBSD
>> we want to fix it!
>> BTW, the goal is to only have the database and not the flat files.
>> If you are paranoid about power outage, use something like zfs snapshots...
> No need to look for strange scenarios, I'm surely going to sudo rm -f the file
> more sooner than later, so... maybe just save a copy?
> Pietro Cerutti
> The FreeBSD Project
> gahr at FreeBSD.org
> PGP Public Key:
I think we can provide a periodic script activable by users (I let
other decide if it has to be activated by default or not) that does a
pkg backup /path/to/file/backup
and xz it.
because copying can be a huge.
40Mo for the database here, corresponding to 70Mo in the old format
and to 600 packages. the dump xzed is only 3Mo
More information about the freebsd-current