On Monday 07 June 2010 22:24:37 Dale wrote:
Mick wrote:
I am trying to clean up what seems like a remnant of a failed emerge, but
I can delete the directory in question:
# rm -Rf /var/tmp/portage/sys-devel/gcc-4.4.3-
r2/work/gcc-4.4.3/libjava/classpath/resource/gnu/java/locale
rm:
On Mon, 7 Jun 2010 23:46:19 +0200, Alan McKinnon wrote:
Neil is likely correct - filesystem corruption. A quick easy way to
check is to run ls -al starting with the target then going up on
directory in turn. If you start getting lots of ??? in the output,
corruption is almost certain.
Paul's
On 8 June 2010 10:47, Neil Bothwick n...@digimed.co.uk wrote:
On Mon, 7 Jun 2010 23:46:19 +0200, Alan McKinnon wrote:
Neil is likely correct - filesystem corruption. A quick easy way to
check is to run ls -al starting with the target then going up on
directory in turn. If you start getting
On 8 June 2010 18:42, Mick michaelkintz...@gmail.com wrote:
On 8 June 2010 10:47, Neil Bothwick n...@digimed.co.uk wrote:
On Mon, 7 Jun 2010 23:46:19 +0200, Alan McKinnon wrote:
Neil is likely correct - filesystem corruption. A quick easy way to
check is to run ls -al starting with the target
On Tue, Jun 8, 2010 at 2:01 PM, Mick michaelkintz...@gmail.com wrote:
On 8 June 2010 18:42, Mick michaelkintz...@gmail.com wrote:
On 8 June 2010 10:47, Neil Bothwick n...@digimed.co.uk wrote:
On Mon, 7 Jun 2010 23:46:19 +0200, Alan McKinnon wrote:
Neil is likely correct - filesystem
On 8 June 2010 21:10, James Ausmus james.aus...@gmail.com wrote:
On Tue, Jun 8, 2010 at 2:01 PM, Mick michaelkintz...@gmail.com wrote:
To save me from losing it, can you please tell me if your
/var/tmp/portage has such a stale file in there following your emerge
of gcc-4.4.3-r2 ? Surely I
I am trying to clean up what seems like a remnant of a failed emerge, but I
can delete the directory in question:
# rm -Rf /var/tmp/portage/sys-devel/gcc-4.4.3-
r2/work/gcc-4.4.3/libjava/classpath/resource/gnu/java/locale
rm: cannot remove `/var/tmp/portage/sys-devel/gcc-4.4.3-
On Mon, 7 Jun 2010 20:54:36 +0100, Mick wrote:
# rm -Rf /var/tmp/portage/sys-devel/gcc-4.4.3-
r2/work/gcc-4.4.3/libjava/classpath/resource/gnu/java/locale
rm: cannot remove `/var/tmp/portage/sys-devel/gcc-4.4.3-
r2/work/gcc-4.4.3/libjava/classpath/resource/gnu/java/locale':
Directory not
Mick wrote:
I am trying to clean up what seems like a remnant of a failed emerge, but I
can delete the directory in question:
# rm -Rf /var/tmp/portage/sys-devel/gcc-4.4.3-
r2/work/gcc-4.4.3/libjava/classpath/resource/gnu/java/locale
rm: cannot remove `/var/tmp/portage/sys-devel/gcc-4.4.3-
On Monday 07 June 2010 21:24:37 Dale wrote:
Mick wrote:
I am trying to clean up what seems like a remnant of a failed emerge, but
I can delete the directory in question:
# rm -Rf /var/tmp/portage/sys-devel/gcc-4.4.3-
r2/work/gcc-4.4.3/libjava/classpath/resource/gnu/java/locale
rm:
On Mon, Jun 7, 2010 at 2:54 PM, Mick michaelkintz...@gmail.com wrote:
I am trying to clean up what seems like a remnant of a failed emerge, but I
can delete the directory in question:
Maybe try lsof to see if anything is using one of those directories
Mick writes:
I am getting worried now about fs corruption.
I would be, too.
The fs is supposed to be checked at boot time
But only if it was not shut down correctly. To force a complete fsck on
reboot on a file system that looks sane, issue a 'touch /force_fsck'.
Wonko
On Mon, 7 Jun 2010 22:45:57 +0100, Mick wrote:
I am getting worried now about fs corruption. The fs is supposed to be
checked at boot time
Only if it's marked unclean. extN filesystems are only checked every so
many mounts or days. Run fsck with the --force option to force a proper
Mick wrote:
On Monday 07 June 2010 21:24:37 Dale wrote:
Mick wrote:
I am trying to clean up what seems like a remnant of a failed emerge, but
I can delete the directory in question:
# rm -Rf /var/tmp/portage/sys-devel/gcc-4.4.3-
14 matches
Mail list logo