9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] disk is full; can't boot to fix it because disk is full
Date: Mon, 12 Jan 2004 17:54:21 +0100	[thread overview]
Message-ID: <6aaa709812623c0506990f8b0647f59f@plan9.escet.urjc.es> (raw)
In-Reply-To: <Pine.LNX.4.44.0401120831220.12252-100000@maxroach.lanl.gov>

[-- Attachment #1: Type: text/plain, Size: 84 bytes --]

cant you boot from a cd and then use a fossil
to drop some (temporary) snapshots?

[-- Attachment #2: Type: message/rfc822, Size: 2786 bytes --]

From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] disk is full; can't boot to fix it because disk is full
Date: Mon, 12 Jan 2004 08:34:12 -0700 (MST)
Message-ID: <Pine.LNX.4.44.0401120831220.12252-100000@maxroach.lanl.gov>


Came back after the weekend any my Plan 9 cluster is down.

The front end says this many times:
cacheAllocBlock wrap 609408
cacheAllocBlock: xxx1 disk is full
cacheAllocBlock wrap 609408
cacheAllocBlock wrap 609408
cacheAllocBlock: xxx1 disk is full
.
.
.
.
boot: /386/init: '/386/init' disk is full
panic blah blah blah


ok, the disk is full, can't boot, can't get in to fix it. Any options here
or am I totally screwed?

Are these fossil or Venti errors? I would look but my Plan 9 machine is
.... well, you guessed it.

ron

      parent reply	other threads:[~2004-01-12 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-12 15:34 ron minnich
2004-01-12 15:55 ` mirtchov
2004-01-12 15:55   ` ron minnich
2004-01-12 19:28     ` Scott Schwartz
2004-01-12 20:16       ` Christopher Nielsen
2004-01-13  6:57         ` boyd, rounin
2004-01-12 16:54 ` Fco.J.Ballesteros [this message]

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=6aaa709812623c0506990f8b0647f59f@plan9.escet.urjc.es \
    --to=nemo@plan9.escet.urjc.es \
    --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).