9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fs64 file server, partition boundaries out of range,
Date: Tue, 25 Jul 2006 16:44:32 -0700	[thread overview]
Message-ID: <14deef7df0d433ae637b4960799547c6@collyer.net> (raw)
In-Reply-To: <ca73f28a5049b321224b670770b08245@comcast.net>

It sounds like

	cannot add sd12!plan9 [63,156296385] to disk [0,976937355): partition boundaries out of range

is coming from 9load.  I haven't seen this, but it does sound like
garbled partition tables or a bad disk.  The first block of a file
system contains its configuration block, so if you plan to have an MBR
or other DOS/FAT stuff on the disk, you'll need to skip it.  I do that
on my main file server to allow a small DOS partition.  To do so, use
p(w0)1.99 instead of w0, for example.

`panic: fworm: checktag 6105775' is quite serious.  The fake-worm
bitmap isn't initialised.  Copying fworms is tricky, particularly if
the output device is larger than the input device.  You probably ought
to use copyworm instead of copydev, since copydev just blindly copies
blocks, assuming input and output are the same size, but copyworm
knows how to copy fworms, including reaming the output fworm, thus
creating its bitmap.



      parent reply	other threads:[~2006-07-25 23:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17 14:44 [9fans] Fs64 file server, partition boundaries out of range, and `Tvirgo' tag Gregory Pavelcak
2006-07-17 15:01 ` jmk
2006-07-25 23:44 ` geoff [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=14deef7df0d433ae637b4960799547c6@collyer.net \
    --to=geoff@collyer.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).