From owner-freebsd-questions Sun Oct 15 10:50: 3 2000 Delivered-To: freebsd-questions@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 1403137B503 for ; Sun, 15 Oct 2000 10:49:59 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id KAA04468; Sun, 15 Oct 2000 10:49:37 -0700 Message-ID: <39E9EE30.872E2EE9@urx.com> Date: Sun, 15 Oct 2000 10:49:36 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Bob Willcox Cc: questions list Subject: Re: Problem with vi recover References: <20001015090115.A35837@luke.immure.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob Willcox wrote: > > My system crashed while I had a number of unsaved changes to a file and > unfortunately "vi -r myfile" fails for me. When I try it I get: > > +=+=+=+=+=+=+=+ > There are other files for you to recover; gipmain.c: modified: line 1. > Error: unable to retrieve line 39; Error: unable to retrieve line 40. > Error: unable to retrieve line 41; Error: unable to retrieve line 42. > Error: unable to retrieve line 43; Error: unable to retrieve line 44. > Error: unable to retrieve line 45; Error: unable to retrieve line 46. > Error: unable to retrieve line 47; Error: unable to retrieve line 48. > Error: unable to retrieve line 49; Error: unable to retrieve line 50. > Error: unable to retrieve line 39; Error: unable to retrieve line 40. > Error: unable to retrieve line 41; Error: unable to retrieve line 42. > Error: unable to retrieve line 43; Error: unable to retrieve line 44. > Error: unable to retrieve line 45; Error: unable to retrieve line 46. > Error: unable to retrieve line 47; Error: unable to retrieve line 48. > Error: unable to retrieve line 49; Error: unable to retrieve line 50 > > errors repeated over and over and the vi process hangs (after allocating > 258MB of memory). > > Does "vi -r" work for others? Is it possible that I just have some > kind of configuration error on my system? Any help would be greatly > appreciated...I really don't want to have to recreate my changes! :-( I've used vi -r on many occasions. One of my most memorable was trying to edit a 50MB file on a Cray XM/P. One historical problem with vi is that it can fill /tmp and if you don't catch it, nasty things will happen. Could you have had an edit change get away from you and create lines the system can't load because you have filled the filesystem where vi is keeping its temp space. Kent > > Thanks, > Bob > > -- > Bob Willcox Have the courage to take your own thoughts > bob@VIEO.com seriously, for they will shape you. > Austin, TX -- Albert Einstein > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message