The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wlc@jctaylor.com (William Corcoran)
Subject: [TUHS] SYSTEM V R1 HELP
Date: Thu, 21 Dec 2017 22:12:33 +0000	[thread overview]
Message-ID: <8157BC46-2833-48D5-B224-B9E488A4B8F0@jctaylor.com> (raw)

Hello Team TUHS: 

I am having a problem with my PDP-11 SVR1 running under a recent SIMH build.  My problem occurs on both MAC OS X and FreeBSD.  

First, I created a six disk (RP06) and eight port TTY (DZ) kernel, with swap placed on drive 1.  The system behaves beautifully as FSCK reports clean.  Eight users can login with no problem.  

Second, I reverted to a pristine PDP-11 SVR1 with one drive (RP06) and no DZ and booted the default kernel (gdtm) and I see the same problem described below.

Third, when using the tape driver instead of /dev/null i get the same results.   

Next, here is the issue: 

cd / 
find . -print | cpio -ocvB > /dev/null 

It runs for a short while and then shitz a core: 
I am using /dev/null to take the tape driver out of the equation.  

Here is the backtrace for cpio:  

$c
__strout(053522,043,0,053012)
__doprnt(046652,0177606,053012)
_fprintf(053012,046652,053522)
~main(02,0177636)


Now, interestingly,  I run into a similar issue when using tar: 

cd  /usr
tar -cvf /dev/null . 

Again, this will run for a while, then drops a core.  Here is the backtrace for tar:  

$c
__strout(043123,02,0,045506)
__doprnt(043123,0167472,045506)
_fprintf(045506,043123,0170600)
~putfile(0170600,0170641)
~putfile(0171654,0171704)
~putfile(0172730,0172745)
~putfile(0174004,0174016)
~putfile(0175060,0175066)
~putfile(0176134,0176136)
~putfile(0177672,0177672)
~dorep(0177632)
~main(04,0177630)

This really bugging me since my SVR1 is otherwise working flawlessly.  I was able to remake the entire system and custom kernels that boot with no problem.   
Also, I configured my main port to run inside the AWS Lightsail and now I have access to SVR1 from anywhere in the world!

I was also wondering if doing a CPIO or TAR on the entire system was overflowing some link tables and maybe this is expected behavior for the minimal resource of the PDP-11?

Thank you for any help.   

Would you expect tar or cpio to dump core if you attempted to copy large filesystems  (or the entire system) on a PDP-11? 
Note: All of my testing has been in single user mode.   


Truly, 

Bill Corcoran  











             reply	other threads:[~2017-12-21 22:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 22:12 William Corcoran [this message]
2017-12-21 22:30 ` Clem Cole
2017-12-22  0:34   ` William Corcoran
2017-12-22  1:51     ` William Corcoran
2017-12-22  1:54       ` William Corcoran
2017-12-22  2:55       ` Random832
2017-12-22  3:47         ` William Corcoran
2017-12-22  9:09           ` Random832
2017-12-22 12:42             ` William Corcoran
2017-12-22 23:48             ` William Corcoran
2017-12-23  0:19             ` Dave Horsfall
2017-12-23  0:21               ` Larry McVoy
2017-12-23 12:26                 ` Clem cole
2017-12-22 15:04       ` Clem Cole
2017-12-22  1:55     ` Random832

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=8157BC46-2833-48D5-B224-B9E488A4B8F0@jctaylor.com \
    --to=wlc@jctaylor.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).