Big Disks, NFS, Solaris 2.3 and SunOS 4.1.3_U1

Big Disks, NFS, Solaris 2.3 and SunOS 4.1.3_U1

Post by Michael T.Y. McNama » Tue, 12 Jul 1994 12:51:14



        I just bought a SEAGATE-ST410800N-0016, which is a 9 GB
5.25" SCSI II disk.  Thats right, 9,090,000,000 bytes (formatted).
I paid $0.51 per megabyte.

        I installed it on a SparcServer 1000, running Solaris 2.3,
with no problem.  I split it into 3 equally sized partitions (about
2.9 GB each)

        I've exported (sorry, shared) the disk, and my SunOS 4.1.3_U1
machine list it as:
sunos % df
Filesystem            kbytes    used   avail capacity  Mounted on
/dev/sd2a              15583    5899    8126    42%    /
  ...  
empty:/dsk1          2097151       0 2097151     0%    /tmp_mnt/Net/empty/dsk1
empty:/dsk2          2097151       0 2097151     0%    /tmp_mnt/Net/empty/dsk2
empty:/dsk3          2097151       0 2097151     0%    /tmp_mnt/Net/empty/dsk3

In reality, the disk is:
solaris % df
/dev/dsk/c3t0d0s3    2902873  188255 2424338     7%    /dsk1
/dev/dsk/c3t0d0s4    2901077       9 2610968     0%    /dsk2
/dev/dsk/c3t0d0s5    2901077      27 2610950     0%    /dsk3

        My question is, am I just looking at a myopic assumption made
at SMI in /bin/df on or about the 28th of November, 1989 [ % strings

break loose if one of these partitions grows over 2^30 bytes in use?

        Is there a patch I should install (he askes with a naive
twang in his voice)...

        Should I make it 5 1.8GB partitions :-?

        Please reply by mail.. (or to comp.unix.solaris, as we do not
receive comp.sys.sun.admin at our site)

        -mac

--


`------' A VIEWlogic Company      For information, call 1-800-VERILOG

 
 
 

1. SunOS 4.1.3_U1 and BIG disks?

Hi.

        yeah OK so I wasn't thinking.

        We had a disk start acting flakey, so I took a 4GB
        Disk from a solaris machine which we weren't using
        and hooked it up to our last SunOS 4.1.3_U1 server

        When I looked at in format, I was a tad surprised
        to have it find and like the solaris partition
        table (Then I thought about it more and I wasn't
        that surprised anymore.) I had no trouble mounting
        it either. I should say here, that the disk was
        partitioned on Solaris to be one 4gb partition.

        Well, I've been copiing files onto it for about 2
        hours now, and I wanted to see how it was going.

        So I typed 'df' here's what I got:

/dev/sd7d            2097151       0 2049531     0%    /export/local

        Then I remembered that SunOS doesn't like FS's
        bigger than 2GB.

        I do know that if it is an NFS filesystem, it will
        work fine but 'df' just won't output the right
        info.

        Is the same true for local ufs disks also? It seems
        to be working fine so far. Will I have problems when
        it actually gets to 2GB? Should I start over?

                Thanks.

                        -Kyle

--
                                   _
-------------------------------ooO( )Ooo-------------------------------
Kyle J. McDonald                 (o o)                 Systems Analyst/
Northeastern University          |||||          Applications Programmer

360 Huntington Ave. 230SN        \\\//          voice:    (617)373-3361
Boston MA 02115                  (o o)            fax:    (617)373-8504
-------------------------------ooO(_)Ooo-------------------------------

2. log formats, virtual hosts

3. nfs performance SunOS 4.1.3_U1 vs Solaris 2.4

4. After Week 1 With Linux -- licking wounds.

5. SunOS 4.1.3_U1 and Solaris 2.4 on one disk?

6. quantum fireball HDD & DMA

7. mount remote DOS disk on solaris 1 (SunOS 4.1.3_U1) ?

8. C++ on KDevelop 2.0

9. Problems with NFS Solaris 2.3 <> SunOS

10. Solaris 2.3 NFS serving SunOS 4.1.3

11. NFS compatibility SunOS & Solaris 2.3

12. mounting locally a sunos 4.1.3 disk in solaris 2.3

13. Migrating user information from SunOS 4 to Solaris 2.3 (SunOS 5.3