Date: Fri, 12 Aug 2011 20:44:07 +0200 From: "Hartmann, O." <ohartman@zedat.fu-berlin.de> To: Roland Smith <rsmith@xs4all.nl> Cc: Olivier Smedts <olivier@gid0.org>, freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Subject: Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt. Message-ID: <4E457477.4060400@zedat.fu-berlin.de> In-Reply-To: <20110812182108.GA90173@slackbox.erewhon.net> References: <4E454ADD.1020201@zedat.fu-berlin.de> <20110812171611.GA88850@slackbox.erewhon.net> <CABzXLYP6bTskimizXcNLuq%2BDKZBszTWy2d7nbqff4PR8iNGYkg@mail.gmail.com> <20110812182108.GA90173@slackbox.erewhon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/12/11 20:21, Roland Smith wrote: > On Fri, Aug 12, 2011 at 07:38:06PM +0200, Olivier Smedts wrote: >> 2011/8/12 Roland Smith<rsmith@xs4all.nl>: >>> On Fri, Aug 12, 2011 at 05:46:37PM +0200, Hartmann, O. wrote: >>>> Since today, I can not update my ports tree due to this error as follows. >>>> This happens on all boxes running FreeBSD, the version of the OS (FBSD >>>> 8.2/9.0) doesn't >>>> matter. What's up with the ports collection? >>> Probably nothing. >>> >>>> files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not >>>> found -- snapshot corrupt. >>> This looks like a portsnap error. Remove everything in /var/db/portsnap, and >>> run 'portsnap fetch extract'. >> Same error here and after removing all files in /var/db/portsnap/ >> except pub.ssl and serverlist*. > Did you clean out the files subdirectory as well? Try and remove > /var/db/portsnap completely. I did ... I figured out that the files folder was populated with 90MB and > 22000 files. I checked that after the error occured and then killed the whole postsnap folder ... > >> files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz > This file is relatively recent; When I used portsnap yesterday, it wasn't > there, and now it is. I do a postrmaster on a nearly daily basis. This occured this morning (German standard time) to me the first time. > > Have you fscked the volume that contains /var? If not I suggest you do. You > might be looking at filesystem corruption. No I did not. If this is a inconsistent filesystem (I thought about this also), then it has occured on ALL(!) FreeBSD 9.0-CURRENT/amd64 boxes over night (this i why I thought about the filesystem, since the FreeBSD 8.2/amd64-boxes do not show this problem as I mentioned at the start of the post, my mistake). I'll force a fsck as soon as possible. I started the boxes already and they didn't show up any unclean filesystem so far ... Oliver > > Roland
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E457477.4060400>