Date: Wed, 4 Oct 1995 07:42:07 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: mrami@minerva.cis.yale.edu Cc: hackers@freebsd.org Subject: Re: Well... Message-ID: <199510040642.HAA20882@uriah.heep.sax.de> In-Reply-To: <Pine.BSF.3.91.951003153552.9091B-100000@mramirez.sy.yale.edu> from "Marc Ramirez" at Oct 3, 95 03:47:01 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As Marc Ramirez wrote: > > After having accidentally blown away /home, I find that the ft driver > doesn't seem to work anymore. This is on 2.1-STABLE vintage about two > weeks. When doing > > > root[/usr]# ft|restore tf - > > It gives the dump info > > > Dump date: Sun Oct 1 12:52:00 1995 > > Dumped from: the epoch > > Level 0 dump of /home on mramirez.sy.yale.edu:/dev/sd1a > > Label: none > > and proceeds to list files. > > After the first block (I think), it stops, I get console messages to the > effect > > > fdc0: output ready timeout > > fdc0: input ready timeout > > fdc0: input ready timeout I'm about to commit a minor fix that supresses these message that are confusing ft users in the regular case (they will be hidden behind "bootverbose" aka. boot -c). They are (for the ft driver) benign. > and then ft dies and I get > > > ... > > 21440 ./mail/jian > > 21774 ./jay > > 21775 ./jay/.bash_history > > Broken pipe > > root[/usr]# I cannot confirm this. I've just checked on my 2.1 test machine, and was able to succesfully extract an old dump tape. This is with a Colorado QIC-40 drive. Nobody has been touching that code in the last months, btw., neither in -current nor 2.1-stable. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510040642.HAA20882>