Date: Thu, 14 Aug 2014 13:53:29 +0700 From: Victor Sudakov <vas@mpeks.tomsk.su> To: freebsd-questions@freebsd.org Subject: Re: Problems with dump and restore Message-ID: <20140814065329.GB64974@admin.sibptus.tomsk.ru> In-Reply-To: <alpine.BSF.2.11.1408121641480.1074@qemg.org> References: <alpine.BSF.2.11.1408121255230.1074@qemg.org> <20140812193419.GB7166@slackbox.erewhon.home> <alpine.BSF.2.11.1408121641480.1074@qemg.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Hamilton-Wright wrote: > > True, but my understanding of snapshots is that it is supposed to > eliminate exactly this problem, no? There is something fishy about 'dump -L'. When I dump a busy mail server and then restore the dumps, I often get the message lile ./CommuniGate/Domains/mail.tomsk.ru/mptdkfe.macnt/account.info: (inode 7206930) not found on tape However, restoring this filesystems has always worked in general, with a few file lost like shown above. If you have SU+J, you cannot use -L at all, 'dump -L' (or mksnap_ffs) will complain. -- Victor Sudakov Tomsk, Russia Russian Barefoot FAQ at http://www.barefooters.ru/barefoot.txt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140814065329.GB64974>