From: Russ Cox <rsc@swtch.com>
To: Thomas Miller <tom@insolvencyhelp.org>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] fossil shutdown
Date: Fri, 7 Oct 2005 00:11:50 -0400 [thread overview]
Message-ID: <ee9e417a0510062111m716995dbp90df16ef1a20cf61@mail.gmail.com> (raw)
In-Reply-To: <4345f0bd.l5R330s/pBsD2tR1%tom@insolvencyhelp.org>
> > echo dma on >/dev/sdXX/ctl
> > echo rwm on >/dev/sdXX/ctl
> Inspired, I tried this, and I got an improvement (decrease)
> in time taken to copy files to a new filename of at least
> an order of magnitude.
> I was surprised to find the letters "rwm on" right at the
> beginning of the disk. I saved the output of
> I'm pretty sure that I did *not* type
>
> echo rwm on > /dev/sdC0/data /* WRONG */
I'm pretty sure that you did type
echo dma on >/dev/sdC0/ctl
echo rwm on >/dev/sdC0/data
explaining both the performance improvement
and the subsequently broken mbr.
The disk fragment you posted on the ftp server
begins with a standard NetBSD mbr except that
the first 7 bytes are "rwm on\n". This is perfectly
explained by a typo and very hard to explain with
a software or hardware error.
Once I set up a pseudo-worm file server on a few
SCSI disks, spent a few hours populating it, and then
rebooted and the kernel couldn't find the file system.
On inspection, I found postscript code in what should
have been the file server's superblock. That felt like a
hardware error (shouldn't use discarded machines;
people discard them for a reason!). This doesn't.
Russ
next prev parent reply other threads:[~2005-10-07 4:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 8:01 fgergo
2005-09-22 14:15 ` David Leimbach
2005-09-22 14:19 ` Charles Forsyth
2005-09-22 14:53 ` David Leimbach
2005-10-07 3:51 ` Thomas Miller
2005-10-07 4:11 ` Russ Cox [this message]
2005-10-07 10:21 ` Charles Forsyth
2005-10-07 15:49 ` Dave Eckhardt
2005-10-07 16:02 ` Russ Cox
2005-09-22 14:19 ` Russ Cox
2005-09-22 14:23 ` David Leimbach
2005-09-22 14:38 ` David Leimbach
2005-09-22 16:11 ` Dave Eckhardt
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=ee9e417a0510062111m716995dbp90df16ef1a20cf61@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
--cc=tom@insolvencyhelp.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).