9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] i/o error: wrenwrite
Date: Wed,  3 Mar 2004 14:43:05 +0400	[thread overview]
Message-ID: <200403031043.i23Ah5dT098972@adat.davidashen.net> (raw)
In-Reply-To: <a36b0d5b22230cb3408bc74c7011d9d7@juice.thebigchoice.com>

> > But if I just turn it off with power button, FreeBSD comes up just fine after intensive disk writes just before poweroff;
>
> I wouldn't rely on that feature if I were you.
>

I do not rely on this feature. I properly do shutdown on all my servers
and terminals, and my file server's uptime is more than year now at home.

But I cannot allocate a 2KWh UPS to every computer; and sometimes
computers loose power. After this accident, I must be able to repair
the file system, either automatically, or manually,.

Plan9 has a bug that puts it into endless loop on my hardware
after reboot without fshalt. I am asking where to look at to
fix the bug.

David Tolpin


  reply	other threads:[~2004-03-03 10:43 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03  7:57 David Tolpin
2004-03-03  8:06 ` Fco.J.Ballesteros
2004-03-03  8:10   ` David Tolpin
2004-03-03  8:15     ` Fco.J.Ballesteros
2004-03-03  8:22       ` David Tolpin
2004-03-03  8:34         ` Fco.J.Ballesteros
2004-03-03  8:59           ` David Tolpin
2004-03-03  9:51           ` Geoff Collyer
2004-03-03  9:54             ` David Tolpin
2004-03-03 10:39               ` matt
2004-03-03 10:43                 ` David Tolpin [this message]
2004-03-03 11:37                   ` Charles Forsyth
2004-03-03 12:19                     ` David Tolpin
2004-03-03 12:46                   ` boyd, rounin
2004-03-03 12:44                 ` boyd, rounin
2004-03-03 20:35             ` splite
2004-03-03 21:25               ` Geoff Collyer
2004-03-03 21:42                 ` splite
2004-03-03 22:48                   ` boyd, rounin
2004-03-03  9:55     ` Bruce Ellis
2004-03-03 10:00       ` David Tolpin
2004-03-03 10:47         ` Richard Miller
2004-03-03 11:19           ` David Tolpin
2004-03-03 11:25             ` lucio
2004-03-03 11:34               ` David Tolpin
2004-03-03 20:11                 ` splite
2004-03-03 20:25                   ` David Tolpin
2004-03-03 13:41             ` jmk
2004-03-03 13:45               ` David Tolpin
2004-03-03 13:58                 ` C H Forsyth
2004-03-03 13:58                   ` lucio
2004-03-03 14:07                     ` C H Forsyth
2004-03-03 14:04                       ` David Tolpin
2004-03-03 14:14                         ` lucio
2004-03-03 14:23                           ` jmk
2004-03-03 14:24                             ` David Tolpin
2004-03-03 21:34                             ` Exact Eios " David Tolpin
2004-03-03 14:41                         ` Derek Fawcus
2004-03-03  9:15   ` Richard Miller
2004-03-03  9:18     ` David Tolpin
2004-03-03 12:31 ` boyd, rounin

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=200403031043.i23Ah5dT098972@adat.davidashen.net \
    --to=dvd@davidashen.net \
    --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).