9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "EBo" <ebo@sandien.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: [9fans] corrupted update on 9vx
Date: Thu, 22 Apr 2010 11:55:54 -0600	[thread overview]
Message-ID: <twig.1271958954.40543@swcp.com> (raw)
In-Reply-To: <i2ya560a5d01004221032ld264a5c2v651f6640a81bb73f@mail.gmail.com>

OK.  I've been trying to track down the odd 9vx crash and discovered some
other oddities and request some guidance in what might be causing the pull to
become corrupted and installing entire blocks of nil's in updated files.

Following details outlined in
http://fixunix.com/plan9/501128-9fans-pull-9vx.html, I first tried to update
the original plan9 distro, then moved to a new 9atom.iso.  To get the pull to
work I had to update the network and client db:

# cp -a plan9/dist/replica/client/plan9.* root9atom/dist/replica/client/
# cp -a plan9/dist/replica/network root9atom/dist/replica/network

Then I ran /usr/glenda/bin/rc/pull.  At one point it seemed to work until I
decided to recompile a couple of the commands in /sys/src/cmd and discovered
that several of the source files had blocks of nil's in them.  I wanted to see
if the problem was systematic or more random, so I saved that root tree and
reran the test.  What I found is that the corruption happens very often and at
seemingly random files and locations.  I also wanted to check to see if these
differences were consistent (like 4K blocks, etc).  I found that the number of
corrupted blocks, and their respective lengths, vary.  I also found that they
are not guaranteed to be multiples of 512.

These tests were so far run on my AMD x86_64.  I'll try rerunning these tests
on an Intel based laptop to see if this is some weird x86_64'ism.  I will also
try the Tvx code compiled for i486 on both machines

Does anyone have an idea what could be causing replica to behave so?  Has
anyone ever seen this behavior before?

  Thanks and best regards,


  EBo --




  reply	other threads:[~2010-04-22 17:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 17:32 [9fans] sam language question Rudolf Sykora
2010-04-22 17:55 ` EBo [this message]
2010-04-22 18:44   ` [9fans] corrupted update on 9vx Steve Simon
2010-04-22 18:53     ` erik quanstrom
2010-04-24  0:01       ` EBo
2010-04-22 18:21 ` [9fans] sam language question Rob Pike
2010-04-22 18:30   ` Rudolf Sykora
2010-04-22 18:24 ` yy
2010-04-22 18:32   ` Rudolf Sykora
2010-04-22 19:28     ` yy
2010-04-22 20:23       ` Rudolf Sykora
2010-04-22 22:04 ` roger peppe
2010-04-23  7:22   ` Rudolf Sykora

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=twig.1271958954.40543@swcp.com \
    --to=ebo@sandien.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).