Sponsored Content
Full Discussion: Root filesystem filling up!
Top Forums UNIX for Dummies Questions & Answers Root filesystem filling up! Post 302369789 by psiva_arul on Monday 9th of November 2009 03:03:27 PM
Old 11-09-2009
Hi,
You have to check the filesystem hosted path and maximum used space in %
using the below command

df -k . | sort +4rn
The above command will listout the maximum used path and filesystem

Then you have check the maximum used filesystem path and check which file used more space in the directory using below command df -k . | sort +4rn

Then you have to ziped the maximum size file if its not current active processed file.



Thanks
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Mounted Root Filesystem

In my Solaris 10 based server, I have noticed the following mounts when a use DF -K /dev/dsk/c0t0d0s0 5062414 3213876 1797914 65% / / 5062414 3213876 1797914 65% /net/se420 I understand the first mount because it appears in my vfstab file and is the mount of root that I would expect.... (1 Reply)
Discussion started by: jimthompson
1 Replies

2. Solaris

Filesystem filling up and no clue as to why!

df shows that the filesystem is filling up and the usage is 94%. However when I actually traverse to the directory I du shows only about 10% of the space occupied! Below is the output of df and du: >>>df -kh /cbmdata/00 470M 393M 29M 94% /cbmdata/00 >>>/cbmdata/00>... (3 Replies)
Discussion started by: zombiezparadize
3 Replies

3. UNIX for Advanced & Expert Users

diff command filling /var filesystem space

Hi, I am using diff command to check difference between two files.Both files are very big and when i execute this command /var temp space is filled up almost 99%. Can any one please tell me is there any way i can specify directory name which has more space so that diff can use that dir for... (2 Replies)
Discussion started by: ukatru
2 Replies

4. Solaris

Root Filesystem

Hi, Can we install root file system on other than 0th slice???? (5 Replies)
Discussion started by: tirupathiraju_t
5 Replies

5. AIX

how to find whats filling up Root Directory

Hi guys I am running AIX 5.3 and a newbie to it. And I am getting reports telling me that the Root Directory is reaching almost max capacity, can someone give m some advice to find out what files are causing it to grow? , or how I can identify the growing files? Thanks (6 Replies)
Discussion started by: ryanbsc@gmail.c
6 Replies

6. Solaris

Resizing the Root Filesystem

Is it possible to increase the root filesystem size without reboot ?? (4 Replies)
Discussion started by: gowthamakanthan
4 Replies

7. Solaris

Root partition filling up

I have a T1000 Sparc server that has a relatively small root partition which is 24Gb and a larger partition dedicated to /export/home that is approximately 100 Gb. We have a lot of data going to /var/audit and to /var/core/corefiles. Is there any non-destructive way to redirect files from... (4 Replies)
Discussion started by: goose25
4 Replies

8. Linux

root filesystem goes readonly

I see this when tried to create a dir using root fstab entries are pretty normal tried to remount with rw but it is still the same block device /dev/sda2 is write-protected ---------- Post updated at 04:57 PM ---------- Previous update was at 03:51 PM ---------- fstab entry ... (4 Replies)
Discussion started by: robo
4 Replies

9. Solaris

Cannot tell what is filling up root (/) partition on Sol10

I can see that my root partition is down to single-digit GB free out of 134GB root partition on a larger server with many SAN, NFS, LOFS mounts etc mounted at the root (/) partition. How can I specifically tell which directories is causing the most utilization in my root (/) partition? (3 Replies)
Discussion started by: ckmehta
3 Replies
ATTR_SET(3)						       XFS Compatibility API						       ATTR_SET(3)

NAME
attr_set, attr_setf - set the value of a user attribute of a filesystem object C SYNOPSIS
#include <attr/attributes.h> int attr_set (const char *path, const char *attrname, const char *attrvalue, const int valuelength, int flags); int attr_setf (int fd, const char *attrname, const char *attrvalue, const int valuelength, int flags); DESCRIPTION
The attr_set and attr_setf functions provide a way to create attributes and set/change their values. Path points to a path name for a filesystem object, and fd refers to the file descriptor associated with a file. If the attribute attrname does not exist, an attribute with the given name and value will be created and associated with that indicated filesystem object. If an attribute with that name already exists on that filesystem object, the existing value is replaced with the new value given in this call. The new attribute value is copied from the attrvalue buffer for a total of valuelength bytes. The flags argument can contain the following symbols bitwise OR'ed together: ATTR_ROOT Look for attrname in the root address space, not in the user address space. (limited to use by super-user only) ATTR_DONTFOLLOW Do not follow symbolic links when resolving a path on an attr_set function call. The default is to follow symbolic links. ATTR_CREATE Return an error (EEXIST) if an attribute of the given name already exists on the indicated filesystem object, otherwise create an attribute with the given name and value. This flag is used to implement a pure create operation, without this flag attr_set will create the attribute if it does not already exist. An error (EINVAL) will be returned if both ATTR_CREATE and ATTR_REPLACE are set in the same call. ATTR_REPLACE Return an error (ENOATTR) if an attribute of the given name does not already exist on the indicated filesystem object, otherwise replace the existing attribute's value with the given value. This flag is used to implement a pure replacement operation, without this flag attr_set will create the attribute if it does not already exist. An error (EINVAL) will be returned if both ATTR_CREATE and ATTR_REPLACE are set in the same call. attr_set will fail if one or more of the following are true: [ENOATTR] The attribute name given is not associated with the indicated filesystem object and the ATTR_REPLACE flag bit was set. [E2BIG] The value of the given attribute is too large, it exceeds the maximum allowable size of an attribute value. [EEXIST] The attribute name given is already associated with the indicated filesystem object and the ATTR_CREATE flag bit was set. [ENOENT] The named file does not exist. [EPERM] The effective user ID does not match the owner of the file and the effective user ID is not super-user. [ENOTDIR] A component of the path prefix is not a directory. [EACCES] Search permission is denied on a component of the path prefix. [EINVAL] A bit was set in the flag argument that is not defined for this system call, or both the ATTR_CREATE and ATTR_REPLACE flags bits were set. [EFAULT] Path, attrname, or attrvalue points outside the allocated address space of the process. [ELOOP] A path name lookup involved too many symbolic links. [ENAMETOOLONG] The length of path exceeds {MAXPATHLEN}, or a pathname component is longer than {MAXNAMELEN}. attr_setf will fail if: [ENOATTR] The attribute name given is not associated with the indicated filesystem object and the ATTR_REPLACE flag bit was set. [E2BIG] The value of the given attribute is too large, it exceeds the maximum allowable size of an attribute value. [EEXIST] The attribute name given is already associated with the indicated filesystem object and the ATTR_CREATE flag bit was set. [EINVAL] A bit was set in the flag argument that is not defined for this system call, or both the ATTR_CREATE and ATTR_REPLACE flags bits were set, or fd refers to a socket, not a file. [EFAULT] Attrname, or attrvalue points outside the allocated address space of the process. [EBADF] Fd does not refer to a valid descriptor. DIAGNOSTICS
On success, zero is returned. On error, -1 is returned, and errno is set appropriately. SEE ALSO
attr(1), attr_get(3), attr_list(3), attr_multi(3), and attr_remove(3). Dec 2001 Extended Attributes ATTR_SET(3)
All times are GMT -4. The time now is 07:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy