From: Christian Kellermann <Christian.Kellermann@nefkom.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: mirtchovski@gmail.com
Subject: Re: [9fans] How to get the diagnostics of fs(3)
Date: Wed, 15 Oct 2008 20:37:15 +0200 [thread overview]
Message-ID: <20081015183715.GF1296@hermes.my.domain> (raw)
In-Reply-To: <d1e62424fe2073c736b5589d80c77a70@coraid.com>
* erik quanstrom <quanstro@coraid.com> [081015 18:23]:
> > back when i had mirroring via devfs (some three years ago now) i used
> > 'cmp' to verify that the disks were being correctly written to and
> > that no errors have occurred. i ran cmp from the nigtly log at least
> > couple of times a week.
>
> that's a good idea.
>
> when using the mirror device, no write error is issued unless all mirrored
> copies are unwritable. this would make me nervous since without a
> checksum, it's hard to know which copy is good.
>
> (/n/sources/plan9/sys/src/9/port/devfs.c:697)
Also it means that while the writes may be ok, you will find out
that some sectors are corrupt at the wrong time. For this a cmp
would not be sufficient would it? An interesting thing in my case
is that I got cmp errors from the start, even with freshly nulled
partitions and identical partitions and disks. I still cannot figure
out why.
Cheers,
Christian
next prev parent reply other threads:[~2008-10-15 18:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 8:28 Christian Kellermann
2008-10-15 8:39 ` Fco. J. Ballesteros
2008-10-15 8:47 ` Christian Kellermann
2008-10-15 9:13 ` Fco. J. Ballesteros
2008-10-15 15:48 ` ron minnich
2008-10-15 15:54 ` andrey mirtchovski
2008-10-15 16:19 ` erik quanstrom
2008-10-15 18:37 ` Christian Kellermann [this message]
2008-10-16 0:57 ` erik quanstrom
2008-10-16 7:38 ` Christian Kellermann
2008-10-15 12:42 ` erik quanstrom
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=20081015183715.GF1296@hermes.my.domain \
--to=christian.kellermann@nefkom.net \
--cc=9fans@9fans.net \
--cc=mirtchovski@gmail.com \
/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).