From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: [9fans] bug in disk/format
Date: Sat, 25 May 2002 20:01:59 -0700 [thread overview]
Message-ID: <200205260302.g4Q31xS1037269@ducky.net> (raw)
Here is a report of a bug in disk/format that results
in broken 9fat partitions that won't boot.
The test system is using a 9GB IBM SCSI disk drive
connected to an 53c875 based controller. Plan 9
is the only operating system on this computer.
term% cat /dev/sd01/ctl
inquiry IBM DGHS09Y 03E0682B91A1GAGSPMT03E
geometry 17916240 512
part data 0 17916240
part plan9 63 17912475
part 9fat 63 20545
part fs 20545 16971267
part swap 16971267 17912475
In this demonstration, /dev/sd01/9fat initially contains all
bytes 0 except for the Plan 9 partition table in block 1.
Now we run disk/format following the example in the
man page:
term% disk/format -b /386/pbs -d -r 2 /dev/sd01/9fat /386/9load /386/9pcdisk /tmp/plan9.ini
Initialising FAT file system
type hard, 10 tracks, 64 heads, 32 sectors/track, 512 bytes/sec
Adding file /386/9load, length 177320
Adding file /386/9pcdisk, length 1744105
Adding file /tmp/plan9.ini, length 185
used 1927168 bytes
Now, using dossrv, we unfortunately find that 9load and
9pcdisk were not copied correctly!
term% 9fat:
term% cmp /386/9load /n/9fat/9load
/386/9load /n/9fat/9load differ: char 55809
term% cmp /386/9pcdisk /n/9fat/9pcdisk
/386/9pcdisk /n/9fat/9pcdisk differ: char 1
The system crashes in 9load when I try to boot from
the resulting 9fat partition.
Using dossrv and cp I was able to manually recopy 9load
and 9pcdisk to the 9fat partition to make a bootable system,
but this would be a bad experience for a new user.
next reply other threads:[~2002-05-26 3:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-26 3:01 Mike Haertel [this message]
2002-05-26 4:13 rsc
2002-05-26 5:11 ` Mike Haertel
2002-05-26 5:22 Geoff Collyer
2002-05-26 5:27 rsc
2002-05-26 6:01 ` Mike Haertel
2002-05-26 6:19 rsc
2002-05-26 20:40 ` Mike Haertel
2002-05-26 22:13 rsc
2002-05-27 6:31 ` Michael Baldwin
2002-05-27 8:32 nigel
2002-05-27 17:49 rsc
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=200205260302.g4Q31xS1037269@ducky.net \
--to=mike@ducky.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).