Closed Bug 736809 Opened 10 years ago Closed 10 years ago
Bring up cb-seamonkey-linux-01 again
Ok, I was getting errors during clobberer so I logged into cb-seamonkey-linux-01, then I logged in and tried deleting that directory, my terminal locked up so I closed it and reconnected. After reconnecting I got errors deleting anything with "Read Only Filesystem" yet mount -v showed all as "rw". So I tried a reboot, and the system has yet to come back up. This is on our parallels server and other active VMs seem fine. When you bring it up, can you please run a chkdisk across all (physical) mounts for sanity?
It is going to take a while to repair /build.
(In reply to Phong Tran [:phong] from comment #1) > It is going to take a while to repair /build. To be clear, much of /builds can just be dropped if its faster and easier, with some exceptions... /builds/slave/buildbot.tac /builds/slave/info/* /builds/hg-shared * /builds/hg-shared/* can go /builds/tmp * /builds/tmp/* can go /builds/ccache * /builds/ccache/* can go If it is far easier to just let the recovery run that is fine by me.
This VM is back online.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
V.Fixed, per bug 736754 comment 3.
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.