1 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/temp/logging/unpack: No space left on device |
2 |
* [[ $x -ne 0 && $x -ne ${PORTAGE_SIGPIPE_STATUS:-141} ]] && die "$@" |
3 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/temp/logging/unpack: No space left on device |
4 |
* |
5 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/temp/logging/unpack: No space left on device |
6 |
* If you need support, post the output of `emerge --info '=sys-kernel/gentoo-sources-3.7.10'`, |
7 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/temp/logging/unpack: No space left on device |
8 |
* the complete build log and the output of `emerge -pqv '=sys-kernel/gentoo-sources-3.7.10'`. |
9 |
/usr/lib/portage/bin/isolated-functions.sh: line 217: /var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/.die_hooks: No space left on device |
10 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/temp/logging/unpack: No space left on device |
11 |
* The complete build log is located at '/var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/temp/build.log'. |
12 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/temp/logging/unpack: No space left on device |
13 |
* The ebuild environment file is located at '/var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/temp/environment'. |
14 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/temp/logging/unpack: No space left on device |
15 |
* Working directory: '/var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/work' |
16 |
/usr/lib/portage/bin/isolated-functions.sh: line 273: /var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/temp/logging/unpack: No space left on device |
17 |
* S: '/var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/work/linux-3.7.10-gentoo' |
18 |
Traceback (most recent call last): |
19 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 228, in <module> |
20 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
21 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 225, in ebuild_ipc_main |
22 |
return ebuild_ipc.communicate(args) |
23 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 82, in communicate |
24 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
25 |
File "/usr/lib/portage/pym/portage/locks.py", line 103, in lockfile |
26 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
27 |
File "/usr/lib/portage/pym/portage/__init__.py", line 246, in __call__ |
28 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
29 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/.ipc_lock' |
30 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
31 |
* is known to be triggered by things such as failed variable assignments |
32 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
33 |
* exiting, bash should have displayed an error message above. If bash did |
34 |
* not produce an error message above, it's possible that the ebuild has |
35 |
* called `exit` when it should have called `die` instead. This behavior |
36 |
* may also be triggered by a corrupt bash binary or a hardware problem |
37 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
38 |
* it appears to occur randomly, then it is likely to be triggered by a |
39 |
* hardware problem. If you suspect a hardware problem then you should try |
40 |
* some basic hardware diagnostics such as memtest. Please do not report |
41 |
* this as a bug unless it is consistently reproducible and you are sure |
42 |
* that your bash binary and hardware are functioning properly. |
43 |
/usr/lib/portage/bin/misc-functions.sh: line 1246: /var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/.die_hooks: No space left on device |
44 |
Traceback (most recent call last): |
45 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 228, in <module> |
46 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
47 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 225, in ebuild_ipc_main |
48 |
return ebuild_ipc.communicate(args) |
49 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 82, in communicate |
50 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
51 |
File "/usr/lib/portage/pym/portage/locks.py", line 103, in lockfile |
52 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
53 |
File "/usr/lib/portage/pym/portage/__init__.py", line 246, in __call__ |
54 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
55 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-kernel/gentoo-sources-3.7.10/.ipc_lock' |
56 |
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of |
57 |
* behavior is known to be triggered by things such as failed variable |
58 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
59 |
* Normally, before exiting, bash should have displayed an error message |
60 |
* above. If bash did not produce an error message above, it's possible |
61 |
* that the ebuild has called `exit` when it should have called `die` |
62 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
63 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
64 |
* not reproducible or it appears to occur randomly, then it is likely to |
65 |
* be triggered by a hardware problem. If you suspect a hardware problem |
66 |
* then you should try some basic hardware diagnostics such as memtest. |
67 |
* Please do not report this as a bug unless it is consistently |
68 |
* reproducible and you are sure that your bash binary and hardware are |
69 |
* functioning properly. |
70 |
* Messages for package sys-kernel/gentoo-sources-3.7.10 merged to /tmp/kerncache/gentoo/: |
71 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
72 |
* is known to be triggered by things such as failed variable assignments |
73 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
74 |
* exiting, bash should have displayed an error message above. If bash did |
75 |
* not produce an error message above, it's possible that the ebuild has |
76 |
* called `exit` when it should have called `die` instead. This behavior |
77 |
* may also be triggered by a corrupt bash binary or a hardware problem |
78 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
79 |
* it appears to occur randomly, then it is likely to be triggered by a |
80 |
* hardware problem. If you suspect a hardware problem then you should try |
81 |
* some basic hardware diagnostics such as memtest. Please do not report |
82 |
* this as a bug unless it is consistently reproducible and you are sure |
83 |
* that your bash binary and hardware are functioning properly. |
84 |
|
85 |
|
86 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/tmp/kerncache: filesystem umounted, but mount(8) failed: No space left on device |
87 |
|
88 |
!!! catalyst: Runscript kernel build failed |
89 |
|
90 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//tmp/kerncache failed. |
91 |
!!! catalyst: Killing any pids still running in the chroot |
92 |
Checking for processes running in chroot and killing them. |
93 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/tmp/kerncache: not mounted |
94 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/usr/portage/packages: filesystem umounted, but mount(8) failed: No space left on device |
95 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//tmp/kerncache |
96 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//usr/portage/packages failed. |
97 |
!!! catalyst: Killing any pids still running in the chroot |
98 |
Checking for processes running in chroot and killing them. |
99 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/usr/portage/packages: not mounted |
100 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/dev/pts: filesystem umounted, but mount(8) failed: No space left on device |
101 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//usr/portage/packages |
102 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//dev/pts failed. |
103 |
!!! catalyst: Killing any pids still running in the chroot |
104 |
Checking for processes running in chroot and killing them. |
105 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/dev/pts: not mounted |
106 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/usr/portage/distfiles: filesystem umounted, but mount(8) failed: No space left on device |
107 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//dev/pts |
108 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//usr/portage/distfiles failed. |
109 |
!!! catalyst: Killing any pids still running in the chroot |
110 |
Checking for processes running in chroot and killing them. |
111 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/usr/portage/distfiles: not mounted |
112 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/usr/portage: filesystem umounted, but mount(8) failed: No space left on device |
113 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//usr/portage/distfiles |
114 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//usr/portage failed. |
115 |
!!! catalyst: Killing any pids still running in the chroot |
116 |
Checking for processes running in chroot and killing them. |
117 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/usr/portage: not mounted |
118 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/dev: filesystem umounted, but mount(8) failed: No space left on device |
119 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//usr/portage |
120 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//dev failed. |
121 |
!!! catalyst: Killing any pids still running in the chroot |
122 |
Checking for processes running in chroot and killing them. |
123 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/dev: not mounted |
124 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/proc: filesystem umounted, but mount(8) failed: No space left on device |
125 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//dev |
126 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//proc failed. |
127 |
!!! catalyst: Killing any pids still running in the chroot |
128 |
Checking for processes running in chroot and killing them. |
129 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/proc: not mounted |
130 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/tmp/kerncache: not mounted |
131 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//proc |
132 |
|
133 |
Traceback (most recent call last): |
134 |
File "modules/generic_stage_target.py", line 1492, in build_kernel |
135 |
"Runscript kernel build failed",env=self.env) |
136 |
File "/usr/lib/catalyst/modules/catalyst_support.py", line 539, in cmd |
137 |
raise CatalystError,myexc |
138 |
CatalystError |
139 |
None |
140 |
|
141 |
!!! catalyst: Couldn't umount one or more bind-mounts; aborting for safety. |
142 |
|
143 |
/proc is still mounted; performing auto-bind-umount... !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//tmp/kerncache failed. |
144 |
!!! catalyst: Killing any pids still running in the chroot |
145 |
Checking for processes running in chroot and killing them. |
146 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/tmp/kerncache: not mounted |
147 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/usr/portage: not mounted |
148 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//tmp/kerncache |
149 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//usr/portage failed. |
150 |
!!! catalyst: Killing any pids still running in the chroot |
151 |
Checking for processes running in chroot and killing them. |
152 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/usr/portage: not mounted |
153 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/dev: not mounted |
154 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//usr/portage |
155 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//dev failed. |
156 |
!!! catalyst: Killing any pids still running in the chroot |
157 |
Checking for processes running in chroot and killing them. |
158 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/dev: not mounted |
159 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/proc: not mounted |
160 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//dev |
161 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//proc failed. |
162 |
!!! catalyst: Killing any pids still running in the chroot |
163 |
Checking for processes running in chroot and killing them. |
164 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/proc: not mounted |
165 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618//proc |
166 |
|
167 |
Traceback (most recent call last): |
168 |
File "modules/generic_stage_target.py", line 1290, in run |
169 |
apply(getattr(self,x)) |
170 |
File "modules/generic_stage_target.py", line 1516, in build_kernel |
171 |
self.unbind() |
172 |
File "modules/generic_stage_target.py", line 971, in unbind |
173 |
"Couldn't umount one or more bind-mounts; aborting for safety." |
174 |
CatalystError |
175 |
None |
176 |
|
177 |
!!! catalyst: Couldn't umount one or more bind-mounts; aborting for safety. |
178 |
|
179 |
|
180 |
Traceback (most recent call last): |
181 |
File "modules/generic_stage_target.py", line 623, in mount_safety_check |
182 |
self.unbind() |
183 |
File "modules/generic_stage_target.py", line 971, in unbind |
184 |
"Couldn't umount one or more bind-mounts; aborting for safety." |
185 |
CatalystError |
186 |
None |
187 |
|
188 |
!!! catalyst: Unable to auto-unbind /proc |
189 |
|
190 |
Traceback (most recent call last): |
191 |
File "/usr/lib/catalyst/catalyst", line 214, in build_target |
192 |
mytarget.run() |
193 |
File "modules/generic_stage_target.py", line 1292, in run |
194 |
self.mount_safety_check() |
195 |
File "modules/generic_stage_target.py", line 629, in mount_safety_check |
196 |
raise CatalystError, "Unable to auto-unbind "+x |
197 |
CatalystError |
198 |
!!! catalyst: Error encountered during run of target livecd-stage2 |
199 |
Catalyst aborting.... |
200 |
lockfile does not exist '/var/tmp/catalyst/tmp/default/livecd-stage2-ia64-20130618/.catalyst_lock' |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /tmp/catalyst-auto.27619/log/installcd-stage2-minimal.log |