/ full system - Solaris

This is a discussion on / full system - Solaris ; I can not mount any devices using volume management becuase of root full system . Please guide me how to exceed the space of root or empty some of its space. # df -k Filesystem kbytes used avail capacity Mounted ...

+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 20 of 23

Thread: / full system

  1. / full system

    I can not mount any devices using volume management becuase of root
    full system . Please guide me how to exceed the space of root or empty
    some of its space.


    # df -k
    Filesystem kbytes used avail capacity Mounted on
    /dev/dsk/c1d0s0 4391670 4294028 53726 99% /
    /devices 0 0 0 0% /devices
    ctfs 0 0 0 0% /system/
    contract
    proc 0 0 0 0% /proc
    mnttab 0 0 0 0% /etc/mnttab
    swap 665588 728 664860 1% /etc/svc/
    volatile
    objfs 0 0 0 0% /system/object
    /usr/lib/libc/libc_hwcap1.so.1
    4391670 4294028 53726 99% /lib/libc.so.1
    fd 0 0 0 0% /dev/fd
    swap 664936 76 664860 1% /tmp
    swap 664892 32 664860 1% /var/run
    /dev/dsk/c1d0s7 127237310 1017608 124947329 1% /export/
    home

    # uname -a
    SunOS xerox 5.10 Generic_118855-33 i86pc i386 i86pc
    # ls
    Desktop cdrom export mnt rmdisk var
    Documents dev home net sbin vol
    TT_DB devices kernel opt system
    bin etc lib platform tmp
    boot evolution lost+found proc usr
    #

  2. Re: / full system

    happytoday wrote:
    > I can not mount any devices using volume management becuase of root
    > full system . Please guide me how to exceed the space of root or empty
    > some of its space.
    >

    Why did you create such a small root partition?

    Your best bet is to either backup and reinstall (leaving a slice for
    Live Upgrade) with sensible sizes, or move /opt (if you have much there)
    under /export and add a link.

    --
    Ian Collins.

  3. Re: / full system

    happytoday wrote:
    > I can not mount any devices using volume management becuase of root
    > full system . Please guide me how to exceed the space of root or empty
    > some of its space.
    >
    >
    > # df -k
    > Filesystem kbytes used avail capacity Mounted on
    > /dev/dsk/c1d0s0 4391670 4294028 53726 99% /
    > /devices 0 0 0 0% /devices
    > ctfs 0 0 0 0% /system/
    > contract
    > proc 0 0 0 0% /proc
    > mnttab 0 0 0 0% /etc/mnttab
    > swap 665588 728 664860 1% /etc/svc/
    > volatile
    > objfs 0 0 0 0% /system/object
    > /usr/lib/libc/libc_hwcap1.so.1
    > 4391670 4294028 53726 99% /lib/libc.so.1
    > fd 0 0 0 0% /dev/fd
    > swap 664936 76 664860 1% /tmp
    > swap 664892 32 664860 1% /var/run
    > /dev/dsk/c1d0s7 127237310 1017608 124947329 1% /export/
    > home
    >
    > # uname -a
    > SunOS xerox 5.10 Generic_118855-33 i86pc i386 i86pc
    > # ls
    > Desktop cdrom export mnt rmdisk var
    > Documents dev home net sbin vol
    > TT_DB devices kernel opt system
    > bin etc lib platform tmp
    > boot evolution lost+found proc usr
    > #


    Your problem does not appear to be lack of disk space but rather
    misallocation of space. Why the huge, and almost unused, allocation for
    /export???


    I'd say that you have three choices:
    1. Buy another, very large, disk or,
    2. Do some serious house cleaning; e.g. delete a lot of files you no
    longer need or use or,
    3. Back up your files, run format, redo the disk partitions, and restore
    your files.

    I figure that I need, on the SPARC platform, about 4 GB of space for /
    and /usr. Add another 4 GB for /var and 2 GB for swap. I have 10 GB
    allocated to the O/S as a whole. You may need more or be able to get
    along with less. YMMV.

    The last time I looked, I could buy an 80 GB EIDE drive for $70 US.
    That's a real bargain. If your system uses EIDE, just invest the $70
    plus shipping and your worries about disk space should be over. Note
    that there is a limitation in Sun EIDE controllers such that 127 GB is
    the largest disk you can use. You can install a bigger disk but you
    will only be able to use the first 127 GB!!!

    SCSI disk is a lot more expensive but, if you're going to play with the
    big boys, you should be prepared to pay the bills!


  4. Re: / full system

    On Sun, 30 Mar 2008 09:11:51 -0400, Richard B. Gilbert wrote:

    > The last time I looked, I could buy an 80 GB EIDE drive for $70 US.


    Take a new look. 160 GB drives, both SATAII and EIDE, are selling for
    under $60 USD.

    But dummy already has what appears to be a huge drive. He just accepted
    the default partitioning offered by the installer instead of using the
    experience he should have by now. Certainly he has no common sense.


  5. Re: / full system


    "happytoday" wrote in message
    news:ccfe572c-f0ff-4e7c-80c2-bc6c3c9bb0f2@z38g2000hsc.googlegroups.com...
    >I can not mount any devices using volume management becuase of root
    > full system . Please guide me how to exceed the space of root or empty
    > some of its space.
    >
    >
    > # df -k
    > Filesystem kbytes used avail capacity Mounted on
    > /dev/dsk/c1d0s0 4391670 4294028 53726 99% /
    > /devices 0 0 0 0% /devices
    > ctfs 0 0 0 0% /system/
    > contract
    > proc 0 0 0 0% /proc
    > mnttab 0 0 0 0% /etc/mnttab
    > swap 665588 728 664860 1% /etc/svc/
    > volatile
    > objfs 0 0 0 0% /system/object
    > /usr/lib/libc/libc_hwcap1.so.1
    > 4391670 4294028 53726 99% /lib/libc.so.1
    > fd 0 0 0 0% /dev/fd
    > swap 664936 76 664860 1% /tmp
    > swap 664892 32 664860 1% /var/run
    > /dev/dsk/c1d0s7 127237310 1017608 124947329 1% /export/
    > home
    >
    > # uname -a
    > SunOS xerox 5.10 Generic_118855-33 i86pc i386 i86pc
    > # ls
    > Desktop cdrom export mnt rmdisk var
    > Documents dev home net sbin vol
    > TT_DB devices kernel opt system
    > bin etc lib platform tmp
    > boot evolution lost+found proc usr
    > #


    Looks like a default partition install to me. Never did like that.

    Looks like your /export/ file system is empty. But / is full.

    So two choices, re-install with better partitioning. If this is just for
    playing around, or a personal workstation (not server) I would recommend the
    following steps when partitioning. Also adjust for you special needs.

    When partitioning, you will see an option to customize, use it.

    Select /export/home and erase its text and number value.
    Increase swap to say 4096
    Allocate all the remaining to / until it says zero free.

    For servers, I also recommend /var, keep /export/home and more but this I
    suspect is beyond scope.



  6. Re: / full system

    On Mar 30, 4:01*pm, "Canuck57" wrote:
    > "happytoday" wrote in message
    >
    > news:ccfe572c-f0ff-4e7c-80c2-bc6c3c9bb0f2@z38g2000hsc.googlegroups.com...
    >
    >
    >
    >
    >
    > >I can not mount any devices using volume management becuase of root
    > > full system . Please guide me how to exceed the space of root or empty
    > > some of its space.

    >
    > > # df -k
    > > Filesystem * * * * * *kbytes * *used * avail capacity *Mounted on
    > > /dev/dsk/c1d0s0 * * *4391670 4294028 * 53726 * *99% * */
    > > /devices * * * * * * * * * 0 * * * 0 * * *0 * * 0% * */devices
    > > ctfs * * * * * * * * * * * 0 * * * 0 * ** 0 * * 0% * */system/
    > > contract
    > > proc * * * * * * * * * * * 0 * * * 0 * ** 0 * * 0% * */proc
    > > mnttab * * * * * * * * * * 0 * * * 0 * * * 0 * * 0% * */etc/mnttab
    > > swap * * * * * * * * *665588 * * 728 *664860 ** 1% * */etc/svc/
    > > volatile
    > > objfs * * * * * * * * * * *0 * * * 0 * ** 0 * * 0% * */system/object
    > > /usr/lib/libc/libc_hwcap1.so.1
    > > * * * * * * * * * * 4391670 4294028 * 53726 * *99% * */lib/libc.so.1
    > > fd * * * * * * * * * * * * 0 * * * 0 * * * 0 * * 0% * */dev/fd
    > > swap * * * * * * * * *664936 * * *76 *664860 * * 1% * */tmp
    > > swap * * * * * * * * *664892 * * *32 *664860 * * 1% * */var/run
    > > /dev/dsk/c1d0s7 * * *127237310 1017608 124947329 * * 1% * */export/
    > > home

    >
    > > # uname -a
    > > SunOS xerox 5.10 Generic_118855-33 i86pc i386 i86pc
    > > # ls
    > > Desktop * * cdrom * * * export * * *mnt * * * * rmdisk * * *var
    > > Documents * dev * * * * home * * * *net * * * * sbin * * * *vol
    > > TT_DB * * * devices * * kernel * * *opt * * * * system
    > > bin * * * * etc * * * * lib * * * * platform **tmp
    > > boot * * * *evolution * lost+found *proc * * * *usr
    > > #

    >
    > Looks like a default partition install to me. *Never did like that.
    >
    > Looks like your /export/ file system is empty. *But / is full.
    >
    > So two choices, re-install with better partitioning. *If this is just for
    > playing around, or a personal workstation (not server) I would recommend the
    > following steps when partitioning. *Also adjust for you special needs.
    >
    > When partitioning, you will see an option to customize, use it.
    >
    > Select /export/home and erase its text and number value.
    > Increase swap to say 4096
    > Allocate all the remaining to / until it says zero free.
    >
    > For servers, I also recommend /var, keep /export/home and more but this I
    > suspect is beyond scope.- Hide quoted text -
    >
    > - Show quoted text -


    Can you figure How can I distribute 160 GB (on my hard) on all
    slices ?

  7. Re: / full system

    happytoday wrote:
    > On Mar 30, 4:01 pm, "Canuck57" wrote:
    >
    >>"happytoday" wrote in message
    >>
    >>news:ccfe572c-f0ff-4e7c-80c2-bc6c3c9bb0f2@z38g2000hsc.googlegroups.com...
    >>
    >>
    >>
    >>
    >>
    >>
    >>>I can not mount any devices using volume management becuase of root
    >>>full system . Please guide me how to exceed the space of root or empty
    >>>some of its space.

    >>
    >>># df -k
    >>>Filesystem kbytes used avail capacity Mounted on
    >>>/dev/dsk/c1d0s0 4391670 4294028 53726 99% /
    >>>/devices 0 0 0 0% /devices
    >>>ctfs 0 0 0 0% /system/
    >>>contract
    >>>proc 0 0 0 0% /proc
    >>>mnttab 0 0 0 0% /etc/mnttab
    >>>swap 665588 728 664860 1% /etc/svc/
    >>>volatile
    >>>objfs 0 0 0 0% /system/object
    >>>/usr/lib/libc/libc_hwcap1.so.1
    >>> 4391670 4294028 53726 99% /lib/libc.so.1
    >>>fd 0 0 0 0% /dev/fd
    >>>swap 664936 76 664860 1% /tmp
    >>>swap 664892 32 664860 1% /var/run
    >>>/dev/dsk/c1d0s7 127237310 1017608 124947329 1% /export/
    >>>home

    >>
    >>># uname -a
    >>>SunOS xerox 5.10 Generic_118855-33 i86pc i386 i86pc
    >>># ls
    >>>Desktop cdrom export mnt rmdisk var
    >>>Documents dev home net sbin vol
    >>>TT_DB devices kernel opt system
    >>>bin etc lib platform tmp
    >>>boot evolution lost+found proc usr
    >>>#

    >>
    >>Looks like a default partition install to me. Never did like that.
    >>
    >>Looks like your /export/ file system is empty. But / is full.
    >>
    >>So two choices, re-install with better partitioning. If this is just for
    >>playing around, or a personal workstation (not server) I would recommend the
    >>following steps when partitioning. Also adjust for you special needs.
    >>
    >>When partitioning, you will see an option to customize, use it.
    >>
    >>Select /export/home and erase its text and number value.
    >>Increase swap to say 4096
    >>Allocate all the remaining to / until it says zero free.
    >>
    >>For servers, I also recommend /var, keep /export/home and more but this I
    >>suspect is beyond scope.- Hide quoted text -
    >>
    >>- Show quoted text -

    >
    >
    > Can you figure How can I distribute 160 GB (on my hard) on all
    > slices ?



    Anybody can come up with a set of numbers. Whether those numbers are of
    any use to you is for you to decide! That being the case, you should
    probably make up your own set of numbers.

    Allocating 4 GB for / plus /usr, 4 GB for /VAR, at least 2 GB for swap,
    and 2 GB for /opt seems reasonable to me. If I knew that there would
    NEVER be an opportunity to change the partitioning, I would allocate
    still more space! I expect that you will find nearly as many different
    opinions as there are sysadmins!!!!!

    When allocating disk, remember that every patch and update you install
    is going to eat some space in / and/or /usr and /var. Be generous when
    allocating space. Remember that backing up your disk, repartioning, and
    restoring will give you a huge pain in a place where it is
    physiologically impossible to have a toothache! Disk is cheap, your
    time is not and down time may not be cheap either.


  8. Re: / full system


    "happytoday" wrote in message
    news:9afec656-6fe9-4085-891a-51297c07fa77@b5g2000pri.googlegroups.com...
    On Mar 30, 4:01 pm, "Canuck57" wrote:
    > "happytoday" wrote in message
    >
    > news:ccfe572c-f0ff-4e7c-80c2-bc6c3c9bb0f2@z38g2000hsc.googlegroups.com...
    >
    >
    >
    >
    >
    > >I can not mount any devices using volume management becuase of root
    > > full system . Please guide me how to exceed the space of root or empty
    > > some of its space.

    >
    > > # df -k
    > > Filesystem kbytes used avail capacity Mounted on
    > > /dev/dsk/c1d0s0 4391670 4294028 53726 99% /
    > > /devices 0 0 0 0% /devices
    > > ctfs 0 0 0 0% /system/
    > > contract
    > > proc 0 0 0 0% /proc
    > > mnttab 0 0 0 0% /etc/mnttab
    > > swap 665588 728 664860 1% /etc/svc/
    > > volatile
    > > objfs 0 0 0 0% /system/object
    > > /usr/lib/libc/libc_hwcap1.so.1
    > > 4391670 4294028 53726 99% /lib/libc.so.1
    > > fd 0 0 0 0% /dev/fd
    > > swap 664936 76 664860 1% /tmp
    > > swap 664892 32 664860 1% /var/run
    > > /dev/dsk/c1d0s7 127237310 1017608 124947329 1% /export/
    > > home

    >
    > > # uname -a
    > > SunOS xerox 5.10 Generic_118855-33 i86pc i386 i86pc
    > > # ls
    > > Desktop cdrom export mnt rmdisk var
    > > Documents dev home net sbin vol
    > > TT_DB devices kernel opt system
    > > bin etc lib platform tmp
    > > boot evolution lost+found proc usr
    > > #

    >
    > Looks like a default partition install to me. Never did like that.
    >
    > Looks like your /export/ file system is empty. But / is full.
    >
    > So two choices, re-install with better partitioning. If this is just for
    > playing around, or a personal workstation (not server) I would recommend
    > the
    > following steps when partitioning. Also adjust for you special needs.
    >
    > When partitioning, you will see an option to customize, use it.
    >
    > Select /export/home and erase its text and number value.
    > Increase swap to say 4096
    > Allocate all the remaining to / until it says zero free.
    >
    > For servers, I also recommend /var, keep /export/home and more but this I
    > suspect is beyond scope.- Hide quoted text -
    >
    > - Show quoted text -


    Can you figure How can I distribute 160 GB (on my hard) on all
    slices ?
    ------
    Go find a good book or PDF on planning and deployment. Read it.



  9. Re: / full system

    On Mar 30, 7:03 am, happytoday wrote:

    > > >I can not mount any devices using volume management becuase of root
    > > > full system . Please guide me how to exceed the space of root or empty
    > > > some of its space.
    > > > # df -k
    > > > Filesystem kbytes used avail capacity Mounted on
    > > > /dev/dsk/c1d0s0 4391670 4294028 53726 99% /
    > > > /dev/dsk/c1d0s7 127237310 1017608 124947329 1% /export/home
    > > > # uname -a
    > > > SunOS xerox 5.10 Generic_118855-33 i86pc i386 i86pc


    For shame. Utterly trivial to reason this out without input from
    others.
    Plus, you can search the archives where this subject has been well
    discussed.
    Third, the install gives you the choice to carve your own slices which
    suggests you dont even read whats in front of you during the install
    process.
    I really believe you have the brains to accomplish many of the things
    you ask about
    but appear to be too lazy to bother trying. If not then consider
    taking some
    courses or another line of work maybe : /

  10. Re: / full system

    On Mar 30, 2:33*am, happytoday wrote:
    > I can not mount any devices using volume management becuase of root
    > full system . Please guide me how to exceed the space of root or empty
    > some of its space.
    >
    > # df -k
    > Filesystem * * * * * *kbytes * *used * avail capacity *Mounted on
    > /dev/dsk/c1d0s0 * * *4391670 4294028 * 53726 * *99% * */
    > /devices * * * * * * * * * 0 * * * 0 * * * 0* * 0% * */devices
    > ctfs * * * * * * * * * * * 0 * * * 0 * * * 0 * * 0% * */system/
    > contract
    > proc * * * * * * * * * * * 0 * * * 0 * * * 0 * * 0% * */proc
    > mnttab * * * * * * * * * * 0 * * * 0 * * *0 * * 0% * */etc/mnttab
    > swap * * * * * * * * *665588 * * 728 *664860 * * 1% * */etc/svc/
    > volatile
    > objfs * * * * * * * * * * *0 * * * 0 * * * 0 * * 0% * */system/object
    > /usr/lib/libc/libc_hwcap1.so.1
    > * * * * * * * * * * *4391670 4294028 * 53726 * *99% * */lib/libc.so.1
    > fd * * * * * * * * * * * * 0 * * * 0 * ** 0 * * 0% * */dev/fd
    > swap * * * * * * * * *664936 * * *76 *664860 ** 1% * */tmp
    > swap * * * * * * * * *664892 * * *32 *664860 ** 1% * */var/run
    > /dev/dsk/c1d0s7 * * *127237310 1017608 124947329 * * 1% * */export/
    > home
    >
    > # uname -a
    > SunOS xerox 5.10 Generic_118855-33 i86pc i386 i86pc
    > # ls
    > Desktop * * cdrom * * * export * * *mnt * * * * rmdisk * * *var
    > Documents * dev * * * * home * * * *net * * * * sbin * * * *vol
    > TT_DB * * * devices * * kernel * * *opt * * * * system
    > bin * * * * etc * * * * lib * * * * platform * *tmp
    > boot * * * *evolution * lost+found *proc * * * *usr
    > #


    If you don't need staroffice remove these packages:
    SUNWsogm and SUNWsom

    You'll get about 500MB back.

    But yeah, that is a bad partition layout unless you are really
    tweaking your
    Solaris install

  11. Re: / full system


    "Dave Uhring" wrote in message newsan.2008.03.30.13.58.57.584940@yahoo.com...
    >
    > ... already has what appears to be a huge drive. He just accepted
    > the default partitioning offered by the installer instead of using the
    > experience he should have by now. Certainly he has no common sense.
    >


    Heaven forfend that the default should be reasonable.

    The OP should perhaps have a quick look in /var for any large log files
    that are not being rotated (and compressed). Could /opt be moved to
    a separate (loopback mounted rather than symbolically linked) filesystem?
    And is /home being used correctly as a mounting point for /export/home
    or are there real directories taking up space in there?

    But yes, like everyone else says, repartition.

    --
    John.



  12. Re: / full system

    On Mon, 31 Mar 2008 04:50:23 +0100, John L wrote:

    >
    > "Dave Uhring" wrote in message newsan.2008.03.30.13.58.57.584940@yahoo.com...
    >>
    >> ... already has what appears to be a huge drive. He just accepted
    >> the default partitioning offered by the installer instead of using the
    >> experience he should have by now. Certainly he has no common sense.
    >>

    >
    > Heaven forfend that the default should be reasonable.


    The OP has been posting here for years. Clearly he has sufficient
    experience to have *known* that the default was inadequate. He even
    claims to be his local expert, teaching other Solaris sysadmins.

    > The OP should perhaps have a quick look in /var for any large log files
    > that are not being rotated (and compressed). Could /opt be moved to a
    > separate (loopback mounted rather than symbolically linked) filesystem?
    > And is /home being used correctly as a mounting point for /export/home
    > or are there real directories taking up space in there?


    Or just pkgrm staroffice7. But none of this solves his problem. A
    shortage of space on his HDD does not prevent mounting removable media.

    > But yes, like everyone else says, repartition.


    Or just get a brain.


  13. Re: / full system

    Dave Uhring wrote:
    > On Mon, 31 Mar 2008 04:50:23 +0100, John L wrote:
    >
    >> "Dave Uhring" wrote in message newsan.2008.03.30.13.58.57.584940@yahoo.com...
    >>> ... already has what appears to be a huge drive. He just accepted
    >>> the default partitioning offered by the installer instead of using the
    >>> experience he should have by now. Certainly he has no common sense.
    >>>

    >> Heaven forfend that the default should be reasonable.

    >
    > The OP has been posting here for years. Clearly he has sufficient
    > experience to have *known* that the default was inadequate. ...


    While all that is true, the default really should be redone to better
    reflect modern software requirements and disk sizes. The fact that
    any experienced (or at least well-read) SA should know of this problem
    and the obvious work-around, doesn't excuse having out-dated
    defaults. This is especially true with OpenSolaris, as a lot of
    newbies will install it and accept all defaults, as they should
    be able to.

    -Wayne

  14. Re: / full system

    Wayne wrote:
    > Dave Uhring wrote:
    >> On Mon, 31 Mar 2008 04:50:23 +0100, John L wrote:
    >>
    >>> "Dave Uhring" wrote in message
    >>> newsan.2008.03.30.13.58.57.584940@yahoo.com...
    >>>> ... already has what appears to be a huge drive. He just accepted
    >>>> the default partitioning offered by the installer instead of using the
    >>>> experience he should have by now. Certainly he has no common sense.
    >>>>
    >>> Heaven forfend that the default should be reasonable.

    >>
    >> The OP has been posting here for years. Clearly he has sufficient
    >> experience to have *known* that the default was inadequate. ...

    >
    > While all that is true, the default really should be redone to better
    > reflect modern software requirements and disk sizes. The fact that
    > any experienced (or at least well-read) SA should know of this problem
    > and the obvious work-around, doesn't excuse having out-dated
    > defaults. This is especially true with OpenSolaris, as a lot of
    > newbies will install it and accept all defaults, as they should
    > be able to.
    >

    The new installer for SXDE does use more sensible defaults.

    --
    Ian Collins.

  15. Re: / full system

    On Mon, 31 Mar 2008 19:44:47 -0400, Wayne wrote:

    > Dave Uhring wrote:


    >> The OP has been posting here for years. Clearly he has sufficient
    >> experience to have *known* that the default was inadequate. ...

    >
    > While all that is true, the default really should be redone to better
    > reflect modern software requirements and disk sizes. The fact that
    > any experienced (or at least well-read) SA should know of this problem
    > and the obvious work-around, doesn't excuse having out-dated
    > defaults. This is especially true with OpenSolaris, as a lot of
    > newbies will install it and accept all defaults, as they should
    > be able to.


    If that's done then they will also disable customization of partition
    sizes for the people who do have a clue. Just look what those idiotic GUI
    installers for Solaris have done for years. The ones for Nevada have been
    even worse than Solaris 10 in this respect; the sysadmin gets *no* choice
    in his partitioning.

    At least we can still avoid the useless eye candy and get on about a
    proper job of installation.


  16. Re: / full system

    Dave Uhring wrote:
    > On Mon, 31 Mar 2008 19:44:47 -0400, Wayne wrote:
    >
    >> Dave Uhring wrote:

    >
    >>> The OP has been posting here for years. Clearly he has sufficient
    >>> experience to have *known* that the default was inadequate. ...

    >> While all that is true, the default really should be redone to better
    >> reflect modern software requirements and disk sizes. The fact that
    >> any experienced (or at least well-read) SA should know of this problem
    >> and the obvious work-around, doesn't excuse having out-dated
    >> defaults. This is especially true with OpenSolaris, as a lot of
    >> newbies will install it and accept all defaults, as they should
    >> be able to.

    >
    > If that's done then they will also disable customization of partition
    > sizes for the people who do have a clue. Just look what those idiotic GUI
    > installers for Solaris have done for years. The ones for Nevada have been
    > even worse than Solaris 10 in this respect; the sysadmin gets *no* choice
    > in his partitioning.
    >

    Use console mode, which offers all the customisation options. Remember
    the new installer is a WIP. If you have constructive suggestions to
    offer, subscribe to the opensolaris installer lists.

    --
    Ian Collins.

  17. Re: / full system

    Wayne wrote:
    > Dave Uhring wrote:
    >
    >> On Mon, 31 Mar 2008 04:50:23 +0100, John L wrote:
    >>
    >>> "Dave Uhring" wrote in message
    >>> newsan.2008.03.30.13.58.57.584940@yahoo.com...
    >>>
    >>>> ... already has what appears to be a huge drive. He just accepted
    >>>> the default partitioning offered by the installer instead of using the
    >>>> experience he should have by now. Certainly he has no common sense.
    >>>>
    >>> Heaven forfend that the default should be reasonable.

    >>
    >>
    >> The OP has been posting here for years. Clearly he has sufficient
    >> experience to have *known* that the default was inadequate. ...

    >
    >
    > While all that is true, the default really should be redone to better
    > reflect modern software requirements and disk sizes. The fact that
    > any experienced (or at least well-read) SA should know of this problem
    > and the obvious work-around, doesn't excuse having out-dated
    > defaults. This is especially true with OpenSolaris, as a lot of
    > newbies will install it and accept all defaults, as they should
    > be able to.
    >
    > -Wayne


    My understanding is that "OpenSolaris" lets you "roll your" own and add
    it to the code base.

    Let's design a reasonable set of defaults. Assume, for the sake of
    argument, that the smallest possible disk is 10 GB. I suppose you could
    shoe horn Solaris into something smaller than that, but for most users
    these days 10 GB is a tiny disk! Also assume that we are doing a full
    install (SUNWCxall).

    How should the layout be defaulted on a 10 GB disk? If we assume a 20
    GB disk, how should it be defaulted? A 40 GB disk? An 80 GB disk? For
    the 10 GB disk, I propose 4GB for / plus /usr, 2 GB for /var, 2 Gb for
    swap, and 2 GB for /export.

    How do we want to default the size of swap? It depends on both the
    available RAM and the amount of disk space we can afford to devote to
    swap. Shall we assume a minimum of 512 MB for swap? Or can we get away
    with 256 MB or even less?

    Comments anyone?


  18. Re: / full system

    Richard B. Gilbert wrote:
    >
    > My understanding is that "OpenSolaris" lets you "roll your" own and add
    > it to the code base.
    >
    > Let's design a reasonable set of defaults. Assume, for the sake of
    > argument, that the smallest possible disk is 10 GB. I suppose you could
    > shoe horn Solaris into something smaller than that, but for most users
    > these days 10 GB is a tiny disk! Also assume that we are doing a full
    > install (SUNWCxall).
    >
    > How should the layout be defaulted on a 10 GB disk? If we assume a 20
    > GB disk, how should it be defaulted? A 40 GB disk? An 80 GB disk? For
    > the 10 GB disk, I propose 4GB for / plus /usr, 2 GB for /var, 2 Gb for
    > swap, and 2 GB for /export.
    >

    This was all nutted out on the OpenSolaris caiman-discuss list last
    year. Search for a thread "default VTOC layout in dwarf caiman"

    --
    Ian Collins.

  19. Re: / full system

    On 2008-04-01 00:55:04 +0100, Ian Collins said:

    > The new installer for SXDE does use more sensible defaults.


    .... and the installer for Indiana avoids the issue altogether by using ZFS.

    But I'll grant that an installer than can sensibly default UFS
    partition sizes is a highly useful thing.

    Cheers,

    Chris


  20. Re: / full system

    Chris Ridd wrote:
    > On 2008-04-01 00:55:04 +0100, Ian Collins said:
    >
    >> The new installer for SXDE does use more sensible defaults.

    >
    > .... and the installer for Indiana avoids the issue altogether by using
    > ZFS.
    >

    It looks like we will have ZFS install support in SXCE within a couple
    of months.

    --
    Ian Collins.

+ Reply to Thread
Page 1 of 2 1 2 LastLast