When I am using VI to edit a file, I get message "no space left on device".
Is there any way to expand /var file system ?

/export/home/oracle/schwarz >> df -h
Filesystem             size   used  avail capacity  Mounted on
/dev/dsk/c0t0d0s0      204M   109M    74M    60%    /
/devices                 0K     0K     0K     0%    /devices
ctfs                     0K     0K     0K     0%    /system/contract
proc                     0K     0K     0K     0%    /proc
mnttab                   0K     0K     0K     0%    /etc/mnttab
swap                   638M   376K   638M     1%    /etc/svc/volatile
objfs                    0K     0K     0K     0%    /system/object
/dev/dsk/c0t0d0s6      3.6G   2.5G   1.1G    70%    /usr
fd                       0K     0K     0K     0%    /dev/fd
/dev/dsk/c0t0d0s3       87M    84M     0K   100%    /var
swap                   638M    32K   638M     1%    /var/run
swap                   638M     0K   638M     0%    /tmp
/dev/dsk/c0t0d0s5      188M    79M    90M    47%    /opt
/dev/dsk/c0t0d0s7       14G    53M    13G     1%    /export/home
/dev/dsk/c0t0d0s1      577M   394M   125M    76%    /usr/openwin
/export/home/oracle/schwarz >>

On Fri, 11 Mar 2005 10:30:19 -0800, Shiva MahaDeva wrote:

> When I am using VI to edit a file, I get message "no space left on device".
> Is there any way to expand /var file system ?

> /dev/dsk/c0t0d0s3       87M    84M     0K   100%    /var

> /dev/dsk/c0t0d0s7       14G    53M    13G     1%    /export/home

# mkdir /export/home/tmp
# chmod 1777 /export/home/tmp
# rm -rf /var/tmp
# ln -s /export/home/tmp /var/tmp

On Fri, 11 Mar 2005, Shiva MahaDeva wrote:

> When I am using VI to edit a file, I get message "no space left on device".
> Is there any way to expand /var file system ?

Dave Uhring's post explains how to do this, but intrigues me is why the
file systems are set up the way they are in the first place...

-- 
Rich Teer, SCNA, SCSA

President,
Rite Online Inc.

Voice: +1 (250) 979-1638
URL: http://www.rite-group.com/rich

Rich Teer <rich.teer@rite-group.com> writes:

> On Fri, 11 Mar 2005, Shiva MahaDeva wrote:
>
>> When I am using VI to edit a file, I get message "no space left on device".
>> Is there any way to expand /var file system ?
>
> Dave Uhring's post explains how to do this, but intrigues me is why the
> file systems are set up the way they are in the first place...

Funny, haven't seen a system with a separate /usr/openwin slice for quite a
while

  /dev/dsk/c0t0d0s1      577M   394M   125M    76%    /usr/openwin


Bye, Dragan

-- 
Dragan Cvetkovic, 

To be or not to be is true. G. Boole      No it isn't.  L. E. J. Brouwer

!!! Sender/From address is bogus. Use reply-to one !!!

Dragan Cvetkovic wrote:
> Rich Teer <rich.teer@rite-group.com> writes:
> 
> 
>>On Fri, 11 Mar 2005, Shiva MahaDeva wrote:
>>
>>
>>>When I am using VI to edit a file, I get message "no space left on device".
>>>Is there any way to expand /var file system ?
>>
>>Dave Uhring's post explains how to do this, but intrigues me is why the
>>file systems are set up the way they are in the first place...
> 
> 
> Funny, haven't seen a system with a separate /usr/openwin slice for quite a
> while
> 
>   /dev/dsk/c0t0d0s1      577M   394M   125M    76%    /usr/openwin
> 
> 
> Bye, Dragan
> 

Isn't /usr/openwin one of the "suggested" slices that the installer 
still creates if one doesn't know any better and actually lets it try 
to lay out disks?


-- 
Coy Hile
hile@cse.psu.edu

Coy Hile <hile@cse.psu.edu> writes:

