Hello,
I have a x86 Solaris server running on VMWare. c1t0d0 is root disk of 40 GB. I am not able to find, where space is being consumed. It just available space is 2.6 GB only. There is no quota or reservation set. Can somebody give me some pointer to fix it ?
Thanks
Hi
I'm using HP-UX 11.00, the root file system is as shown below. Several time it reach 100% used, to free some space I use to reboot the system. What can I do to free some space without rebooting the machine?
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 ... (2 Replies)
Hi everybody,
I got a problem on my SUN server in Solaris 9. I'll try to explain, if somebody could help me.
I have mounted some volumes in RAID 0+1, that is stripped slices and then mirror. To be clear the result of metastat d80 is as follow :
d80: Mirror
Submirror 0: d81
State:... (2 Replies)
dear all,
I have some problem in my file system :
df -k result :
...
/dev/md/dsk/d3 3101839 2736380 303423 91% /var
...
it occupied around 2.7 gb
but when I tried command
du -sk /var
813991 /var
so /var only have around 800Mb , Do you know why there is many difference... (6 Replies)
Hello,
Can anybody please tell me the command to find out the filesystem or a file which is consuming larger disk space sing i want to find out the file and want to compress it
please help me out
any help would be appreciated (6 Replies)
Hi guys,
I'm trying to get free space in GB of file system into parameter.
I have the following code:
> cat get_free_space_FS.ksh
#! /bin/ksh
FS=/dw/mar
FreeSpace=`df -h | grep $FS | awk '{print $4}'`
echo $FreeSpace
> ./get_free_space_FS.ksh
362G
My question is ,how can I cut in... (4 Replies)
have a VMWARE machine, I have extended it from 20GB to 30GB for Linux box.
The linux box shows this for df -hal:
Filesystem Size Used Avail Use% Mounted on
-dev-mapper-VolGroup00-LogVol00
19G 5.9G 12G 34% -
proc 0 0 0 - -proc
sysfs 0 0 0 - -sys
devpts 0 0 0 - -dev-pts
-dev-sda1 99M 13M... (1 Reply)
Hi,
The solaris filesystem /u01 shows available space as 100GB, and used space as 6 GB.
The Problem is when iam trying to install some software or copy some files in this file system /u01 Iam unable to copy or install in this file system due to lack of space.
ofcourse the software... (31 Replies)
Hi Friends,
I want to cut space from one file system and add in another file system.
For example I have 100 gb space in /oracle/TST/oraarch
I wnat to cut 50 gb from this file system and add 50 in /oracle/TST/sapdata1.
Please hel, How I can do it.
Regards,
Bhagawati Pandey (3 Replies)
Hi Experts,
I have query regarding output of df command.
$ df -k
Filesystem 1024-blocks Used Available Capacity Mounted on
rpool/ROOT/solaris-161 191987712 6004395 140577816 5% /
/devices 0 0 0 0% /devices... (3 Replies)
A file system has reached 100%. I have tried adding space using chfs -a size=+100 command to that file system. However, the % used is not decreasing from 100%. Is there a way to add more space?
Also, can someone suggest a script to send a mail alert when a file system is reaching 90%.
G (4 Replies)
Discussion started by: ggayathri
4 Replies
LEARN ABOUT OPENSOLARIS
reboot
reboot(1M) System Administration Commands reboot(1M)NAME
reboot - restart the operating system
SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments]
/usr/sbin/reboot [-f [-e environment]] [-dlnq] [boot_arguments]
DESCRIPTION
The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel.
On x86 systems, when the -f flag is specified, the running kernel will load the next kernel into memory, then transfer control to the newly
loaded kernel. This form of reboot is shown in the second synopsis, above.
Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending
loss of service. See shutdown(1M) for details.
The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On x86
systems, reboot may also update the boot archive as needed to ensure a successful reboot.
The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting
file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present.
Normally, the system reboots itself at power-up or after crashes.
OPTIONS
The following options are supported:
-d
Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps.
-e
If -f is present, reboot to the specified boot environment.
-f
Fast reboot, bypassing firmware and boot loader. The new kernel will be loaded into memory by the running kernel, and control will be
transferred to the newly loaded kernel. If disk or kernel arguments are specified, they must be specified before other boot arguments.
This option is currently available only on x86 systems.
See EXAMPLES for details.
-l
Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot.
-n
Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync filesystems
prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to sync filesystems.
-q
Quick. Reboot quickly and ungracefully, without shutting down running processes first.
OPERANDS
The following operands are supported:
boot_arguments
An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel upon restart.
The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are specified, whitespace
between them is replaced by single spaces unless the whitespace is quoted for the shell. If the boot_arguments begin with a hyphen,
they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot argument list.
EXAMPLES
Example 1 Passing the -r and -v Arguments to boot
In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M).
example# reboot -dl -- -rv
Example 2 Rebooting Using a Specific Disk and Kernel
The following example reboots using a specific disk and kernel.
example# reboot disk1 kernel.test/unix
Example 3 Fast Rebooting
The following examples use the f option to perform fast reboots.
The following command reboots to the same kernel.
example# reboot -f
The following command reboots to another UFS root disk.
example# reboot -f -- '/dev/dsk/c1d0s0'
The following command reboots to another ZFS root pool.
example# reboot -f -- 'rpool/ROOT/root2'
The following command reboots to mykernel on the same disk with -k option.
example# reboot -f -- '/platform/i86pc/mykernel/amd64/unix -k'
The following command reboots to mykernel off another root disk mounted on /mnt.
example# reboot -f -- '/mnt/platform/i86pc/mykernel/amd64/unix -k'
The following command reboots to /platform/i86pc/kernel/$ISADIR/unix on another boot environment named second_root.
example# reboot -f -e second_root
The following command reboots to the same kernel with -kv options.
example# reboot -f -- '-kv'
FILES
/var/adm/wtmpx
login accounting file
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2),
reboot(3C), attributes(5)NOTES
The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown of
system services, use shutdown(1M) or init(1M) to reboot a Solaris system.
SunOS 5.11 29 Sep 2008 reboot(1M)