9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: link=3Dvga; broken f.s.
Date: Sun,  6 Aug 1995 12:20:44 -0400	[thread overview]
Message-ID: <19950806162044.wPTDmhBZrQ1-Jp2jfHkRy_KO4UdCrT5SWGb6s5ObdJw@z> (raw)

>>2) i don't understand the reference to "link=3Dvga", you haven't been fiddling
>>   with aux/vga without a licence have you?

splite@wdni.com's mailer seems to be using = as an escape (3D is `=').

>>Content-Type: text/plain; charset=X-roman8
>>Content-Transfer-Encoding: quoted-printable

anyhow, as far as this goes:

>>prompt.  /tmp/x contains:
>>	tag = Tnone; expected Tfile

that probably signifies a corrupt file system; that looks to me like a
message from disk/kfs (or /fs).

it isn't surprising there are problems if the system hung up
and had to be reset before a disk/kfscmd halt could be done.
(if it happens again, wait about 30 seconds before resetting
to give it a chance to sync automatically; normally the f.s. will
then be consistent.)

disk/kfscmd 'check' will show the extent of the damage, but
the demo. system is small enough that there aren't any optional files;
something is bound to break later.

while it is possible to make the curdled file system consistent again using
the options to disk/kfscmd 'check', it's probably better to unpack the
distribution again into a remade file system.






             reply	other threads:[~1995-08-06 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-08-06 16:20 forsyth [this message]
1995-08-07 18:30 Steven
1995-08-07 23:36 Scott
1995-08-08 12:50 presotto
1995-08-08 17:02 Steven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19950806162044.wPTDmhBZrQ1-Jp2jfHkRy_KO4UdCrT5SWGb6s5ObdJw@z \
    --to=forsyth@plan9.cs.york.ac.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).