www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Stevenson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-5849) bb-vm3 is experiencing disk problems
Date Fri, 15 Feb 2013 16:49:12 GMT

    [ https://issues.apache.org/jira/browse/INFRA-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579306#comment-13579306
] 

Tony Stevenson commented on INFRA-5849:
---------------------------------------

Andrew, 

Given the high load on all our VM hosts we should probably wait until the new VMware host
arrives in March.  Is that ok with you? 

                
> bb-vm3 is experiencing disk problems
> ------------------------------------
>
>                 Key: INFRA-5849
>                 URL: https://issues.apache.org/jira/browse/INFRA-5849
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Buildbot
>         Environment: bb-vm3 - ubuntu 10.2
>            Reporter: Andrew Rist
>            Priority: Critical
>
> bb-vm3 file system seems to be read only
> >> mv: inter-device move failed: `/tmp/2E4v3zeTnI' to `/home/buildslave29/slave29/openoffice-linux32-snapshot/build/log/unxlngi6.pro.build.html';
unable to remove target: Read-only file system 
> home$ touch me
> touch: cannot touch `me': Read-only file system
> cant write tmp to authenticate sudo
> /dev/sda1              46G   38G  6.0G  87% /
> /dev/sda5             9.2G  1.2G  7.6G  13% /tmp
> console is giving me messages
> EXT4-fs error (device sda1): ext4 lookup: deleted inode referenced: xxxxxxx
> CPU#0 stuck
> CPU#1 stuck
> mounr /root/[proc|sys|dev] failed, no such file or directory
> physical disk of this VM is X5-VMFS  -   1.04TB free 
> add another virtual disk, install ubuntu on that, copy over anything needed
> nothing will mount/unmount/fsck/whatever
> going to need to install a new disk and start again

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message