Date: Fri, 15 May 2015 19:18:20 +0530 From: Avinash Sonawane <rootkea@gmail.com> To: andrew clarke <mail@ozzmosis.com> Cc: freebsd-questions@freebsd.org Subject: Re: portsnap fetch : "snapshot is corrupt" Message-ID: <CAJ9BSW-qK3MOsM8KvpjN-mS7oOFLkO9y%2BZC_K5PJfsd8J58NUw@mail.gmail.com> In-Reply-To: <20150515013141.GB78765@ozzmosis.com> References: <CAJ9BSW9680J%2Bk_qi4_7mz2XE5s2CDi0KxkpOFhrJ4QVG61gkoA@mail.gmail.com> <20150515013141.GB78765@ozzmosis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 15, 2015 at 7:01 AM, andrew clarke <mail@ozzmosis.com> wrote: > On Thu 2015-05-14 20:13:53 UTC+0530, Avinash Sonawane (rootkea@gmail.com) wrote: > >> Hello! >> >> I am using FreeBSD 10.1 RELEASE >> >> Whenever I try to fetch the portsnap it says "snapshot is corrupt". I >> rmed `/var/db/portsnap/*` to start from fresh but then too when I >> issue `portsnap fetch` it says the same. >> >> Here is the complete error message : http://pastebin.com/AiLn8QdE >> >> Anybody has any idea how do I get that missing gz? > > I've noticed this happen in the past on the odd occasion. I ruled out > hardware error on my machine and put it down to some sort of > corruption (or more likely syncronisation problem) with the snapshot > server(s). If I waited a while (a few hours) then re-ran portsnap the > errors went away. Same here. Now I can fetch the portsnap without any "sync" errors. But from browsing the web and from the mailing list archives I found this same problem to be quite frequent and having the only apparent solution "just to wait few hours" Is this specific issue is bound to happen? I mean it seems as if community has adjusted with it. Is this "sync" issue is inherent in portsnap design? I am sorry but I am new to BSD world (Just completed a week!) so have no idea how things work here. Thank you. Avinash Sonawane (RootKea) PICT, Pune http://rootkea.wordpress.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ9BSW-qK3MOsM8KvpjN-mS7oOFLkO9y%2BZC_K5PJfsd8J58NUw>