2 messages in com.perforce.perforce-userMore info: RE: [p4] Problem migrating...| From | Sent On | Attachments |
|---|---|---|
| Doug Palmer | 06 Dec 2001 21:24 | |
| Todd Short | 07 Dec 2001 06:51 |
| Subject: | More info: RE: [p4] Problem migrating to Linux![]() |
|---|---|
| From: | Doug Palmer (dpal...@mahinetworks.com) |
| Date: | 12/06/2001 09:24:35 PM |
| List: | com.perforce.perforce-user |
OK, I did some more checking, and it's not a filesystem limitation. I have a 2.5GB tar file of my depot and it fits just fine. The error happened when db.have grew to 2147483647bytes, which is about 1.99999GB. That's why I thought it might be a filesystem limit. Here's the error message, could I just have a bad checkpoint file?
Recovering from checkpoint.359.gz... Perforce server error: Journal file 'checkpoint.359.gz' replay failed at line 8697767! Database write error on db.have! dbput: db.have: Success Error allocating new node
Doug
-----Original Message----- From: Doug Palmer [mailto:dpalmer at mahinetworks.com] Sent: Thursday, December 06, 2001 9:11 PM To: Perforce-User (E-mail) Subject: [p4] Problem migrating to Linux
I'm testing a migration from NT to Linux. The test system is RedHat 7.2 with ext3 filesystem. Everything was going well until I hit the 2GB file size limit when I was restoring db.have from the checkpoint.
What gives? I thought that the 2GB limit goes away with kernel 2.4. Any advice?
And please don't tell me to use Solaris, that's a discussion for another time.
Doug Palmer MTS, Software Configuration Management Mahi Networks, Inc. (707) 283-1234 dpalmer at mahinetworks.com ... . -- .--. . .-. / ..-. ..
_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user




