On Fri, May 24, 2013 at 3:50 AM, O. Hartmann <ohart...@zedat.fu-berlin.de>wrote:
> Since r250670 (last known stable) I face a lot of problems. > > On systems with SSD, after a couple of seconds the box is crashing and > rebooting, showing up a lot of CAM/SCSI stuff on the console. > > A system with "traditional" disks I get while shutdown in progress (via > ACPI power button or shutdown -p now command) corrupt filesystems (UFS > disk). > > Below an error message after such a crahs, /usr/ports is a partition and > while the shutdown was in effect, there were no activities on that > partition, but is has been "repaired" while the box then powered up > again. Now it seems to be corrupted in the way that I can not svn update > the ports tree anymore. > > What happened? > > > root@thor:/usr/ports # make update > -------------------------------------------------------------- > >>> Updating /usr/ports using Subversion > -------------------------------------------------------------- > cd /usr/ports; /usr/local/bin/svn update > svn: E155036: Please see the 'svn upgrade' command > svn: E155036: Working copy '/usr/ports' is an old development version > (format 12); to upgrade it, use a format 18 client, then use > 'tools/dev/wc-ng/bump-to-19.py', then use the current client > *** Error code 1 > > Stop. > make: stopped in /usr/ports > Coincidentally, I get that exact same error message today when I exported an SVN /usr/src tree to a raspberry-pi host from an amd64 system. I tried the script and it complains about I/O errors... dave c _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
