i am working with solaris 9 and my disk usages are

# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 2148263 1902721 202577 91% /
/proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
fd 0 0 0 0% /dev/fd
swap 371992 32 371960 1% /var/run
swap 372272 312 371960 1% /tmp
/dev/dsk/c0t0d0s7 36317277 86239 35867866 1% /export/home


means c0t0d0s0 had been filled by 91% and c0t0d0s7 is only 1%.

So my question is that can I increase the space of c0t0d0s0 by distracting it from c0t0d0s7 ??

is it then how can I do it ??

thanks in advance...

You can, but you'll probably lose all the data in /export/home when you re-write the partition table. I'd look in / first, since you've probably got all your log files and everything else under it, based on this, and see what you can remove. You can probably free up a good amount of space.

This page http://devnull.typepad.com/devnull/2...is-how-to.html can give you some tips, but be SURE you have a GOOD backup first.

Here is one way to do it:
create /export/home-slash
move /export/home/* to /export/home-slash
unmount /export/home
remove /export/home from vfstab
remove /export/home directory
rename /export/home-slash to /export/home
save the disk vtoc to an external media just in case
boot on an installation CD/DVD and launch a shell from it
move all data from slice 0 to slice 7 with dd
extract the disk vtoc to a file
edit the file and swap slice 0 and slice 7
overwrite the disk vtoc
reboot ...
If everything is ok, create a new filesytem on slice 7, a mount point for it and add it to your vfstab

Of course, this is quite tricky and there are several steps where mistakes can be disastrous for all of your data.

Alternatively, could merge slice 7 to slice 0 and growfs while on the boot shell.

Finally, if you have external storage space, backup (ufsdump) both of your slices, recreate a single one and restore from the backup.

Can you remove or /dev/null some files under /var/tmp or logs under /var/adm /var/log to free up some space? Any other logs? 40GB is a lot for a solaris install. Even with the second largest install option you can do it for far less than 20GB. Sounds like you might be able to get yourself temporarily out of trouble by cleaning up logs and stuff. Can't hurt to look for core files and that sort of thing too.

-Raymond

According to df output, the OP has Solaris installed on 1.9 GB, not 40 GB. I doubt much space is wasted there.

Oops, brain fart, I registered some bad info in my head from the duplicate thread here.

-Raymond