12-30-2008
thanx
using lsof i have seen that only one process was writing to directory and killed the rest. then the space changed
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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
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
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
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 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
/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
/ 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
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
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
LEARN ABOUT MOJAVE
chroot
CHROOT(2) BSD System Calls Manual CHROOT(2)
NAME
chroot -- change root directory
SYNOPSIS
#include <unistd.h>
int
chroot(const char *dirname);
DESCRIPTION
Dirname is the address of the pathname of a directory, terminated by an ASCII NUL. chroot() causes dirname to become the root directory,
that is, the starting point for path searches of pathnames beginning with '/'.
In order for a directory to become the root directory a process must have execute (search) access for that directory.
If the program is not currently running with an altered root directory, it should be noted that chroot() has no effect on the process's cur-
rent directory.
If the program is already running with an altered root directory, the process's current directory is changed to the same new root directory.
This prevents the current directory from being further up the directory tree than the altered root directory.
This call is restricted to the super-user.
RETURN VALUES
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate an error.
ERRORS
chroot() will fail and the root directory will be unchanged if:
[ENOTDIR] A component of the path name is not a directory.
[ENAMETOOLONG] A component of a pathname exceeded {NAME_MAX} characters, or an entire path name exceeded {PATH_MAX} characters.
[ENOENT] The named directory does not exist.
[EACCES] Search permission is denied for any component of the path name.
[ELOOP] Too many symbolic links were encountered in translating the pathname.
[EFAULT] Path points outside the process's allocated address space.
[EIO] An I/O error occurred while reading from or writing to the file system.
SEE ALSO
chdir(2)
WARNINGS
There are ways for a root process to escape from the chroot jail.
HISTORY
The chroot() function call appeared in 4.2BSD.
4.2 Berkeley Distribution June 4, 1993 4.2 Berkeley Distribution