freebsd-update upgrading 9.2 - 9.3
Trying to upgrade a system from 9.2 - 9.3 with freebsd-update and I get the output below. Search has seen reports but not solutions. I also tried upgrading to 10.1 and seeing similar issue those the No such file or directory error only shows up once but is asking for me to manually merge lots of unmodified files in /etc. Anybody have a clue on what is going wrong? -- Dave freebsd-update -r 9.3-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching public key from update6.freebsd.org... done. Fetching metadata signature for 9.2-RELEASE from update6.freebsd.org... done. Fetching metadata index... done. Fetching 2 metadata files... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic world/base world/doc world/lib32 The following components of FreeBSD do not seem to be installed: src/src world/games Does this look reasonable (y/n)? y Fetching metadata signature for 9.3-RELEASE from update6.freebsd.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. Fetching files from 9.2-RELEASE for merging... done. Preparing to download files... done. Fetching 1322 patches.102030405060708090100110120130140150160170180190200210220230240250260270280290300310320330340350360370380390400410420430440450460470480490500510520530540550560570580590600610620630640650660670680690700710720730740750760770780790800810820830840850860870880890900910920930940950960970980990100010101020103010401050106010701080109011001110112011301140115011601170118011901200121012201230124012501260127012801290130013101320. done. Applying patches... done. Fetching 199 files... done. /usr/sbin/freebsd-update: cannot open files/.gz: No such file or directory /usr/sbin/freebsd-update: cannot open files/.gz: No such file or directory /usr/sbin/freebsd-update: cannot open files/.gz: No such file or directory [ snip the out the 100 repeats of this error ] /usr/sbin/freebsd-update: cannot open files/.gz: No such file or directory /usr/sbin/freebsd-update: cannot open files/.gz: No such file or directory The following file will be removed, as it no longer exists in FreeBSD 9.3-RELEASE: /boot/device.hints Does this look reasonable (y/n)? n ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd-update upgrading 9.2 - 9.3
On Jun 14, 2015, at 8:59 AM, Rainer Duffner rai...@ultra-secure.de wrote: Am 14.06.2015 um 15:46 schrieb Dave Duchscher da...@nostrum.com: Trying to upgrade a system from 9.2 - 9.3 with freebsd-update and I get the output below. Search has seen reports but not solutions. I also tried upgrading to 10.1 and seeing similar issue those the No such file or directory error only shows up once but is asking for me to manually merge lots of unmodified files in /etc. Anybody have a clue on what is going wrong? Are you on the latest patch-level for 9.2? Looking, I am not at the latest version. Trying to upgrade to the latest version breaks things (ssh is the main thing, missing libssh.so.5 errors). Ignoring the breakage, I get the same errors. Using the freebsd-update script from the latest 9.2 doesn't help. I am guessing a rebuild of the system is necessary. That may have to wait for another day. Thankfully, I can rollback. -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: JFS
On Sat, Jul 07, 2001 at 08:35:35PM -0500, Dave Uhring wrote: You seem to have missed the critical point of that paper. When the system goes completely haywire and either crashes or locks up so hard that a manual reset is required, UFS/softupdates requires a substantial amount of time to run fsck. If you have a very large filesystem, you then have to wait until fsck completes. And if you are lucky, it will not terminate with the suggestion that you run fsck by hand. With a true journalling filesystem this wait is obviated. The last transactions are rerun or truncated and the system boots up. Just to bring up a point, Softupdates will also avoid the long fsck at boot. If I understand the papers I have read and with playing with Softupdates on current, Softupdates leaves files system in a consistent state so that the file-system can be mounted after a crash/lockup/etc immediately and only a background fsck need be run to free up left over pieces laying around. You guys also might want to wonder over to Kirk's Softupdates site: http://www.McKusick.com/softdep/index.html DaveD To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
