Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On 2011-08-13 12:08, Roland Smith wrote:
On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote:
On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?
Roland
No, it does not.
What I did so far over night:
I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again.
Again failure.
After that it got the ports tree via CVS (make update in /usr/ports).
Everything seems
all right. I tried portsnap again. portsnap compalins about a
non-portsnap-created /usr/ports
and please me to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is generated
by the shell's built-in test command, specifically '[ -r'. It is looking for a
file that was extracted with tar. So the place to look for the bug is IMO
1) the portsnap script itself (differences between 8.2 and 9?)
2) the sh(1)'s built-in test command (ditto)
3) tar (ditto)
When you run 'portsnap fetch' it downloads a tgz archive and unpacks it with
tar(1). What you could try is to comment out the line 'rm ${SNAPSHOTHASH}.tgz'
in portsnap, and test if the tgz file extracts differently using an
8.2-RELEASE tar and the 9-CURRENT tar. If so, that would be a bug!
Roland
Just a me too!. It happens for me on a recently updated 9-current
virtual machine, built with clang.
Regards!
--
Niclas
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On 08/14/11 11:48, Niclas Zeising wrote:
On 2011-08-13 12:08, Roland Smith wrote:
On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote:
On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?
Roland
No, it does not.
What I did so far over night:
I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again.
Again failure.
After that it got the ports tree via CVS (make update in /usr/ports).
Everything seems
all right. I tried portsnap again. portsnap compalins about a
non-portsnap-created /usr/ports
and please me to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is generated
by the shell's built-in test command, specifically '[ -r'. It is looking for a
file that was extracted with tar. So the place to look for the bug is IMO
1) the portsnap script itself (differences between 8.2 and 9?)
2) the sh(1)'s built-in test command (ditto)
3) tar (ditto)
When you run 'portsnap fetch' it downloads a tgz archive and unpacks it with
tar(1). What you could try is to comment out the line 'rm ${SNAPSHOTHASH}.tgz'
in portsnap, and test if the tgz file extracts differently using an
8.2-RELEASE tar and the 9-CURRENT tar. If so, that would be a bug!
Roland
Just a me too!. It happens for me on a recently updated 9-current
virtual machine, built with clang.
Regards!
Just got a notebook, build with the old gcc 4.2 of the system FreeBSD
9.0/amd64 -r224579: portsnap works as expected.
I will build a most recent system on that box (with systems's outdated
gcc 4.2) and I'll report if the problem is still present.
By the way: My boxes of failure are all built with CLANG.
Oliver
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
2011/8/14 Hartmann, O. ohart...@zedat.fu-berlin.de:
On 08/14/11 11:48, Niclas Zeising wrote:
On 2011-08-13 12:08, Roland Smith wrote:
On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote:
On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?
Roland
No, it does not.
What I did so far over night:
I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again.
Again failure.
After that it got the ports tree via CVS (make update in /usr/ports).
Everything seems
all right. I tried portsnap again. portsnap compalins about a
non-portsnap-created /usr/ports
and please me to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is
generated
by the shell's built-in test command, specifically '[ -r'. It is looking
for a
file that was extracted with tar. So the place to look for the bug is IMO
1) the portsnap script itself (differences between 8.2 and 9?)
2) the sh(1)'s built-in test command (ditto)
3) tar (ditto)
When you run 'portsnap fetch' it downloads a tgz archive and unpacks it
with
tar(1). What you could try is to comment out the line 'rm
${SNAPSHOTHASH}.tgz'
in portsnap, and test if the tgz file extracts differently using an
8.2-RELEASE tar and the 9-CURRENT tar. If so, that would be a bug!
Roland
Just a me too!. It happens for me on a recently updated 9-current
virtual machine, built with clang.
Regards!
Just got a notebook, build with the old gcc 4.2 of the system FreeBSD
9.0/amd64 -r224579: portsnap works as expected.
I will build a most recent system on that box (with systems's outdated gcc
4.2) and I'll report if the problem is still present.
By the way: My boxes of failure are all built with CLANG.
Oliver
Trying again today, with my 9.0-BETA1 amd64 box built with clang.
Not the same error, but the same kind when using portsnap extract :
/usr/ports/lang/p5-JavaScript-Value-Escape/
/usr/ports/lang/p5-JavaScript/
/usr/ports/lang/p5-List-MoreUtils/
/usr/ports/lang/p5-Modern-Perl/
/usr/ports/lang/p5-POE-Component-Hailo/
files/b54a58da6d23d31f19a9105f70af03ef797aba8db6bdbc03d6deb72e62011d56.gz
not found -- snapshot corrupt.
This file is not present in /var/db/portsnap/files/.
# ll /var/db/portsnap/files/ | wc -l
22862
This was after removing /var/db/portsnap/files/ and
/var/db/portsnap/t* and a fresh portsnap fetch, on the portsnap5
mirror.
# fetch
http://portsnap5.freebsd.org/s/c9a2c992e8bde0c98309f76a0ecfb00eb76558c7c3dcbd0405a88316b775e66b.tgz
# tar tf c9a2c992e8bde0c98309f76a0ecfb00eb76558c7c3dcbd0405a88316b775e66b.tgz
| grep b54a58
nothing...
I tried on portsnap2 and the file was not present in
c9a2c992e8bde0c98309f76a0ecfb00eb76558c7c3dcbd0405a88316b775e66b.tgz
--
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oliv...@gid0.org - against HTML email vCards X
www: http://www.gid0.org - against proprietary attachments / \
Il y a seulement 10 sortes de gens dans le monde :
ceux qui comprennent le binaire,
et ceux qui ne le comprennent pas.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On Sun Aug 14 11, Niclas Zeising wrote:
On 2011-08-13 12:08, Roland Smith wrote:
On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote:
On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?
Roland
No, it does not.
What I did so far over night:
I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again.
Again failure.
After that it got the ports tree via CVS (make update in /usr/ports).
Everything seems
all right. I tried portsnap again. portsnap compalins about a
non-portsnap-created /usr/ports
and please me to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is
generated
by the shell's built-in test command, specifically '[ -r'. It is looking
for a
file that was extracted with tar. So the place to look for the bug is IMO
1) the portsnap script itself (differences between 8.2 and 9?)
2) the sh(1)'s built-in test command (ditto)
3) tar (ditto)
When you run 'portsnap fetch' it downloads a tgz archive and unpacks it with
tar(1). What you could try is to comment out the line 'rm
${SNAPSHOTHASH}.tgz'
in portsnap, and test if the tgz file extracts differently using an
8.2-RELEASE tar and the 9-CURRENT tar. If so, that would be a bug!
Roland
Just a me too!. It happens for me on a recently updated 9-current
virtual machine, built with clang.
same here:
/usr/ports/databases/gigabase/
/usr/ports/databases/godis/
files/39644d98f9e9b9d9a362cbfc075a996683e8a611a4362d883247c9a2e2fa2658.gz not
found -- snapshot corrupt.
running r224841 on amd64 built with base clang.
Regards!
--
Niclas
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
2011/8/14 Alexander Best arun...@freebsd.org:
On Sun Aug 14 11, Niclas Zeising wrote:
On 2011-08-13 12:08, Roland Smith wrote:
On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote:
On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?
Roland
No, it does not.
What I did so far over night:
I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again.
Again failure.
After that it got the ports tree via CVS (make update in /usr/ports).
Everything seems
all right. I tried portsnap again. portsnap compalins about a
non-portsnap-created /usr/ports
and please me to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is
generated
by the shell's built-in test command, specifically '[ -r'. It is looking
for a
file that was extracted with tar. So the place to look for the bug is IMO
1) the portsnap script itself (differences between 8.2 and 9?)
2) the sh(1)'s built-in test command (ditto)
3) tar (ditto)
When you run 'portsnap fetch' it downloads a tgz archive and unpacks it
with
tar(1). What you could try is to comment out the line 'rm
${SNAPSHOTHASH}.tgz'
in portsnap, and test if the tgz file extracts differently using an
8.2-RELEASE tar and the 9-CURRENT tar. If so, that would be a bug!
Roland
Just a me too!. It happens for me on a recently updated 9-current
virtual machine, built with clang.
same here:
/usr/ports/databases/gigabase/
/usr/ports/databases/godis/
files/39644d98f9e9b9d9a362cbfc075a996683e8a611a4362d883247c9a2e2fa2658.gz not
found -- snapshot corrupt.
running r224841 on amd64 built with base clang.
Aparently fixed with latest HEAD *kernel* :
# svn log -v -r224842
r224842 | rwatson | 2011-08-13 18:03:40 +0200 (sam 13 aoû 2011) | 10 lignes
Chemins modifiés :
M /head/sys/kern/vfs_syscalls.c
When falloc() was broken into separate falloc_noinstall() and finstall(),
a bug was introduced in kern_openat() such that the error from the vnode
open operation was overwritten before it was passed as an argument to
dupfdopen(). This broke operations on /dev/{stdin,stdout,stderr}. Fix
by preserving the original error number across finstall() so that it is
still available.
Approved by:re (kib)
Reported by:cognet
You won't be able to buildworld with the buggy kernel, but you can
buildkernel and reboot on the new kernel. No problems with portsnap
after that (don't know if you have to clean the old portsnap files, I
did it).
--
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oliv...@gid0.org - against HTML email vCards X
www: http://www.gid0.org - against proprietary attachments / \
Il y a seulement 10 sortes de gens dans le monde :
ceux qui comprennent le binaire,
et ceux qui ne le comprennent pas.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On Sun Aug 14 11, Olivier Smedts wrote:
2011/8/14 Alexander Best arun...@freebsd.org:
On Sun Aug 14 11, Niclas Zeising wrote:
On 2011-08-13 12:08, Roland Smith wrote:
On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote:
On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?
Roland
No, it does not.
What I did so far over night:
I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again.
Again failure.
After that it got the ports tree via CVS (make update in /usr/ports).
Everything seems
all right. I tried portsnap again. portsnap compalins about a
non-portsnap-created /usr/ports
and please me to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is
generated
by the shell's built-in test command, specifically '[ -r'. It is looking
for a
file that was extracted with tar. So the place to look for the bug is IMO
1) the portsnap script itself (differences between 8.2 and 9?)
2) the sh(1)'s built-in test command (ditto)
3) tar (ditto)
When you run 'portsnap fetch' it downloads a tgz archive and unpacks it
with
tar(1). What you could try is to comment out the line 'rm
${SNAPSHOTHASH}.tgz'
in portsnap, and test if the tgz file extracts differently using an
8.2-RELEASE tar and the 9-CURRENT tar. If so, that would be a bug!
Roland
Just a me too!. It happens for me on a recently updated 9-current
virtual machine, built with clang.
same here:
/usr/ports/databases/gigabase/
/usr/ports/databases/godis/
files/39644d98f9e9b9d9a362cbfc075a996683e8a611a4362d883247c9a2e2fa2658.gz
not found -- snapshot corrupt.
running r224841 on amd64 built with base clang.
Aparently fixed with latest HEAD *kernel* :
# svn log -v -r224842
r224842 | rwatson | 2011-08-13 18:03:40 +0200 (sam 13 aoû 2011) | 10 lignes
Chemins modifiés :
M /head/sys/kern/vfs_syscalls.c
When falloc() was broken into separate falloc_noinstall() and finstall(),
a bug was introduced in kern_openat() such that the error from the vnode
open operation was overwritten before it was passed as an argument to
dupfdopen(). This broke operations on /dev/{stdin,stdout,stderr}. Fix
by preserving the original error number across finstall() so that it is
still available.
Approved by:re (kib)
Reported by:cognet
You won't be able to buildworld with the buggy kernel, but you can
buildkernel and reboot on the new kernel. No problems with portsnap
after that (don't know if you have to clean the old portsnap files, I
did it).
thanks. switching to a newer revision alone didn't solve the issue. however
after doing
rm -r /var/db/portsnap/files/; rm /var/db/portsnap/t*; portsnap fetch update
everything's back to normal. :)
--
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oliv...@gid0.org - against HTML email vCards X
www: http://www.gid0.org - against proprietary attachments / \
Il y a seulement 10 sortes de gens dans le monde :
ceux qui comprennent le binaire,
et ceux qui ne le comprennent pas.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote: On 08/12/11 22:54, Roland Smith wrote: On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz Does this file actually exist if you extract the snapshot? And are the permissions et cetera OK? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpXSyMn0lIgR.pgp Description: PGP signature
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On 08/13/11 09:26, Roland Smith wrote: On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote: On 08/12/11 22:54, Roland Smith wrote: On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz Does this file actually exist if you extract the snapshot? And are the permissions et cetera OK? Roland No, it does not. What I did so far over night: I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again. Again failure. After that it got the ports tree via CVS (make update in /usr/ports). Everything seems all right. I tried portsnap again. portsnap compalins about a non-portsnap-created /usr/ports and please me to use 'extract'. I do ... but then I run into the very same failure: (portsnap fetch extract:) /usr/ports/devel// /usr/ports/devel/ccdoc/ /usr/ports/devel/ccrtp/ /usr/ports/devel/cdash/ files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt. Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote:
On 08/13/11 09:26, Roland Smith wrote:
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the snapshot? And are the
permissions et cetera OK?
Roland
No, it does not.
What I did so far over night:
I deleted /var/db/portsnap as well as /usr/ports/. Then I tried again.
Again failure.
After that it got the ports tree via CVS (make update in /usr/ports).
Everything seems
all right. I tried portsnap again. portsnap compalins about a
non-portsnap-created /usr/ports
and please me to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is generated
by the shell's built-in test command, specifically '[ -r'. It is looking for a
file that was extracted with tar. So the place to look for the bug is IMO
1) the portsnap script itself (differences between 8.2 and 9?)
2) the sh(1)'s built-in test command (ditto)
3) tar (ditto)
When you run 'portsnap fetch' it downloads a tgz archive and unpacks it with
tar(1). What you could try is to comment out the line 'rm ${SNAPSHOTHASH}.tgz'
in portsnap, and test if the tgz file extracts differently using an
8.2-RELEASE tar and the 9-CURRENT tar. If so, that would be a bug!
Roland
--
R.F.Smith http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
pgpZ0qmATYvWX.pgp
Description: PGP signature
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
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? Regards, Oliver Extracting new files: /usr/ports/GIDs /usr/ports/UIDs /usr/ports/audio/teamspeak3-server/ /usr/ports/audio/xmms-fc/ /usr/ports/cad/admesh/ /usr/ports/databases/postgresql82-server/ /usr/ports/databases/postgresql83-server/ /usr/ports/databases/postgresql84-server/ /usr/ports/databases/postgresql90-server/ /usr/ports/devel/Makefile /usr/ports/devel/cdash/ files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On Fri, 12 Aug 2011 17:46:37 +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? You're using portsnap? What if you try to update per CVS? /usr/ports/devel/cdash/ files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt. I think this last message got a bit de-arranged by quoting. The file with the long name belongs to /usr/ports/devel/cdash/files/ as it seems, but that doesn't exist (at least not on my local ports tree). A cdash port doesn't exist in the whole ports tree. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
2011/8/12 Polytropon free...@edvax.de: On Fri, 12 Aug 2011 17:46:37 +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? You're using portsnap? What if you try to update per CVS? /usr/ports/devel/cdash/ files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt. I think this last message got a bit de-arranged by quoting. The file with the long name belongs to /usr/ports/devel/cdash/files/ as it seems, but that doesn't exist (at least not on my local ports tree). A cdash port doesn't exist in the whole ports tree. No, the file does not belong in /usr/ports/devel/cdash/files/. You should read /var/db/portsnap/files/. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-po...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
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? Nothing wrong with ports. Just csup'd 2 machines and all is fine. Regards, Oliver Extracting new files: /usr/ports/GIDs /usr/ports/UIDs /usr/ports/audio/teamspeak3-server/ /usr/ports/audio/xmms-fc/ /usr/ports/cad/admesh/ /usr/ports/databases/postgresql82-server/ /usr/ports/databases/postgresql83-server/ /usr/ports/databases/postgresql84-server/ /usr/ports/databases/postgresql90-server/ /usr/ports/devel/Makefile /usr/ports/devel/cdash/ files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt. This smacks of either you downloaded a corrupt file or it was corrupted during decompression. If the former others will experience same, if the latter it's either your hardware or your software. Test out gzip on some compressed file you know you've ungzipped before. Overclocking and overheated CPU/RAM, or other forms of intermittent glitches (excessive ripple under load on an aged power supply) can play havoc with decompression programs. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
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'. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpBFFiEast0j.pgp Description: PGP signature
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On Fri, 12 Aug 2011 19:16:11 +0200 Roland Smith articulated: 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'. I get this crap from time to time also. It seems dependent upon which mirror portsnap uses at a given time. It always corrects itself in anywhere from a few hours to a few days. You can also try forcing it to use another mirror. -- Jerry ✌ jerry+f...@seibercom.net Disclaimer: off-list followups get on-list replies or ignored. Do not CC this poster. Please do not ignore the Reply-To header. http://www.catb.org/~esr/faqs/smart-questions.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
2011/8/12 Roland Smith rsm...@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*. # portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found. Fetching snapshot tag from portsnap6.FreeBSD.org... done. Fetching snapshot metadata... done. Fetching snapshot generated at Fri Aug 12 02:12:43 CEST 2011: 2296564b5c42a1560759bece15b4c98074658e52fbed23100% of 63 MB 508 kBps 00m00s Extracting snapshot... done. Verifying snapshot integrity... done. Fetching snapshot tag from portsnap6.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Fri Aug 12 02:12:43 CEST 2011 to Fri Aug 12 19:03:17 CEST 2011. Fetching 3 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Fetching 54 patches. done. Applying patches... done. Fetching 27 new ports or files... done. # portsnap extract [...] /usr/ports/devel/ccache/ /usr/ports/devel// /usr/ports/devel/ccdoc/ /usr/ports/devel/ccrtp/ /usr/ports/devel/cdash/ files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On 08/12/11 19:16, Roland Smith wrote: 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'. Roland That was the first I did ... but it doesn't help. Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On Fri, Aug 12, 2011 at 07:38:06PM +0200, Olivier Smedts wrote: 2011/8/12 Roland Smith rsm...@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. files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz This file is relatively recent; When I used portsnap yesterday, it wasn't there, and now it is. Have you fscked the volume that contains /var? If not I suggest you do. You might be looking at filesystem corruption. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpp11sZlONJS.pgp Description: PGP signature
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
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 Smithrsm...@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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote: 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. I did a portsnap just before my previous mail. It downloaded and extracted the particular file without problem. 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). 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 in VFS? 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 ... 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 filesystem corruption and lockups. After cleaning out two years worth of dust out of the machine in question it now runs fine again. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpsilkrOl7qS.pgp Description: PGP signature
Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.
On 08/12/11 22:54, Roland Smith wrote: On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote: 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. I did a portsnap just before my previous mail. It downloaded and extracted the particular file without problem. 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). 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 in VFS? I have a FreeBSD 8.2-STABLE/amd64 server at my lab, no problems. My workstation, my laptop and my box at home are all FreeBSD 9.0-CURRENT/amd64, recent system (r224803) and they have all without exception this problem. 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 ... 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 filesystem corruption and lockups. After cleaning out two years worth of dust out of the machine in question it now runs fine again. Roland No hardware issue. This hardware issue must have occured on three different systems the same time. An unlikely coincidence. I did a complete fsck. No problems with the filesystem. But the problem remains. Again, I'll delete /var/db/portsnap and if it doesn't help, I'll also delete /usr/ports ... Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
