Sponsored Content
Full Discussion: Filesystem Full
Top Forums UNIX for Dummies Questions & Answers Filesystem Full Post 78228 by ilak1008 on Monday 18th of July 2005 02:10:29 AM
Old 07-18-2005
I have already ran “cp /dev/null /var/adm/wtmpx” and it seems that everything is running smoothly along with the software that we are using. Below is the result after emptying wtmpx file:

# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 741263 518123 163839 76% /
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
swap 727392 16 727376 1% /var/run
swap 728240 864 727376 1% /tmp
/dev/dsk/c0t0d0s7 36592677 913706 35313045 3% /export/home
/dev/dsk/c0t0d0s4 61407 9 55258 1% /var/dump
/dev/dsk/c0t0d0s3 493527 42 444133 1% /var/tmp


As you've noticed, the available used capacity in /dev/dsk/c0t0d0s0 directory decreased from 88% down to 76%. We gained about 12% more disk space now. I guess this would be enough to keep us going without the need of reformatting our hard disk anymore. Is there any more file/s that we need to empty to give us more additional disk space?

Everytime I open /dev/dsk/c0t0d0s0 directory, the only message I get is, “No open method defined for c0t0d0s0”. Obviously, it does not show what files are stored in it.

After running, “df -k /var/adm/wtmpx”, it came up with the following results:
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 741263 518123 163839 76% /

In additing to this, all files in /var/adm directory resulted to the same output after running df -k.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

/tmp filesystem full

I am running AIX 3 4. When I do a df I get: Filesystem 512-blocks Free %Used Iused %Iused Mounted on /dev/hd4 32768 10232 69% 1309 16% / /dev/hd2 917504 86360 91% 19744 18% /usr /dev/hd9var 131072 67712 49% 617 ... (11 Replies)
Discussion started by: szodiac
11 Replies

2. HP-UX

vxfs filesystem full!

Dear all, What should I do with the following error message: vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent) Thanks for your advises, (1 Reply)
Discussion started by: hungevntelecom
1 Replies

3. Solaris

The filesystem is still full - Solaris 10!

Good morning, sir! I've a problem with FileSystem, the problem is FileSystem is full First time, I've already read carefully the sticky thread FileSystem full - What to lock for https://www.unix.com/sun-solaris/25840-filesystem-full-what-look.html And then, I will post some information of... (4 Replies)
Discussion started by: trantuananh24hg
4 Replies

4. UNIX for Dummies Questions & Answers

filesystem full

my root filesystem is eventually full "/dev/rdsk/c1d0s0" as a result i cannot boot to the operating system, i booted into the fail safe mode to check the space using df -h command i discover that it is eventually full. Also to my amazement i found that i cannot see the filesystem which mounted on... (1 Reply)
Discussion started by: seyiisq
1 Replies

5. Red Hat

/ filesystem getting full

Hi All, How do I increase the root filesystem? It's getting full. / 90% Here's the break down, below 232 dev 5624 tmp *6764 bin 16860 root *19680 sbin *20436 lib64 28329 boot *47992 etc 150012 var *254540 lib 651708 home *2445044 usr (5 Replies)
Discussion started by: itik
5 Replies

6. UNIX for Dummies Questions & Answers

filesystem is full

Hello everybody, a very basic question. Inspite of me deleting huge files in a filesystem(AIX 5.3) in oracle folder, the filesystem when i check using df -k still shows 100% full. Does that mean there is a process still pointing to the files which i deleted. how do i work around this. Thanks!... (3 Replies)
Discussion started by: karthikosu
3 Replies

7. AIX

What is the cause of USR filesystem full

we are using aix 5.3 and we notice that the filesystem /usr is almost full. we have an oracle database running on the server.what are the cause why this filesystem is almost full.what should we do to free some space on this filesystem beside increase the size?thanks (4 Replies)
Discussion started by: paulexis
4 Replies

8. Solaris

Filesystem Full

In our shop we have to run a batch cycle. Every so often while we are running batch we get a filesystem full situation that causes batch to stop or slow down. Anyway, the practiced procedure is to look for large files and zip them. This takes a lot of time. We are in a sun solaris environment. What... (1 Reply)
Discussion started by: Harleyrci
1 Replies

9. AIX

Livedump filesystem almost full

Guy's I'm getting this message Livedump filesystem almost full in errpt logs and its meanning this file system /var/adm/ras/livedump /var has more than 1.5 GB free space .. why I'm getting that message and .. Pls advice to to avoide it ---------- Post updated 03-21-11 at 01:39 AM... (1 Reply)
Discussion started by: Mr.AIX
1 Replies
scdpm(1M)						  System Administration Commands						 scdpm(1M)