> Dragan Cvetkovic wrote:
>> Rich Teer <rich.teer@rite-group.com> writes:
>>
>>>On Fri, 11 Mar 2005, Shiva MahaDeva wrote:
>>>
>>>
>>>>When I am using VI to edit a file, I get message "no space left on device".
>>>>Is there any way to expand /var file system ?
>>>
>>>Dave Uhring's post explains how to do this, but intrigues me is why the
>>>file systems are set up the way they are in the first place...
>> Funny, haven't seen a system with a separate /usr/openwin slice for quite
>> a
>> while
>>   /dev/dsk/c0t0d0s1      577M   394M   125M    76%    /usr/openwin
>> Bye, Dragan
>>
>
> Isn't /usr/openwin one of the "suggested" slices that the installer still
> creates if one doesn't know any better and actually lets it try to lay out
> disks?

Is it? Haven't used the "suggested" layout for quite a while ...

Bye, Dragan

-- 
Dragan Cvetkovic, 

To be or not to be is true. G. Boole      No it isn't.  L. E. J. Brouwer

!!! Sender/From address is bogus. Use reply-to one !!!

Dragan Cvetkovic wrote:
> Coy Hile <hile@cse.psu.edu> writes:
>>Isn't /usr/openwin one of the "suggested" slices that the installer still
>>creates if one doesn't know any better and actually lets it try to lay out
>>disks?
> 
> 
> Is it? Haven't used the "suggested" layout for quite a while ...
> 

I'll go one further.  I don't think I have ever used it.


-- 
Coy Hile
hile@cse.psu.edu

Coy Hile <hile@cse.psu.edu> wrote:
> Dragan Cvetkovic wrote:
>> Funny, haven't seen a system with a separate /usr/openwin slice for quite a
>> while
>> 
>>   /dev/dsk/c0t0d0s1      577M   394M   125M    76%    /usr/openwin
>> 
>> 
>> Bye, Dragan
>> 

> Isn't /usr/openwin one of the "suggested" slices that the installer 
> still creates if one doesn't know any better and actually lets it try 
> to lay out disks?

I believe it's available in the sense of having a checkbox, so you can
make it a separate slice.

But the default for "suggested layout" (on sufficiently large disks) is
just root, swap, and /export/home.  I suppose on smaller disks it might
make different suggestions.

-- 
Darren Dunham                                           ddunham@taos.com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

Dave Uhring wrote:
> > When I am using VI to edit a file, I get message "no space left on device".
> > Is there any way to expand /var file system ?
> 
> > /dev/dsk/c0t0d0s3       87M    84M     0K   100%    /var
> 
> > /dev/dsk/c0t0d0s7       14G    53M    13G     1%    /export/home
> 
> # mkdir /export/home/tmp
> # chmod 1777 /export/home/tmp
> # rm -rf /var/tmp
> # ln -s /export/home/tmp /var/tmp

Ouch ouch ouch. Please do not use symlinks here - this blows-up some
scripts. Better use "lofs" here.

Example entry for /etc/vfstab (for having content in /opt stored
physically on /exports/opt/):
-- snip --
/export/opt   /opt   lofs  1   yes   -
-- snip --

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz@nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)

Roland Mainz wrote:
> > > When I am using VI to edit a file, I get message "no space left on device".
> > > Is there any way to expand /var file system ?
> >
> > > /dev/dsk/c0t0d0s3       87M    84M     0K   100%    /var
> >
> > > /dev/dsk/c0t0d0s7       14G    53M    13G     1%    /export/home
> >
> > # mkdir /export/home/tmp
> > # chmod 1777 /export/home/tmp
> > # rm -rf /var/tmp
> > # ln -s /export/home/tmp /var/tmp
> 
> Ouch ouch ouch. Please do not use symlinks here - this blows-up some
> scripts. Better use "lofs" here.
> 
> Example entry for /etc/vfstab (for having content in /opt stored
> physically on /exports/opt/):
> -- snip --
> /export/opt   /opt   lofs  1   yes   -
> -- snip --

