On Thu, 2006-04-06 at 00:29, Eric Spakman wrote:
> >> Now that CVS is online again, we have a problem with checking out the
> >> bash sources. This is the message I get:
> >>
> >> cvs [update aborted]: Could not map memory to RCS archive
> >> /cvsroot/leaf/src/bering-uclibc/apps/bash/buildtool.cfg,v: No such
> >> device
Everyone,
It seems our cvs repository is in a corrupt state. I had a conversation
with SF staff member burley this morning:
<mhnoyes> burley, ping
<burley> mhnoyes: re
<mhnoyes> burley, Any update on the cvs issue we discussed the
other day?
<burley> mhnoyes: yes
<burley> So, we are aware of corruption on the host, as stated
in the site status page
* mhnoyes looks
<burley> so, need you guys to submit a confidential ticket on it
<burley> the resolution is going to be that we provide you with
a copy of your data to enable you guys to fix it
<burley> key here is to make sure that you don't overwrite your
own working copies, if at all possible, as that is another
viable point of restoration
<mhnoyes> burley, ok. Thanks for the information. I'll pass it
onto our developers, so they can address the issue.
<mhnoyes> burley, Do you want multiple SRs, or a single one?
<burley> one
<burley> action will be taken against the SR
<burley> but only one is necessary, as it doesn't change the
action we take
<mhnoyes> burley, Does the person submitting the SR need
bandwidth?
<burley> mhnoyes: no, but someone will, especially in your case
<mhnoyes> burley, ok. I'll post to our developers list, and have
someone with better available bandwidth open the SR.
http://sourceforge.net/docs/A04/
"( 2006-04-06 13:02:34 - Project CVS Service ) During the post-CVS
outage system assessment from the March 30, 2006 CVS outage, we have
noted a few cases of filesystem corruption on the developer CVS server.
We expect that a small number of repositories are affected (likely 50 or
less) by the data corruption. Accordingly, we'd like all projects to
audit their CVS repository for corruption and raise any issues to us via
a Confidential Support Request immediately. In order to ensure your own
data integrity, we also ask that you make a backup of your working copy,
and do a full checkout of your repository along-side your existing
working copy, so it can remain a valid source of data for your project,
should a file be found corrupt (it very well may be the most recent,
applicable data, even though we have multiple other sources for the same
file). In some cases, we have detected the corruption and will be
contacting those projects directly via email as we move forward. While
we continue to work on ensuring the data viability on the developer CVS
host, we are also continuing our progress with the replacement
infrastructure for CVS. The new hardware order has been placed and we
are concurrently preparing the technology and software components needed
to make the transition to the new infrastructure. Again, we thank you
for your patience and cooperation while we do everything we can to
safegaurd your data."
--
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
