From: covertusername967@gmail.com
To: covertusername967@gmail.com, 9front@9front.org
Subject: devfs config file loading on startup
Date: Sun, 10 May 2020 13:17:29 -0500 [thread overview]
Message-ID: <3B225AC4901770DA67232ABB3C41C37B@gmail.com> (raw)
Hello,
I recently bootstrapped a new file server that I plan on using to
replace my old one. I have nearly everything working, other than
unattended startup - I can't seem to get devfs to load the config file
specified in plan9.ini. I can configure it manually by catting the
same config file into /dev/fs/ctl and then bring up cwfs using the
resulting file in /dev/fs, but it's not there on startup, which makes
cwfs panic.
I dd'ed the WORM from my old file server onto a 2-disk array of drives
that was set up by fs(3) using the following config line:
mirror worm /dev/sdE0/data /dev/sdE2/data
This line is stored on a raw 512-byte partition on a separate SSD at
/dev/sdN0/fsconfig. The resulting /dev/fs/worm was then used to bring
up a cwfs with a cache/other on the same SSD:
filsys main c(/dev/sdN0/fscache)(/dev/fs/worm)
filsys dump o
filsys other (/dev/sdN0/other)
The file system was initialized successfully. However, it will not
boot unattended. Here is my plan9.ini:
bootfile=9pc64
fsconfig=/dev/sdN0/fsconfig
nvram=/dev/sdN0/nvram
bootargs=local!/dev/sdN0/fscache -a tcp!*!564
nobootprompt=local!/dev/sdN0/fscache -a tcp!*!564
mouseport=2
monitor=vesa
vgasize=1366x768x32
service=cpu
*acpi=1
On startup, cwfs will panic with the following message:
panic: wreninit: can't open /dev/fs/worm for w"/dev/fs/worm":
'/dev/fs/worm' does not exist
Dropping into rc from the resulting bootargs prompt confirms the lack
of a 'worm' file after listing /dev/fs. However, catting
/dev/sdN0/fsconfig into /dev/fs/ctl does create the file, as expected,
allowing cwfs to come up normally. Am I doing something wrong here?
reply other threads:[~2020-05-10 18:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B225AC4901770DA67232ABB3C41C37B@gmail.com \
--to=covertusername967@gmail.com \
--cc=9front@9front.org \
/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).