From: erik quanstrom <quanstro@coraid.com>
To: rsc@swtch.com, 9fans@cse.psu.edu
Subject: Re: [9fans] ls: /net: '/net' clone failed
Date: Tue, 19 Dec 2006 20:05:20 -0500 [thread overview]
Message-ID: <d775017012d735d0468434505dedee35@coraid.com> (raw)
i did restart dns, but it was not Broken at the time. other cpu
sessions were trouble-free.
- erik
On Tue Dec 19 18:35:18 EST 2006, rsc@swtch.com wrote:
> something mounted onto /net has broken.
> perhaps dns. ps|grep Broke
> etc.
>
> On 12/19/06, erik quanstrom <quanstro@coraid.com> wrote:
> > i've been getting this error message lately:
> >
> > cpu% lc /net
> > ls: /net: '/net' clone failed
> >
> > what's going on? the network seemed to be working -- i was
> > able to type that command and read it.
> >
> > - erik
next reply other threads:[~2006-12-20 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 1:05 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-19 22:14 erik quanstrom
2006-12-19 23:34 ` Russ Cox
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=d775017012d735d0468434505dedee35@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
--cc=rsc@swtch.com \
/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).