X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7AD71.FE4D9E75@onstor-exch02.onstor.net>; Tue, 12 Jun 2007 20:19:11 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Perforce back online - Was: RE: something wrong with p4
Date: Tue, 12 Jun 2007 20:19:11 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E03E9A1C5@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E041BFBB7@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Perforce back online - Was: RE: something wrong with p4
Thread-Index: AcetRzobYTrrYRv3R0iUUQidxy+8kAAArkqFAAai+58AA0IhEAAAFAeA
From: "Chris Vandever" <chris.vandever@onstor.com>
To: "Brian DeForest" <brian.deforest@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>

Perfect timing, I just completed my check-in, #24245.  I'll update the
defect in the morning.

ChrisV

-----Original Message-----
From: Brian DeForest=20
Sent: Tuesday, June 12, 2007 9:18 PM
To: Chris Vandever; Andy Sharp
Subject: FW: Perforce back online - Was: RE: something wrong with p4
Importance: High

Chris, please let me know when you're done checking in tonight or Weds.
morning.

Andy, please let me know if you plan to checkin any code today or Weds.
morning.

-----Original Message-----
From: Ken Renshaw=20
Sent: Tuesday, June 12, 2007 7:54 PM
To: Ken Renshaw; Maxim Kozlovsky; Larry Scheer
Cc: dl-Engineering
Subject: Perforce back online - Was: RE: something wrong with p4
Importance: High

Good evening all, Perforce seems to have settled down now. Please
continue your operations as usual and let me know ASAP if you get any
client-side errors while doing so.

For the curious, here's what transpired:

-Chris informed me that Perforce was evidently hanging for her

-I logged into the server, saw a p4 child process taking up 100's of
megabytes ( unusual ), and restarted p4d which should have cleaned it up
w/o client hiccups

-p4d restarted, and Chris let me know she could then access it

-Larry and Max both instantly alerted me to client side errors talking
ominously
of db files, so I decided to stop the presses before things got worse
and verify we didn't have any real problems.

-I ran p4 verify on the entire depot, verified no errors, verified the
current journals and checkpoint files were good, and then restarted
Perforce

We've seen some rampant p4 children on the server before, and it's not
possible to tie a given thread to the client and operation it was
performing at the time of the crash. Unfortunately, Perforce logs the
client events and process events separately so you can't correlate them.

Thanks, let me know if there are any more issues. I had a checkin ready
to go so I tested the system, no errors, so please have at it.=20

-Ken


-----Original Message-----
From: Ken Renshaw
Sent: Tue 6/12/2007 4:32 PM
To: Maxim Kozlovsky; Larry Scheer
Cc: dl-Engineering
Subject: Re: something wrong with p4
=20
I've pulled the ebrake on Perforce after getting sight of a couple
database issues. I am going to run a complete scan of the depot and
hopefully don't need to rebuild anything. If so the journal and
checkpoint files are there and intact.

This is going to take a while....please keep your perforce workspaces in
their current states and everything should sync back up once I'm
finished.

I'll send out an info email once I've found something and have taken
action.

Thanks,

-Ken

=20

-----Original Message-----
From: Maxim Kozlovsky
To: Ken Renshaw; Larry Scheer
Sent: Tue Jun 12 16:13:03 2007
Subject: something wrong with p4

Getting this message when trying to sync //depot/cougar:


[maximk@compile2 cg2]$ p4 sync
Date 2007/06/12 16:09:38:
Operation: user-sync
Operation 'dbscan' failed.
Database scan error on db.rev!
dbscan: db.rev: No child processes
Corrupt tree


[maximk@compile2 cg2]$ p4 client -o
# A Perforce Client Specification.
#
#  Client:      The client name.
#  Update:      The date this specification was last modified.
#  Access:      The date this client was last used in any way.
#  Owner:       The user who created this client.
#  Host:        If set, restricts access to the named host.
#  Description: A short description of the client (optional).
#  Root:        The base directory of the client workspace.
#  AltRoots:    Up to two alternate client workspace roots.
#  Options:     Client options:
#                      [no]allwrite [no]clobber [no]compress
#                      [un]locked [no]modtime [no]rmdir
#  LineEnd:     Text file line endings on client:
local/unix/mac/win/share.
#  View:        Lines to map depot files into the client workspace.
#
# Use 'p4 help client' to see more about client views and options.

Client: maximk-6

Update: 2007/06/12 16:06:24

Access: 2007/06/12 16:06:24

Owner:  maximk

Host:   compile2.onstor.net

Description:
        Created by maximk.

Root:   /homes/maximk

Options:        noallwrite noclobber nocompress unlocked nomodtime
normdir

LineEnd:        unix

View:
        //depot/cougar/... //maximk-6/cg2/...


