9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Martin Harriss <martin@Princeton.EDU>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs incompatable w/ ASUS CUSL2
Date: Mon, 19 Mar 2001 16:53:11 -0500	[thread overview]
Message-ID: <3AB67FC7.C72A68C1@princeton.edu> (raw)
In-Reply-To: <3AB66EE7.3E952A50@mailbag.com>

Ed Brown wrote:
> ...
> A long running program that accessed the
> ide file system sdta during a dump
> caused the file server to throw a
> hissy.  After that point I received
> phase errors on any files on sdta.
> Doing a check on sdta from the file server
> caused it to reboot.  I could get
> the file server to reboot from a terminal
> by doing an ls on the root of sdta or
> an ls in the first dump of main.
> ...

Locking not quite worked out for devata????

--Martin


  reply	other threads:[~2001-03-19 21:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-19 20:41 Ed Brown
2001-03-19 21:53 ` Martin Harriss [this message]
2001-03-20  2:34   ` Eric Dorman
2001-03-20  9:59 ` Douglas A. Gwyn
2001-03-20 12:34   ` Ed Brown
2001-03-21  2:16     ` Eric Dorman
2001-03-21  2:32 Russ Cox
2001-03-21  5:44 ` Eric Dorman

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=3AB67FC7.C72A68C1@princeton.edu \
    --to=martin@princeton.edu \
    --cc=9fans@cse.psu.edu \
    /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).