🚀 go-pugleaf

In article <1jit6r$gb4@agate.berkeley.edu> izumi@pinoko.berkeley.edu writes:
>In article <C14r6A.B9K@dartvax.dartmouth.edu> fermat@fermat.dartmouth.edu (Michael Glenn) writes:

>>Is sonata having problems because of disk space?


Please Excuse me for jumping into this discussing late, but
I have been working on getting things right on CS.ORST.EDU.

We had been very short of space. We were loosing submissions 
because people just could not put things onto the disk.


>Perhaps, NeXT and other companies are  willing to donate for more disk
>space?  Particularly those companies that distribute demos via sonata
>that, upon license key activation, become fully functional products.
>

With some very generous work by our Next Representative (thanks marti)
we have been given a large 1.4G disk. That is the good news.
We had it up a couple of weeks ago and things looked rosy,
until people started saying that things were getting damaged.
After looking at the disk, it looks like the disktab is/was a
bit sick. This weekend, I rebuild the disktab and reformated
the disk and it looks like we have a working Next area with 
lots of space:

/dev/dsk/4s0        1007042  237355  668982    26%   /usr/local/ftp/pub/next

For the short term. this should hold us is good stead. 
In the long term, we probably will need more space.

We are working on revamping how our computer systems are 
connected here, so the next archive is likely to move from
CS.ORST.EDU to something like ftp.cs.orst.edu... More
when we get it finalized. 

The FTP site at CS.ORST.EDU is managed by volunteers who
find time between real work to handle the site. I hope that
we have been providing a good service. Any help 
that you might want to give us would go a long way for 
us to keep this service running. 

If you have questions about the CS.ORST.EDU next area send
mail to next-ftp@cs.orst.edu and it will get to those
of us who are working on the ftp area.

If you have problems with anything on the ftp area. Please
let me know.

Now for a request for some help....

The disk that we got from next is a Seagate 41650N disk.
A nice 1.4 G disk. 

We called seagate and got all the drive specs:

the Segate 41650N is a scsi drive.
        15ms seek time
        autoparking
        2107 cylinders
        15 heads
        87 average sectors per track
			

From this we created the disktab:
		
seagate41650:\
        :No swap:ns#43:nt#15:nc#2107:\
        :s0#1359015:b0#8192:f0#1024:\
        :se#1024:rm#3600:

This looked like it worked fine, but in fact there were blocks that
it could not read. After some playing, I was able to find that
somewhere after 1.05G, every 10368 blocks was not readable.
Because we had been down for 3 days. I decided to just 
size the disk smaller than 1.05G.

I would rather have the extra 400M back if I can get it.

We are currently running with a disktab entry of:

seagate41650:\
        :No swap:ns#33:nt#15:nc#2107:\
        :s0#1042965:b0#8192:f0#1024:\
        :se#1024:rm#3600:
			
And it fscks fine.


Does anyone know how I might fix this problem?



-------
John Sechrest		.		Internet: sechrest@cs.orst.edu
Lab Coordinator		 .       	UUCP: hplabs!hp-pcd!orstcs!sechrest 
Computer Science Dept	  .      	
Oregon State University	    .
Corvallis,Oregon 97331         . 
(503) 737-3273                      .