Re: How to convert /tmp to memfs after install
third_at_whasup.com
Date: 10/18/05
- Next message: Steve M. Fabac, Jr.: "Re: Open Server 6.0 is fragile, not ready for prime time?"
- Previous message: Bill Vermillion: "Re: /dev/lp0: cannot create error"
- In reply to: Steve M. Fabac, Jr.: "Re: How to convert /tmp to memfs after install"
- Next in thread: Bob Bailin: "Re: How to convert /tmp to memfs after install"
- Reply: Bob Bailin: "Re: How to convert /tmp to memfs after install"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 18 Oct 2005 12:03:50 +0000 (UTC)
As per Steve M. Fabac, Jr. (smfabac@att.net):
> third@whasup.com wrote:
> >
> > As per Bob Bailin (72027.3605@compuserve.com):
> >
> > >
> > > "Steve M. Fabac, Jr." <smfabac@att.net> wrote in message
> > > news:4353316A.84F6D02@att.net...
> > > >I am installing Openserver 6.0 for the first time on my test system
> > > > and blew through the file system configuration during installation
> > > > so that /tmp is on the root file system.
> > > >
> > > > I have searched the documentation without finding a solution on
> > > > how to set up /etc/vfstab to create and mount /tmp as memfs
> > > >
> > > > How do I do that without resorting to a re-installation?
> > >
> > > Agreed.
> > >
> > > man mount_memfs
> > > is not much help. It implies that you should be able to issue:
> > >
> > > mount -F memfs /tmp
> > >
> > > in order to create a memory filesystem that replaces the
> > > contents of /tmp, using the maximum value from the memory
> > > pool, but all you get is:
> > >
> > > UX:mount: ERROR: cannot determine special device
> > >
> > > (no special device is required, because it's a memfs!)
> > >
> > > Bob
> >
> > Regarding the "mount" command, try:
> >
> > /etc/fscmd.d/memfs/mount memfs MOUNT_POINT
>
>
> Wow, that sort-a-works:
> # /etc/fscmd.d/memfs/mount memfs /tmp
> # df
> / (/dev/root ): 2786668 blocks 179698 i-nodes
> /stand (/dev/boot ): 63478 blocks 10218 i-nodes
> /proc (/proc ): 0 blocks 9839 i-nodes
> /dev/fd (/dev/fd ): 0 blocks 0 i-nodes
> /dev/_tcp (/dev/_tcp ): 0 blocks 0 i-nodes
> /u (/dev/u ): 11872616 blocks 765972 i-nodes
> /app1 (/dev/app1 ): 15650076 blocks 1009671 i-nodes
> /system/processor (/processorfs ): 0 blocks 0 i-nodes
> > /tmp (memfs ): 3607960 blocks 32766 i-nodes
>
>
> # dfspace
> / : Disk space: 1360.67 MB of 3000.99 MB available (45.34%).
> /stand : Disk space: 30.99 MB of 39.99 MB available (77.49%).
> /u : Disk space: 5797.17 MB of 6000.99 MB available (96.60%).
> /app1 : Disk space: 7641.63 MB of 8137.82 MB available (93.90%).
> >/tmp : Disk space: 1760.45 MB of 1997.94 MB available (88.11%).
>
> Looks like it grabbed all available memory to create almost 2G memfs
>
> But since the system only has 1G of RAM, the above result is suspicious.
>
> Ok, that's more information (/etc/fscmd.d/memfs/mount memfs MOUNT_POINT)
> than I was able to dig from the SCO DOC's but does not duplicate the
> /tmp memfs created upon install if the option is checked during ISL.
Try this one:
mount -F memfs -o swapmax=SIZE_IN_BYTES /dev/mem MOUNT_POINT
-3-
- Next message: Steve M. Fabac, Jr.: "Re: Open Server 6.0 is fragile, not ready for prime time?"
- Previous message: Bill Vermillion: "Re: /dev/lp0: cannot create error"
- In reply to: Steve M. Fabac, Jr.: "Re: How to convert /tmp to memfs after install"
- Next in thread: Bob Bailin: "Re: How to convert /tmp to memfs after install"
- Reply: Bob Bailin: "Re: How to convert /tmp to memfs after install"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]