Closed
Bug 571300
Opened 16 years ago
Closed 16 years ago
Run fsck against tinderbox.m.o after last disk increase
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: jabba)
References
Details
(Whiteboard: [buildduty])
On bug 569311 we expanded the capacity of tinderbox.m.o but we finished the downtime without being able to run one last fsck after we reboot it.
We will need to schedule a downtime for running which could take several hours.
IT can we schedule this with your regular Thursday evening downtime?
Maybe we can add bug 571276 into the same downtime.
Will you need a releng to be around?
Updated•16 years ago
|
Assignee: server-ops → jdow
Component: Server Operations: Tinderbox Maintenance → Server Operations
Updated•16 years ago
|
Flags: needs-downtime+
Comment 1•16 years ago
|
||
I'm on buildduty this week, and Thursday evening WFM if the timing is also good for IT.
| Assignee | ||
Comment 2•16 years ago
|
||
We've decided that starting this end of day on Friday would be the best time to do it. I'd like to go ahead and say that everything will be back online Saturday morning, but since there isn't really a way to be sure how long this will take, things could be back online much earlier than that, but I'd say Saturday morning will be a fair worst case time.
Updated•16 years ago
|
Whiteboard: [buildduty]
| Assignee | ||
Comment 3•16 years ago
|
||
The file system check completed successfully without any errors.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•