12-13-2013
your mean "/dev/vg51wh2p/wh2ppkg-dlx 10240000 5819722 4151916 58% /wh2ppkg/dlx" is the directory where the sofware installed ,but i do not see the directory is going to full. and your CPU/MEM use rate is not high.
your memory ,you can use "#machinfo" to check the MEM size.
use “#glance plus m command ” to check the free memory and used memory
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have a SCO UNIX on my Server. When I last tried to shutdown my system, I got an error message
“no space left on device”.
Now when I try to boot the system again, I
just can't and I get the same error message. Please help! (2 Replies)
Discussion started by: anjane
2 Replies
2. UNIX for Dummies Questions & Answers
I am trying to create new files under my directory...but i getting the following message...
cat: write error: No space left on device
How do we handle this error.
I am not getting this error when I login as the super user (3 Replies)
Discussion started by: igandu
3 Replies
3. Solaris
Hi all,
A very strange problem I have this morning with my Solaris 8.
I have a FS full, I deleted some files but the system doesn't seems to reallocate the free space (I'm using Veritas):
df -k :
/dev/vx/dsk/dlds02vg/dlds02oralv 4194304 4194304 0 100% /dlds02/lds/oracle
... (4 Replies)
Discussion started by: unclefab
4 Replies
4. UNIX for Dummies Questions & Answers
hello all,
i have a proc binary that we run on unix environment, and it is generating this error
'' tstfile(): No space left on device ''
can you please assist on how to narrow down the problem?
thanks (4 Replies)
Discussion started by: mjdbouk
4 Replies
5. Solaris
hi guys, me again ;)
i recently opened a thread about physical to zone migration.
My zone is mounted over a "bigger" LUN (500GB) and step is now to move the old files, from the physical server, to my zone.
We are talking about 22mio of files.
i used rsync to do that and every time at... (8 Replies)
Discussion started by: beta17
8 Replies
6. Solaris
Hi All,
This is Sandeep Gupta,
I am facing a problem with sudo command.
Whenever i am executing the command "visudo" i am getting the error "visudo: write error: No space left on device".
but i have checked on my Solaris Box everything is ok, i have enough free space on my box, and also... (13 Replies)
Discussion started by: Sandeepgupta
13 Replies
7. Shell Programming and Scripting
Hi,
We are trying to sort the 40GB file in unix and getting following error.
Error:
sort: can't write /var/tmp/stmAAAvsaGfJ.00002929: No space left on device
sort -t ',' -k4 $DIR/INF_ff_FULL.dat >>$DIR/Sort_INF_ff_FULL.dat; 2>$DIR/sort_error.log
Can you please advise how to... (2 Replies)
Discussion started by: koti_rama
2 Replies
8. Linux
Hello all
posting here after scanning the net and tried most of the things offered
still no solution that worked
when I do :
$ df -h
Filesystem Size Used Avail Use% Mounted on
footmpfs 7.9G 60K 7.9G 1% /dev
tmpfs 7.9G 0 7.9G 0% /dev/shm
/dev/da1 ... (3 Replies)
Discussion started by: umen
3 Replies
9. Solaris
Running a installation on Solaris 11 and getting error write to 1 failed
If anyone can advise ?
ORIGINAL_PATH="${PATH}"
# prepend /usr/xpg4/bin to PATH as needed
temporaryPath=`expr "${PATH}:" : '\(/usr/xpg4/bin:\)'`
if
then
PATH="/usr/xpg4/bin:${PATH}"
seem to have... (6 Replies)
Discussion started by: Mpumi
6 Replies
10. Solaris
user1@:/$
-ksh: line 3: write to 1 failed
user11@:/$
-ksh: line 3: write to 1 failed
user1@:/$
-ksh: line 3: write to 1 failed
user1@:/$
-ksh: line 3: write to 1 failed
user1@:/$
-ksh: line 3: write to 1 failed But theres plenty of space :-
user1@:/$ df -kh
Filesystem ... (9 Replies)
Discussion started by: psychocandy
9 Replies
MEM(4) Linux Programmer's Manual MEM(4)
NAME
mem, kmem, port - system memory, kernel memory and system ports
DESCRIPTION
/dev/mem is a character device file that is an image of the main memory of the computer. It may be used, for example, to examine (and even
patch) the system.
Byte addresses in /dev/mem are interpreted as physical memory addresses. References to nonexistent locations cause errors to be returned.
Examining and patching is likely to lead to unexpected results when read-only or write-only bits are present.
Since Linux 2.6.26, and depending on the architecture, the CONFIG_STRICT_DEVMEM kernel configuration option limits the areas which can be
accessed through this file. For example: on x86, RAM access is not allowed but accessing memory-mapped PCI regions is.
It is typically created by:
mknod -m 660 /dev/mem c 1 1
chown root:kmem /dev/mem
The file /dev/kmem is the same as /dev/mem, except that the kernel virtual memory rather than physical memory is accessed. Since Linux
2.6.26, this file is available only if the CONFIG_DEVKMEM kernel configuration option is enabled.
It is typically created by:
mknod -m 640 /dev/kmem c 1 2
chown root:kmem /dev/kmem
/dev/port is similar to /dev/mem, but the I/O ports are accessed.
It is typically created by:
mknod -m 660 /dev/port c 1 4
chown root:kmem /dev/port
FILES
/dev/mem
/dev/kmem
/dev/port
SEE ALSO
chown(1), mknod(1), ioperm(2)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux 2015-01-02 MEM(4)