NAME
scdpm - manage disk path monitoring daemon SYNOPSIS
scdpm [-a] {node | all} scdpm -f filename scdpm -m {[node | all][:/dev/did/rdsk/]dN | [:/dev/rdsk/]cNtXdY | all} scdpm -n {node | all} scdpm -p [-F] {[node | all][:/dev/did/rdsk/]dN | [/dev/rdsk/]cNtXdY | all} scdpm -u {[node | all][:/dev/did/rdsk/]dN | [/dev/rdsk/]cNtXdY | all} DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The scdpm command manages the disk path monitoring daemon in a cluster. You use this command to monitor and unmonitor disk paths. You can also use this command to display the status of disk paths or nodes. All of the accessible disk paths in the cluster or on a specific node are printed on the standard output. You must run this command on a cluster node that is online and in cluster mode. You can specify either a global disk name or a UNIX path name when you monitor a new disk path. Additionally, you can force the daemon to reread the entire disk configuration. You can use this command only in the global zone. OPTIONS
The following options are supported: -a Enables the automatic rebooting of a node when all monitored disk paths fail, provided that the following conditions are met: o All monitored disk paths on the node fail. o At least one of the disks is accessible from a different node in the cluster. You can use this option only in the global zone. Rebooting the node restarts all resource and device groups that are mastered on that node on another node. If all monitored disk paths on a node remain inaccessible after the node automatically reboots, the node does not automatically reboot again. However, if any monitored disk paths become available after the node reboots but then all monitored disk paths again fail, the node automatically reboots again. You need solaris.cluster.device.admin role-based access control (RBAC) authorization to use this option. See rbac(5). -F If you specify the -F option with the -p option, scdpm also prints the faulty disk paths in the cluster. The -p option prints the cur- rent status of a node or a specified disk path from all the nodes that are attached to the storage. -f filename Reads a list of disk paths to monitor or unmonitor in filename. You can use this option only in the global zone. The following example shows the contents of filename. u schost-1:/dev/did/rdsk/d5 m schost-2:all Each line in the file must specify whether to monitor or unmonitor the disk path, the node name, and the disk path name. You specify the m option for monitor and the u option for unmonitor. You must insert a space between the command and the node name. You must also insert a colon (:) between the node name and the disk path name. You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5). -m Monitors the new disk path that is specified by node:diskpath. You can use this option only in the global zone. You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5). -n Disables the automatic rebooting of a node when all monitored disk paths fail. You can use this option only in the global zone. If all monitored disk paths on the node fail, the node is not rebooted. You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5). -p Prints the current status of a node or a specified disk path from all the nodes that are attached to the storage. You can use this option only in the global zone. If you also specify the -F option, scdpm prints the faulty disk paths in the cluster. Valid status values for a disk path are Ok, Fail, Unmonitored, or Unknown. The valid status value for a node is Reboot_on_disk_failure. See the description of the -a and the -n options for more information about the Reboot_on_disk_failure status. You need solaris.cluster.device.read RBAC authorization to use this option. See rbac(5). -u Unmonitors a disk path. The daemon on each node stops monitoring the specified path. You can use this option only in the global zone. You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5). EXAMPLES
Example 1 Monitoring All Disk Paths in the Cluster Infrastructure The following command forces the daemon to monitor all disk paths in the cluster infrastructure. # scdpm -m all Example 2 Monitoring a New Disk Path The following command monitors a new disk path.All nodes monitor /dev/did/dsk/d3 where this path is valid. # scdpm -m /dev/did/dsk/d3 Example 3 Monitoring New Disk Paths on a Single Node The following command monitors new paths on a single node. The daemon on the schost-2 node monitors paths to the /dev/did/dsk/d4 and /dev/did/dsk/d5 disks. # scdpm -m schost-2:d4 -m schost-2:d5 Example 4 Printing All Disk Paths and Their Status The following command prints all disk paths in the cluster and their status. # scdpm -p schost-1:reboot_on_disk_failure enabled schost-2:reboot_on_disk_failure disabled schost-1:/dev/did/dsk/d4 Ok schost-1:/dev/did/dsk/d3 Ok schost-2:/dev/did/dsk/d4 Fail schost-2:/dev/did/dsk/d3 Ok schost-2:/dev/did/dsk/d5 Unmonitored schost-2:/dev/did/dsk/d6 Ok Example 5 Printing All Failed Disk Paths The following command prints all of the failed disk paths on the schost-2 node. # scdpm -p -F all schost-2:/dev/did/dsk/d4 Fail Example 6 Printing the Status of All Disk Paths From a Single Node The following command prints the disk path and the status of all disks that are monitored on the schost-2 node. # scdpm -p schost-2:all schost-2:reboot_on_disk_failure disabled schost-2:/dev/did/dsk/d4 Fail schost-2:/dev/did/dsk/d3 Ok EXIT STATUS
The following exit values are returned: 0 The command completed successfully. 1 The command failed completely. 2 The command failed partially. Note - The disk path is represented by a node name and a disk name. The node name must be the host name or all. The disk name must be the global disk name, a UNIX path name, or all. The disk name can be either the full global path name or the disk name: /dev/did/dsk/d3 or d3. The disk name can also be the full UNIX path name: /dev/rdsk/c0t0d0s0. Disk path status changes are logged with the syslogd LOG_INFO facility level. All failures are logged with the LOG_ERR facility level. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cldevice(1CL), clnode(1CL), attributes(5) Sun Cluster System Administration Guide for Solaris OS Sun Cluster 3.2 22 Jun 2006 scdpm(1M)
All times are GMT -4. The time now is 11:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy