Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/go: 'go build' output mysterious when disk is full #3802

Closed
gopherbot opened this issue Jul 5, 2012 · 7 comments
Closed

cmd/go: 'go build' output mysterious when disk is full #3802

gopherbot opened this issue Jul 5, 2012 · 7 comments
Milestone

Comments

@gopherbot
Copy link

by elimisteve:

Before filing a bug, please check whether it has been fixed since the
latest release. Search the issue tracker and check that you're running the
latest version of Go:

Run "go version" and compare against
http://golang.org/doc/devel/release.html  If a newer version of Go exists,
install it and retry what you did to reproduce the problem.

Thanks.

What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.

1. Run 'go build program_name.go' with a full hard drive
2. See random errors

What is the expected output?
None

What do you see instead?

$ go build ptm-gobot.go 
# command-line-arguments
compress/gzip.NewReader: write error: No such file or directory

$ go build ptm-gobot.go 
# command-line-arguments
reflect.(*ptrType).Kind: write error: No such file or directory

$ rm bigfile1 bigfile2

$ go build ptm-gobot.go
$ 

(Notice it built correctly the last time)

Which compiler are you using (5g, 6g, 8g, gccgo)?
5g

Which operating system are you using?
Ubuntu 12.04 on an ARM chip (EC2 AMI ID: ami-aef328c7)

$ cat /proc/cpuinfo 
Processor       : ARMv7 Processor rev 0 (v7l)
processor       : 0
BogoMIPS        : 276.48

Features        : swp half thumb fastmult vfp edsp neon vfpv3 tls 
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xc09
CPU revision    : 0

Hardware        : Highbank
Revision        : 0000
Serial          : 0000000000000000


Which version are you using?  (run 'go version')
go version go1.0.2

Please provide any additional information below.

I love Go :-)
@gopherbot
Copy link
Author

Comment 1 by elimisteve:

I should add that 'df -h' showed 1.2 megs remaining when I was getting the problem. 
After deleting a couple files, freeing space, the build then worked.  (Just wanted you
to know it's not a totally random guess confusing correlation with causation by blaming
this issue on a lack of disk space.)

@minux
Copy link
Member

minux commented Jul 5, 2012

Comment 2:

it is not random error.
it is the way ld outputs error messages.
to facilitate debugging, ld outputs the current processing symbol when encountered error;
and unfortunately, the current symbol is irrelevant for this kind of error.

@rsc
Copy link
Contributor

rsc commented Sep 12, 2012

Comment 4:

It should at least print the correct error. See also issue #2705.

Labels changed: added priority-later, removed priority-triage.

Status changed to Accepted.

@rsc
Copy link
Contributor

rsc commented Sep 12, 2012

Comment 5:

Labels changed: added go1.1.

@rsc
Copy link
Contributor

rsc commented Dec 10, 2012

Comment 6:

Labels changed: added size-m.

@davecheney
Copy link
Contributor

Comment 7:

State of play at rev 8bbc0bdf832e+
installing these packages with 'go test -i' will speed future tests.
/tmp: write failed, filesystem is full
/tmp: write failed, filesystem is full
# go/types
pack: write error: No space left on device
# text/tabwriter
pack: write error: No space left on device

@rsc
Copy link
Contributor

rsc commented Jan 31, 2013

Comment 8:

This issue was closed by revision 592b480.

Status changed to Fixed.

@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants