Sponsored Content
Full Discussion: hd9var full
Operating Systems AIX hd9var full Post 302272338 by shockneck on Tuesday 30th of December 2008 09:41:00 AM
Old 12-30-2008
Quote:
Originally Posted by freeman
[...]i have seen that only one process was writing to directory and killed the rest. then the space changed
I'd like to discourage you from killing processes that originate from /var (and /,/usr... and with older versions of HACMP even from /tmp) as long as you don't know for sure that the server does not need them. Should you happen to kill a process that is vital for your server the results may be unpredictable.
It is all files in AIX (as in every UNIX) and therefore problems related to space in filesystems can be solved in a non disruptive way most of the time by either shrinking/blanking files (but not deleting!)during operation or extending filesystems online.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

/ is full HELP

Hi.. i am having a problem, for some reason my / directory is 100 % full.. and i didn't install or anything on it.. it has almost 2 gig on thr root directory.. maybe i am missing some concept because i do not understand why it get full. it is happening on all three of my system.. and i always... (9 Replies)
Discussion started by: souldier
9 Replies

2. UNIX for Advanced & Expert Users

/ is full

Hi Exprts, I faced this problem several times, which / file system is full (near 100%) and "proc" under that is the main reason. i don't know how to reduce the size as all directories under proc seems important & other dir/files under / are OS related & could not be removed. could anyone... (6 Replies)
Discussion started by: nikk
6 Replies

3. Programming

full -duplex ?

what is meant by full duplex and half duplex? b'coz in differences b\w hub and switch ,i heard lot this duplex word so please help me (1 Reply)
Discussion started by: parvathy
1 Replies

4. AIX

/dev/hd9var/ /var what should i do.

Hello my df -k show me that the /var used 93% Filesystem 1024-blocks Free %Used Iused %Iused Mounted on /dev/hd4 196608 33920 83% 2253 3% / /dev/hd2 1310720 352732 74% 25266 8% /usr /dev/hd9var 262144 18724 93%:confused: ... (8 Replies)
Discussion started by: simka
8 Replies

5. AIX

/dev/hd9var full

/dev/hd9var 819200 1928 100% 12101 12% /var the filesystem is full my self being new to aix what do i do to create space (1 Reply)
Discussion started by: freeman
1 Replies

6. Shell Programming and Scripting

How to extract strings from full path when full path is not fixed

/Path/snowbird9/nrfCompMgrRave1230100920.log.gz:09/20/2010 06:14:51 ERROR Error Message. /Path/snowbird6/nrfCompMgrRave1220100920.log.gz:09/20/2010 06:14:51 ERROR Error Message. /Path/snowbird14/nrfCompMgrRave920100920.log.gz:09/20/2010 06:14:51 ERROR Error Message.... (0 Replies)
Discussion started by: Shirisha
0 Replies

7. Red Hat

/ is full

/ has become full.... So i'm unable to login to the server. What should i do now ?? please help me... Thanks in advance (4 Replies)
Discussion started by: vamshigvk475
4 Replies

8. AIX

Problem in /dev/hd1 and /dev/hd9var

Hello AIXians, I can't boot my AIX, it hangs and stops at the code error: 0518 After searching google, I knew the problem is due to problems in File Systems. So the solution is booting from any bootable media, then run these commands in maintenance mode: #fsck -y /dev/hd4 #fsck -y... (3 Replies)
Discussion started by: Mohannad
3 Replies

9. AIX

100% Inode full with only 67% FS full.

AIX Version 6.1 and 7.1. I understand that when the OS initially creates the FS and inodes, its pretty strict, but not always tuned to a 1:1 ratio. I see the same thing when adding a whole disk LV to a separate device. It seems that when we expand a filesystem the inodes don't get tuned... (5 Replies)
Discussion started by: mrmurdock
5 Replies
xfs_fsr(8)						      System Manager's Manual							xfs_fsr(8)

NAME
xfs_fsr - filesystem reorganizer for XFS SYNOPSIS
xfs_fsr [-v] [-t seconds] [-f leftoff] [-m mtab] xfs_fsr [-v] [xfsdev | file] ... DESCRIPTION
xfs_fsr is applicable only to XFS filesystems. xfs_fsr improves the organization of mounted filesystems. The reorganization algorithm operates on one file at a time, compacting or oth- erwise improving the layout of the file extents (contiguous blocks of file data). The following options are accepted by xfs_fsr. The -m, -t, and -f options have no meaning if any filesystems or files are specified on the command line. -m mtab Use this file for the list of filesystems to reorganize. The default is to use /etc/mtab. -t seconds How long to reorganize. The default is 7200 (2 hours). -f leftoff Use this file instead of /var/tmp/.fsrlast to read the state of where to start and as the file to store the state of where reorganization left off. -v Verbose. Print cryptic information about each file being reorganized. When invoked with no arguments xfs_fsr reorganizes all regular files in all mounted filesystems. xfs_fsr makes many cycles over /etc/mtab each time making a single pass over each XFS filesystem. Each pass goes through and selects files that have the largest number of extents. It attempts to defragment the top 10% of these files on each pass. It runs for up to two hours after which it records the filesystem where it left off, so it can start there the next time. This information is stored in the file /var/tmp/.fsrlast_xfs. If the information found here is somehow inconsistent or out of date it is ignored and reor- ganization starts at the beginning of the first filesystem found in /etc/mtab. xfs_fsr can be called with one or more arguments naming filesystems (block device name), and files to reorganize. In this mode xfs_fsr does not read or write /var/tmp/.fsrlast_xfs nor does it run for a fixed time interval. It makes one pass through each specified regular file and all regular files in each specified filesystem. A command line name referring to a symbolic link (except to a file system device), FIFO, or UNIX domain socket generates a warning message, but is otherwise ignored. While traversing the filesystem these types of files are silently skipped. FILES
/etc/mtab contains default list of filesystems to reorganize. /var/tmp/.fsrlast_xfs records the state where reorganization left off. SEE ALSO
xfs_fsr(8), mkfs.xfs(8), xfs_ncheck(8), xfs(5). NOTES
xfs_fsr improves the layout of extents for each file by copying the entire file to a temporary location and then interchanging the data extents of the target and temporary files in an atomic manner. This method requires that enough free disk space be available to copy any given file and that the space be less fragmented than the original file. It also requires the owner of the file to have enough remaining filespace quota to do the copy on systems running quotas. xfs_fsr generates a warning message if space is not sufficient to improve the target file. A temporary file used in improving a file given on the command line is created in the same parent directory of the target file and is pre- fixed by the string '.fsr'. The temporary files used in improving an entire XFS device are stored in a directory at the root of the target device and use the same naming scheme. The temporary files are unlinked upon creation so data will not be readable by any other process. xfs_fsr does not operate on files that are currently mapped in memory. A 'file busy' error can be seen for these files if the verbose flag (-v) is set. Files marked as no-defrag will be skipped. The xfs_io(8) chattr command with the f attribute can be used to set or clear this flag. Files and directories created in a directory with the no-defrag flag will inherit the attribute. An entry in /etc/mtab or the file specified using the -m option must have the rw option specified for read and write access. If this option is not present, then xfs_fsr skips the filesystem described by that line. See the fstab(5) reference page for more details. In general we do not foresee the need to run xfs_fsr on system partitions such as /, /boot and /usr as in general these will not suffer from fragmentation. There are also issues with defragmenting files lilo(8) uses to boot your system. It is recommended that these files should be flagged as no-defrag with the xfs_io(8) chattr command. Should these files be moved by xfs_fsr then you must rerun lilo before you reboot or you may have an unbootable system. xfs_fsr(8)
All times are GMT -4. The time now is 10:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy