Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Aug 2011 22:54:08 +0200
From:      Roland Smith <>
To:        "Hartmann, O." <>
Cc:        Olivier Smedts <>,,
Subject:   Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
> >> files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398=
> > This file is relatively recent; When I used portsnap yesterday, it wasn=
> > there, and now it is.
> I do a postrmaster on a nearly daily basis. This occured this morning=20
> (German standard time) to me the first time.

I did a portsnap just before my previous mail. It downloaded and extracted =
particular file without problem.

> > Have you fscked the volume that contains /var? If not I suggest you do.=
> > 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=

Another data-point: I'm on 8.2-RELEASE amd64 as well and it doesn't show a
problem. So it could well be a CURRENT specific problem. But I would think
that the filesystem code would be pretty mature by now. Maybe some changes =

> I'll force a fsck as soon as possible. I started the boxes already and=20
> they didn't show up any unclean filesystem so far ...

Since portsnap cannot find the file in question, I assume you have checked
that it existed and that it was a normal file etc?

Could it be a hardware issue? Some time ago I began to have random filesyst=
corruption and lockups. After cleaning out two years worth of dust out of t=
machine in question it now runs fine again.

[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)

Content-Type: application/pgp-signature

Version: GnuPG v2.0.18 (FreeBSD)



Want to link to this message? Use this URL: <>