[indiana-discuss] Default Partitions sizes

Sanjay Nadkarni Sanjay.Nadkarni at sun.com
Thu Oct 4 14:16:50 PDT 2007


This will be a non-issue for Indiana. Our plan for the first prototype 
release in October is assign the entire fdisk partition  to a zfs pool. 
It will be set up as a mirrored pool.  A user will have to add the 
second disk. There will be datasets for /usr, /opt, /export, etc.   Swap 
will be on a zvol.    I would love to have feedback on this.

So it will look something like this:

<indiana-build> zpool status                                     
  pool: mypool
  state: ONLINE
  scrub: scrub completed with 0 errors on Wed Sep 26 23:41:40 2007
  config:

         NAME          STATE     READ WRITE CKSUM
         mypool        ONLINE       0     0     0
           mirror      ONLINE       0     0     0
             c3t0d0s0  ONLINE       0     0     0

errors: No known data errors

Filesystem             size   used  avail capacity  Mounted on
mypool/BE1             134G    16G    83G    17%    /
/devices                 0K     0K     0K     0%    /devices
/dev                     0K     0K     0K     0%    /dev
ctfs                     0K     0K     0K     0%    /system/contract
proc                     0K     0K     0K     0%    /proc
mnttab                   0K     0K     0K     0%    /etc/mnttab
swap                   496M   888K   495M     1%    /etc/svc/volatile
objfs                    0K     0K     0K     0%    /system/object
sharefs                  0K     0K     0K     0%    /etc/dfs/sharetab
mypool/BE1/usr         134G   3.4G    83G     4%    /usr
/usr/lib/libc/libc_hwcap2.so.1

                        87G   3.4G    83G     4%    /lib/libc.so.1
fd                       0K     0K     0K     0%    /dev/fd

mypool/BE1/var         134G   1.3G    83G     2%    /var
swap                   522M    27M   495M     6%    /tmp
swap                   495M    40K   495M     1%    /var/run
mypool/BE1/opt         134G   1.4G    83G     2%    /opt
mypool/BE1/export      134G   1.5G    83G     2%    /export


BTW, all UFS file system on Nevada have logging on by default.   For ZFS 
journaling is not required

-Sanjay


Peter Tribble wrote:
> On 10/4/07, Dev Mazumdar <dev at opensound.com> wrote:
>   
>> I absolutely hate Solaris's default partitions - 1 small root 1 small swap and a huge freakin /export/home.
>>
>> The problem is that when you install dev tools and other Blastwave apps, they all go into /opt (or /usr/local) and you're pretty much screwed out of space in /tmp as well. So now none of your compiling or editors have space for temp files.
>>
>> My suggestion for Indiana is now that we have journaling turned on, why not have  1 swap partition = 2-4 x real memory and the rest allocated to root. We no longer need to worry about running out of disk space and having to install programs in other directories only to find out that they sometimes don't behave properly if they aren't installed in their "default" directory (usually /usr/local or /opt)
>>     
>
> We had a discussion over in sysadmin-discuss recently:
>
> http://www.opensolaris.org/jive/thread.jspa?threadID=39882&tstart=15
>
> (which I ought to write up a summary for) which basically goes along
> with the 'keep it simple' approach.
>
> And, you'll note that there was a contribution regarding the standards
> that Sun use to build preinstalled systems, excerpted here:
>
> http://wikis.sun.com/display/BigAdmin/BootDiskLayout
>
> although that's fairly recent.
>
>   



More information about the indiana-discuss mailing list