Sponsored Content
Operating Systems SCO Insuficient space on /dev SCO 5.5 Post 302262532 by edfair on Friday 28th of November 2008 12:03:10 AM
Old 11-28-2008
I'm not sure how you got your /dev to report from df. df is a reporting mechanism for filesystems and normally /dev is buried within root and any space problems would be reporting root as running short.

In addition /dev normally doesn't have any files stored to take up any space, only several directory entries that consume several k. Unless you have had some sort of glitch and ended up with a core dump stored there.
 

7 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Ran out of space on /dev/root partition

hi, I have a SCO unix server which has a 36gb hard drive, but the IT company who supplied it assigned 1gb to /dev/root, 15mb to /dev/boot and 33gb to /dev/u. The /dev/root partition is now full, is there a way I can use the 33gb assigned to /dev/u without loosing any data, preferably... (2 Replies)
Discussion started by: Martyn
2 Replies

2. SCO

No space on dev HD (1/42)

Good Evening to all, I am having a problem with our unix server, I give you a little history. last we the logins started getting slower and slower, when we tried to print nothing came out on the network printer, the system had an error ("printer file close error unit=0). Checking... (3 Replies)
Discussion started by: berkmillionare
3 Replies

3. UNIX for Advanced & Expert Users

NOTICE: HTFS: No space on dev hd (1/42)

If somebody solve this error please help me! Thanks in advance! :confused: (7 Replies)
Discussion started by: FCollet
7 Replies

4. SCO

No space on /dev/hd 1/42

No one is able to log in. What can I try? Help!:( (1 Reply)
Discussion started by: ibqti
1 Replies

5. SCO

Xenix Problems - No space on dev 1/40

Hello - I'm a newbie to these forums. Please excuse me if I am posting in the wrong area. My dilemma. The HD on our ancient Xenix system apparently is full. I receive the "no space on dev 1/40" prompt. This occurred after I attempted to purge some unwanted files. This system runs our small... (1 Reply)
Discussion started by: gmbrickley
1 Replies

6. SCO

/dev/inet/tcp not listening in SCO 6.

While in SCO Openserver 5.0.7, Sybase listened to /dev/inet/tcp, the same is not working in SCO Openserver 6. The Network card is however active and pinging fine. What can be the reason? What is the way out? An early response will be appreciated. Thank you Regards TCG (2 Replies)
Discussion started by: thecobolguy
2 Replies

7. AIX

How to increase space /dev/hd4?

A check disk space and find /dev/hd4 used 99%. How to increase space. Thank you for advice. /home/tecsys > df Filesystem 512-blocks Free %Used Iused %Iused Mounted on /dev/hd4 1048576 20624 99% 5977 68% / /dev/hd2 6815744 653032 91% 59194 ... (4 Replies)
Discussion started by: yapcs88
4 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)
All times are GMT -4. The time now is 03:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy