#134135 CVS lock file

closed
Travis West
9
2009-03-26
2009-03-11
Will Shackleford
No

I am trying to update CVS for the moast project.
It was working until yesterday.

Since yesterday I have been getting:

cvs update: Updating .
cvs update: failed to create lock directory for `/cvsroot/moast/devel' (/cvsroot/moast/devel/#cvs.lock): Read-only file system
cvs update: failed to obtain dir lock in repository `/cvsroot/moast/devel'
cvs [update aborted]: read lock failed - giving up

Discussion

  • Jacob Moorman
    Jacob Moorman
    2009-03-11

    Please note the following Site Status updates on this known issue:

    Original:
    http://apps.sourceforge.net/wordpress/sourceforge/2009/03/10/2009-03-10-service-cvs-unplanned-downtime/

    Latest update:
    http://apps.sourceforge.net/wordpress/sourceforge/2009/03/11/2009-03-10-service-cvs-unplanned-downtime-update/

    The infrastructure upgrades we have made around the CVS service last year
    have made substantial uptime gains for the service and have helped to
    safeguard data. That said, the underlying design of CVS is a limiting
    factor (CVS's network protocol and data storage are both very limiting),
    and you would best be served by moving to a more modern SCM platform if
    high availability is one of your needs. We currently offer Git and
    Subversion (Subversion has a CVS-like command structure), and will soon
    be
    expanding our offering to include Mercurial and Bazaar as well. Our team
    will be glad to support your ongoing use of CVS, or to assist you in
    migrating to an alternate SCM platform.

    Please add a comment here if you have follow-up questions or concerns.

    Jacob Moorman
    Director of Operations, SourceForge.net

     
  • Jacob Moorman
    Jacob Moorman
    2009-03-11

    • assigned_to: nobody --> sog
    • status: open --> pending
     
  • Travis West
    Travis West
    2009-03-11

    • assigned_to: sog --> travis-w
    • status: pending --> open
     
  • Travis West
    Travis West
    2009-03-11

    Greetings,

    This is an initial response the SourceForge.net team uses to let you know how this Support Request will be handled. Please read the entirety of this comment before taking any further action; information enclosed in this comment will help you to ensure that you have an excellent support experience.

    The SourceForge.net team takes all reported issues seriously; we will work to provide you a complete, accurate, and timely response to your inquiry. Information about our support policies and procedures may be found here:
    https://sourceforge.net/docs/C01

    ABOUT THIS ISSUE: Based on the initial review of this request, we have determined that this issue will be considered to have Moderate Priority. Issues within this category typically include service questions, usage problems, system issues, statistics, and specialized requests (such as those requiring significant administrative overview, or which require the development of a custom solution). A description of our issue priorities may be found here:
    https://sourceforge.net/docs/C01#issue_priorities

    TRIAGE PROCESS: The initial review of this issue has resulted in a member of the SourceForge.net staff determining who should process this issue, and a change in the Priority, Summary, Assignee, Group and Category settings for this request.

    WHAT TO EXPECT: Issues of this nature will typically be reviewed again by the assigned member of the SourceForge.net team within 5 business days (the SourceForge.net team works at least Monday through Friday, 9am to 5pm Pacific, excepting holidays). Within our next response, we will typically request additional information about the problem you have reported, or provide you specific troubleshooting instructions. We appreciate your patience as we make our next review of and response to this request.

    INQUIRING ABOUT THE STATUS OF THIS ISSUE: Should you have questions or concerns regarding the status of this issue, simply add a comment to this support request. All comments you post to this support request will be received by the SourceForge.net team member who has been assigned this issue. Please do not submit a second support request about this issue (add a comment to this request instead), and do not attempt to contact the assignee of this request via email; all additional information or comments about this request should be posted as a comment to this request.

    Cheers!,

    SourceForge.net Support

     
  • Travis West
    Travis West
    2009-03-11

    • priority: 5 --> 9
    • status: open --> pending
     
  • Travis West
    Travis West
    2009-03-11

    Please note the following Site Status updates on this known issue:

    Original:
    http://apps.sourceforge.net/wordpress/sourceforge/2009/03/10/2009-03-10-service-cvs-unplanned-downtime/

    Latest update:
    http://apps.sourceforge.net/wordpress/sourceforge/2009/03/11/2009-03-10-service-cvs-unplanned-downtime-update/

    The infrastructure upgrades we have made around the CVS service last year
    have made substantial uptime gains for the service and have helped to
    safeguard data. That said, the underlying design of CVS is a limiting
    factor (CVS's network protocol and data storage are both very limiting),
    and you would best be served by moving to a more modern SCM platform if
    high availability is one of your needs. We currently offer Git and
    Subversion (Subversion has a CVS-like command structure), and will soon
    be
    expanding our offering to include Mercurial and Bazaar as well. Our team
    will be glad to support your ongoing use of CVS, or to assist you in
    migrating to an alternate SCM platform.

    Please add a comment here if you have follow-up questions or concerns.

    Thanks,
    Travis West
    Support Guy
    SourceForge.net

    P.S., Support items set to status of 'Pending', will auto-close in 14 days if there is no response.

     
    • status: pending --> closed
     
  • This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).