AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070108112659.15f610d8@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<larry.scheer@onstor.com>,<tim.gardner@onstor.com>,<jay.michlin@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E0A90F2@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 8 Jan 2007 11:27:45 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Larry Scheer" <larry.scheer@onstor.com>
Cc: "Tim Gardner" <tim.gardner@onstor.com>, "Jay Michlin"
 <jay.michlin@onstor.com>
Subject: Re: /usr/bin/install the problem
Message-ID: <20070108112745.5b15b0b1@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0A90F2@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E0A90F2@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi Larry,

If I was convinced that install really had a bug, then I would be
inclined to go to Openbsd's webcvs site and see what changes have been
checked into that program since the version that we are using.  There
can't have been that many, the program really doesn't change very much.

If this is a problem with install program and not our software, then
someone else must have seen it sometime in the last 7 years, and they
would have fixed it by now, so that is what I would do: go looking for
the fix that must have already been done sometime in the last 7 years.

Cheers,

a

On Mon, 8 Jan 2007 09:49:38 -0800 "Larry Scheer"
<larry.scheer@onstor.com> wrote:

> Andy,
>    Over the weekend I ran continuous tests of upgrade and upgrade
> simulations using cp, tar, and /usr/bin/install with and without the
> -S flag. I also removed the -S (safe option) flag to the install
> command in the ugrade program and tested it. When using the install
> command I see file corruption about 10-20% of the time. It usually
> occurs when the system starts using swap space and nears the limits
> of memory.
> 
> I would like your opinion on how to proceed. 
> 
> Changing the upgrade program to use cp -p might be the quickest thing
> but some work would need to be done to make sure the permissions are
> the desired ones when the tar file is created, but this shouldn't be
> hard to do.
> 
> I could download the latest version of /usr/bin/install from the BSD
> distribution and build it into our version of OpenBSD but there is no
> guarantee this will change anything. Actually I have a version of 3.8
> OpenBSD in one of my directories today that I can use to replace the
> version we are using. I can build this and test it pretty quickly.
> 
> The other option is diving into the sources to figure out where and
> why the corruption is occurring. This would most likely need your
> expertise with the kernel and memory management to figure out and
> fix. This is most likely the "most correct" approach because we would
> now fully understand the issue but may also be time consuming.
> 
> I could pursue the other two approaches while you investigate the BSD
> code.
> 
> Let me know what you think.
> 
> Larry 
> 
> 
