From: "Sigrid Haflinadóttir" <sigrid.haflinadottir@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Partition problems
Date: Wed, 23 Nov 2016 18:58:28 +0100 [thread overview]
Message-ID: <CAP9joagwUAjrfjPpmsFQaZZa=H1LFh4rhN-6AphQZ9KVudA7tw@mail.gmail.com> (raw)
In-Reply-To: <CABJnqBSX8+OMJN+Q0kieJXL7NZvWhCK6rkTPL4WE7VbxqEqTxg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1987 bytes --]
He didn't ask about 9front.
On Wed, Nov 23, 2016 at 4:13 PM, Iruatã Souza <iru.muzgo@gmail.com> wrote:
> 9front solved that 5 years ago.
>
> On Mon, Nov 21, 2016 at 5:20 AM, <tlaronde@polynum.com> wrote:
> > Hello,
> >
> > On Sun, Nov 20, 2016 at 11:07:03PM +0000, Steve Simon wrote:
> >> Hi,
> >>
> >> I run a modified labs kernel with a few bits of 9atom to support my atom
> >> Motherboard.
> >>
> >> I have added an ssd to the mirrored disks in my plan9 server.
> >> The initialisation of devfs fails without a helpful error message
> (something I will sort out)
> >>
> >> However the source of the problem seems to be boot/parts.c which fails
> to instantiate the last partition on my disks. This causes devfs to give up
> rather than continuing to retry other partitions. My kernel then cannot
> find its venti partition and dies with a panic.
> >>
> >> If I boot using a different partition structure I can bring up the
> machine, and see that this one partition is indeed missing.
> >>
> >> If I run disk/prep on the disk and rewrite the partition table
> unchanged, the missing partition appears.
> >>
> >> Anyone seen problems with the partition table generation code in
> boot/part.c?
> >> If not I will keep digging but I thought it was worth asking.
> >
> > I had a problem (and still have) with the plan9 program because the code
> > rewrites the whole partition entry, recomputing the values of the start
> > and so on even with partitions "untouched" rendering the machine
> > unbootable because the starting block was not the correct one.
> >
> > I have never found neither the time nor the incentive to correct this
> > part.
> >
> > I don't know if this has anything to do with your problem at hand.
> >
> > Best,
> > --
> > Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
> > http://www.kergis.com/
> > Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
> >
>
>
[-- Attachment #2: Type: text/html, Size: 2699 bytes --]
next prev parent reply other threads:[~2016-11-23 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 23:07 Steve Simon
2016-11-21 7:20 ` tlaronde
2016-11-23 15:13 ` Iruatã Souza
2016-11-23 17:58 ` Sigrid Haflinadóttir [this message]
2016-11-24 10:20 ` Iruatã Souza
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='CAP9joagwUAjrfjPpmsFQaZZa=H1LFh4rhN-6AphQZ9KVudA7tw@mail.gmail.com' \
--to=sigrid.haflinadottir@gmail.com \
--cc=9fans@9fans.net \
/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).