Closed Bug 620024 Opened 14 years ago Closed 14 years ago

momo-vm-linux-03 failing to clobber properly

Categories

(Mozilla Messaging Graveyard :: Release Engineering, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: standard8, Assigned: gozer)

Details

On its clobber step for Linux comm-central build, momo-vm-linux-03 is saying:

Checking clobber URL: http://build.mozillamessaging.com/clobberer/?master=http%3A%2F%2Fbuild.mozillamessaging.com%2Fbuildbot%2Fproduction%2F&slave=momo-vm-linux-03&builddir=linux-comm-central-build&branch=comm-central&buildername=Linux+comm-central+build
linux_repack_31:Our last clobber date:  2010-12-07 08:07:05
linux_repack_31:Server clobber date:    2010-12-07 08:07:05
linux-comm-central-build:Our last clobber date:  2010-10-15 13:29:23
linux-comm-central-build:Server clobber date:    2010-12-16 15:20:41
linux-comm-central-build:Server is forcing a clobber, initiated by bugzilla@standard8.plus.com
linux-comm-central-build:Clobbering...
Skipping tools
Removing build/
Couldn't clobber properly, bailing out.
program finished with exit code 1
elapsedTime=0.349391
Filesystem corruption for sure, needs fsck'ing
Assignee: nobody → gozer
gozer: I'm starting to wonder whether it's worth using ext2 for the small speed improvement over ext3 as we have seen instances of filesystem corruption a number of times.
fsck'ed and fully clobbered
(In reply to comment #2)
> gozer: I'm starting to wonder whether it's worth using ext2 for the small speed
> improvement over ext3 as we have seen instances of filesystem corruption a
> number of times.

We sure can switch a few of them over to ext3 and compare.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.