* erik quanstrom <[EMAIL PROTECTED]> [081016 03:00]:
> On Wed Oct 15 14:38:47 EDT 2008, [EMAIL PROTECTED] wrote:
> > [...] 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
>
On Wed Oct 15 14:38:47 EDT 2008, [EMAIL PROTECTED] wrote:
> [...] 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.
were these cmp errors in any particular place on t
* erik quanstrom <[EMAIL PROTECTED]> [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.
> 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
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.
simliar story here, lost disk, lost data. In this case because I made
a mistake.
I've been wondering -- how much of your file systems are you using out there?
Seems to me that one could build a fanless wonder with a small via
embedded system and USB sticks -- 3 of them -- as the disks, running
in
we have three different console servers at coraid.
so i've changed how consoles and console logging
works. maybe this will be useful to other people.
here are the changes that make this work
1. instead of consoledb use /lib/ndb/consoledb.$sysname.
and have a general test for this new file in cpur
t; Subject: Re: [9fans] How to get the diagnostics of fs(3)
>
> * Fco. J. Ballesteros <[EMAIL PROTECTED]> [081015 10:42]:
> > We use aux/clog to send the contents of /dev/kprint to /sys/log/$sysname
> > We bind '#k' by hand after booting our server, but how you d
* Fco. J. Ballesteros <[EMAIL PROTECTED]> [081015 10:42]:
> We use aux/clog to send the contents of /dev/kprint to /sys/log/$sysname
> We bind '#k' by hand after booting our server, but how you do it it depends
> on the particular config for your machine.
>
As it has been I placed the fs= line in
; Date: Wed Oct 15 10:31:41 CET 2008
> Subject: [9fans] How to get the diagnostics of fs(3)
>
> Dear List,
>
> I have experienced a disk crash in a mirrored fs(3). It turned out
> that the mirroring has not been successful since December 2007 which
> is quite a loss for
Dear List,
I have experienced a disk crash in a mirrored fs(3). It turned out
that the mirroring has not been successful since December 2007 which
is quite a loss for me now.
To prevent a case like this it would have helped If I had seen the
error messages by fs(3) earlier/at all. By browsing thr
11 matches
Mail list logo
