From: sqweek <sqweek@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] sd(3) and concurrent readers/writers?
Date: Sun, 13 Sep 2009 02:08:28 +0800 [thread overview]
Message-ID: <140e7ec30909121108l411080bam3a34bac1168f911f@mail.gmail.com> (raw)
I have a fairly simple task - I'm trying to mirror a disk. So I run
the obvious:
dd -if /dev/sdE0/data -of /dev/sdF0/data -bs 1048576
That's sitting there on it's merry way, and I get curious as to how
much progress it has made. I think about acid briefly but I don't have
much experience with it, and figure I can get the answer without
touching the procs:
fn chk {
for(i in sdE0 sdF0) dd -if /dev/$i/data -bs 1048576 -iseek $1
-count 1 |md5sum
}
With this crude tool I can easily find a block that differs between
the disks and binary search to gauge how far through the process is.
However, something seems a little fragile. If I keep running chk
eventually the dd falls over with an error of some sort. It just gave
me "write: " (that's an empty error string by the looks of it) 3 times
in a row, and the fourth time around dd didn't report an error itself
but I get this in kmesg:
atagenioretry: disabling dma
sdE0: retry: dma 00000000 rwm 0000
Now it's got itself into a state where even without the dd going, if
I turn dma on for sdE0 and run chk it disables dma again. Hm, in fact
some time before getting the kmesg, reads to sdE0/data started
returning 0 bytes regardless of offset.
System details: SIL3112 sata controller... is there an easy way to
tell if I'm in AHCI mode or not? can't see anything obvious in the
bios. During boot I get these relevant looking lines:
dev A0 port 170 config 85C0 capabilities 0F00 mwdma 0007 udma 0407
dev A0 port 9400 config 0C5A capabilities 2F00 mwdma 0007 udma 207F
LLBA sectors 586072368
dev A0 port 9C00 config 0C5A capabilities 2F00 mwdma 0007 udma 207F
LLBA sectors 586072368
-sqweek
next reply other threads:[~2009-09-12 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 18:08 sqweek [this message]
2009-09-12 18:23 ` erik quanstrom
2009-09-13 14:44 ` erik quanstrom
2009-09-14 18:43 ` sqweek
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=140e7ec30909121108l411080bam3a34bac1168f911f@mail.gmail.com \
--to=sqweek@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).