How to extend / file system in solaris.
varun
Pls explain both with and without SVM.
Richard B. Gilbert
> How best to di it and how safe will it be.
>
> Pls explain both with and without SVM.
Boot from the Solaris CD
Make a full backup of EACH file system on your disk.
Use format to change the sizes of the slices on your disk.
Restore your backups.
It is much better to GET THIS RIGHT THE FIRST TIME!!! Fixing it now is
going to take several hours of down time and a lot of your time!
IMHO, the minimum space for / is 4 GB and the minimum space for /var is
4 GB. You MIGHT have good reason to make either slice larger. Disk
space, especially with EIDE disks, is CHEAP. Your time is not. If your
system is business critical, downtime is not cheap either!!
Ian Collins
Or make life simple and use ZFS boot.
--
Ian Collins
ITguy
Ditto. I can't understand why some of my fellow sysadmins are so
reluctant to get on board with this...
Zfs..
ALL my new Solaris builds are with ZFS roots
It's the future.
Richard B. Gilbert
Perhaps because we know almost nothing about it?
Today or maybe yesterday is the first time I've encountered the phrase
"ZFS boot". The last I heard, ZFS was not bootable!
Does ZFS boot on SPARC hardware?
Ian Collins
It's been discussed a few times here since Update 6 was released.
> Does ZFS boot on SPARC hardware?
Yes.
See
http://docs.sun.com/app/docs/doc/819-5461/ggpdm?a=view
--
Ian Collins
Zfs..
wrote:
Yep.
Solaris u6 10/08 has the ZFS boot option
hume.sp...@bofh.ca
> Does ZFS boot on SPARC hardware?
hume> df -h /
Filesystem size used avail capacity Mounted on
rpool/ROOT/s10sparc_u6wos_07b
31G 8.9G 10G 47% /
hume> uname -a
SunOS kil-lum-3 5.10 Generic_137137-09 sun4v sparc SUNW,Sun-Fire-T200
It boots, and it is Good. This is the main feature I was looking for in U6.
--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
Thommy M.
> How best to di it and how safe will it be.
>
> Pls explain both with and without SVM.
Please do your own homework, you'll never pass the exam otherwise.
varun
:) Agreed I should have done the homework, have been fixed into other
things now-a-days.
BTW is it possible if there is a available slice and which could be
added to root slice (s0) and growfs is used then. I doubt if it ensure
the safety.
Thanks everyone for there comments!!
Richard B. Gilbert
IF, for example, the root slice is slice 0 AND IF slice one is adjacent
to slice 0 AND slice 1 has been assigned space but that space has NOT
been used, then you could, safely, add some, or all, of slice 1 to slice 0.
This sort of tinkering is NOT recommended! It is MUCH better to lay out
your disk with sufficient space in each slice to meet current and future
needs. I recommend a minimum of 4 GB for root, including /usr, and a
minimum of 4 GB for /var, 4-8 GB for swap, etc, etc. Disk space is
usually cheaper than your time and/or down time! Be generous.
Your allocation of disk space may depend on the applications you will be
running. These applications may need substantial amounts of disk space.
If you allocate disk space poorly, you will spend a LOT of time
correcting it! You will have to make a backup of the data in each
slice, run format again to change the size of the slices, restore each
slice from the backup. . . . This is not my idea of fun!! It's more
like terminal boredom, particularly if your manager is asking "When will
the system be up?" every ten or fifteen minutes.
SVM does not change disk allocation very much. If SVM is mirroring
disks, allocation will be identical to what you would have done without
SVM. If SVM has been used to create one or more RAID 5 sets, then these
RAID 5 sets will appear to be a single LARGE disk. That disk can be
divided into slices much the same as any other disk.