X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7AD66.1DA68B37@onstor-exch02.onstor.net>; Tue, 12 Jun 2007 18:54:09 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7AD66.1DA68B37"
Content-class: urn:content-classes:message
Subject: Perforce back online - Was: RE: something wrong with p4
Date: Tue, 12 Jun 2007 18:54:09 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D26A@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+58=
X-Priority: 1
Priority: Urgent
Importance: high
References: <BB375AF679D4A34E9CA8DFA650E2B04E02EB2EA7@onstor-exch02.onstor.net>
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Ken Renshaw" <ken.renshaw@onstor.com>,
	"Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"Larry Scheer" <larry.scheer@onstor.com>
Cc: "dl-Engineering" <dl-engineering@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7AD66.1DA68B37
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

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/...



------_=_NextPart_001_01C7AD66.1DA68B37
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>Perforce back online - Was: RE: something wrong with p4</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>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.<BR>
<BR>
For the curious, here's what transpired:<BR>
<BR>
-Chris informed me that Perforce was evidently hanging for her<BR>
<BR>
-I logged into the server, saw a p4 child process taking up 100's of<BR>
megabytes ( unusual ), and restarted p4d which should have cleaned it up =
w/o client hiccups<BR>
<BR>
-p4d restarted, and Chris let me know she could then access it<BR>
<BR>
-Larry and Max both instantly alerted me to client side errors talking =
ominously<BR>
of db files, so I decided to stop the presses before things got =
worse<BR>
and verify we didn't have any real problems.<BR>
<BR>
-I ran p4 verify on the entire depot, verified no errors, verified the =
current journals and checkpoint files were good, and then restarted =
Perforce<BR>
<BR>
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.<BR>
<BR>
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.<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Ken Renshaw<BR>
Sent: Tue 6/12/2007 4:32 PM<BR>
To: Maxim Kozlovsky; Larry Scheer<BR>
Cc: dl-Engineering<BR>
Subject: Re: something wrong with p4<BR>
<BR>
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.<BR>
<BR>
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.<BR>
<BR>
I'll send out an info email once I've found something and have taken =
action.<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Maxim Kozlovsky<BR>
To: Ken Renshaw; Larry Scheer<BR>
Sent: Tue Jun 12 16:13:03 2007<BR>
Subject: something wrong with p4<BR>
<BR>
Getting this message when trying to sync //depot/cougar:<BR>
<BR>
<BR>
[maximk@compile2 cg2]$ p4 sync<BR>
Date 2007/06/12 16:09:38:<BR>
Operation: user-sync<BR>
Operation 'dbscan' failed.<BR>
Database scan error on db.rev!<BR>
dbscan: db.rev: No child processes<BR>
Corrupt tree<BR>
<BR>
<BR>
[maximk@compile2 cg2]$ p4 client -o<BR>
# A Perforce Client Specification.<BR>
#<BR>
#&nbsp; Client:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The client name.<BR>
#&nbsp; Update:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The date this =
specification was last modified.<BR>
#&nbsp; Access:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The date this client was =
last used in any way.<BR>
#&nbsp; Owner:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The user who created =
this client.<BR>
#&nbsp; Host:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If set, =
restricts access to the named host.<BR>
#&nbsp; Description: A short description of the client (optional).<BR>
#&nbsp; Root:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The base =
directory of the client workspace.<BR>
#&nbsp; AltRoots:&nbsp;&nbsp;&nbsp; Up to two alternate client workspace =
roots.<BR>
#&nbsp; Options:&nbsp;&nbsp;&nbsp;&nbsp; Client options:<BR>
#&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [no]allwrite =
[no]clobber [no]compress<BR>
#&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [un]locked =
[no]modtime [no]rmdir<BR>
#&nbsp; LineEnd:&nbsp;&nbsp;&nbsp;&nbsp; Text file line endings on =
client: local/unix/mac/win/share.<BR>
#&nbsp; View:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Lines to map =
depot files into the client workspace.<BR>
#<BR>
# Use 'p4 help client' to see more about client views and options.<BR>
<BR>
Client: maximk-6<BR>
<BR>
Update: 2007/06/12 16:06:24<BR>
<BR>
Access: 2007/06/12 16:06:24<BR>
<BR>
Owner:&nbsp; maximk<BR>
<BR>
Host:&nbsp;&nbsp; compile2.onstor.net<BR>
<BR>
Description:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Created by maximk.<BR>
<BR>
Root:&nbsp;&nbsp; /homes/maximk<BR>
<BR>
Options:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; noallwrite noclobber =
nocompress unlocked nomodtime normdir<BR>
<BR>
LineEnd:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; unix<BR>
<BR>
View:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; //depot/cougar/... =
//maximk-6/cg2/...<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7AD66.1DA68B37--
