| Date: | Tue, 25 Apr 2006 23:56:45 +0300 |
| From: | Diomidis Spinellis <dds@aueb.gr> |
| Organization: | Athens University of Economics and Business |
| User-Agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060404 SeaMonkey/1.0.1 |
| MIME-Version: | 1.0 |
| Newsgroups: | comp.lang.perl.misc |
| Subject: | Re: ideas to salvage corrupt tie()ed DB_File file? |
| References: | <1145937788.192476.284130@t31g2000cwb.googlegroups.com> <e2kf3s$4ac$1@volcano1.grnet.gr> <1145987798.021490.124470@t31g2000cwb.googlegroups.com> <4b778qFvuau8U2@news.dfncis.de> |
| In-Reply-To: | <4b778qFvuau8U2@news.dfncis.de> |
| Content-Type: | text/plain; charset=ISO-8859-7; format=flowed |
| Content-Transfer-Encoding: | 7bit |
Anno Siegel wrote: > botfood <botfood@yahoo.com> wrote in comp.lang.perl.misc: >> Diomidis Spinellis wrote: > > [try db_dump] > > If the DB is damaged, I'm afraid db_dump will also reject it. Then > again, it's worth a try. It may be more explicit about what is wrong. db_dump has two options for recovering damaged files: -r Salvage data from a possibly corrupt file. -R Aggressively salvage data from a possibly corrupt file. The -R flag differs from the -r option in that it will return all possible data from the file at the risk of also returning already deleted or otherwise nonsensical items. Data dumped in this fashion will almost certainly have to be edited by hand or other means before the data is ready for reload into another database -- Diomidis Spinellis Code Quality: The Open Source Perspective (Addison-Wesley 2006) http://www.spinellis.gr/codequality
Unless otherwise expressly stated, all original material on this page created by Diomidis Spinellis is licensed under a Creative Commons Attribution-Share Alike 3.0 Greece License.