BTW: A more detailed description can be found under
http://groups.google.de/groups?q=%22roland+mainz%22+lofs+/etc/vfstab+mkdir&hl=de&lr=&ie=UTF-8&selm=40B17D66.48161C8B%40nrubsig.org&rnum=2
....

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz@nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)

On Fri, 11 Mar 2005 23:38:28 +0100, Roland Mainz wrote:

> Dave Uhring wrote:

>> # mkdir /export/home/tmp
>> # chmod 1777 /export/home/tmp
>> # rm -rf /var/tmp
>> # ln -s /export/home/tmp /var/tmp
> 
> Ouch ouch ouch. Please do not use symlinks here - this blows-up some
> scripts. Better use "lofs" here.
> 
> Example entry for /etc/vfstab (for having content in /opt stored
> physically on /exports/opt/):
> -- snip --
> /export/opt   /opt   lofs  1   yes   -
> -- snip --

You are missing an entry here.  /etc/vfstab has 7 columns.

Shiva MahaDeva wrote:
> When I am using VI to edit a file, I get message "no space left on device".
> Is there any way to expand /var file system ?
> 
> /export/home/oracle/schwarz >> df -h
> Filesystem             size   used  avail capacity  Mounted on
> /dev/dsk/c0t0d0s0      204M   109M    74M    60%    /
> /devices                 0K     0K     0K     0%    /devices
> ctfs                     0K     0K     0K     0%    /system/contract
> proc                     0K     0K     0K     0%    /proc
> mnttab                   0K     0K     0K     0%    /etc/mnttab
> swap                   638M   376K   638M     1%    /etc/svc/volatile
> objfs                    0K     0K     0K     0%    /system/object
> /dev/dsk/c0t0d0s6      3.6G   2.5G   1.1G    70%    /usr
> fd                       0K     0K     0K     0%    /dev/fd
> /dev/dsk/c0t0d0s3       87M    84M     0K   100%    /var
> swap                   638M    32K   638M     1%    /var/run
> swap                   638M     0K   638M     0%    /tmp
> /dev/dsk/c0t0d0s5      188M    79M    90M    47%    /opt
> /dev/dsk/c0t0d0s7       14G    53M    13G     1%    /export/home
> /dev/dsk/c0t0d0s1      577M   394M   125M    76%    /usr/openwin
> /export/home/oracle/schwarz >>

Maybe an easier solution to your problem is to point vi's scratch directory
to somewhere with more space. You can do it a couple of ways. One is to create
a file called .exrc in your home directory. Add a line to this file that reads:

set directory=/path/to/directory_with_enough_space

Upon startup vi looks for this file to set its defaults.

A second way is to fire up vi (without the filename) then do the following
:set directory=/path/to/directory_with_enough_space
:e FileNameToEdit

-- 
----------------------------------
Randy Jones
E-Mail: randy@jones.tri.net
----------------------------------

Dave Uhring wrote:
> >> # mkdir /export/home/tmp
> >> # chmod 1777 /export/home/tmp
> >> # rm -rf /var/tmp
> >> # ln -s /export/home/tmp /var/tmp
> >
> > Ouch ouch ouch. Please do not use symlinks here - this blows-up some
> > scripts. Better use "lofs" here.
> >
> > Example entry for /etc/vfstab (for having content in /opt stored
> > physically on /exports/opt/):
> > -- snip --
> > /export/opt   /opt   lofs  1   yes   -
> > -- snip --
> 
> You are missing an entry here.  /etc/vfstab has 7 columns.

Ouch - that usually happens when I try to write an reply at 1:00am...
;-(
http://groups.google.de/groups?q=%22roland+mainz%22+lofs+/etc/vfstab+mkdir&hl=de&lr=&ie=UTF-8&selm=40B17D66.48161C8B%40nrubsig.org&rnum=2
has a better (and hopefully correct) description...

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz@nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)