Sponsored Content
Top Forums UNIX for Advanced & Expert Users NOTICE: HTFS: No space on dev hd (1/42) Post 302097962 by blowtorch on Wednesday 29th of November 2006 09:54:13 PM
Old 11-29-2006
One of your filesystems is full. Check which one it is and clear some space.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

/dev/hd* ?? & HTFS .... What is this stuff?

# grep "Jul 3" syslog.messages | more Jul 3 00:16:03 www3 CPU3: NOTICE: HTFS: No space on dev hd (1/42) Jul 3 00:16:08 www3 CPU3: NOTICE: HTFS: No space on dev hd (1/42) Jul 3 00:17:01 www3 CPU2: NOTICE: HTFS: No space on dev hd (1/42) Jul 3 00:17:06 www3 syslogd: /usr/adm/debug: No space... (1 Reply)
Discussion started by: Cameron
1 Replies

2. UNIX for Dummies Questions & Answers

Warning: HTFS: bad dir inode 62730 on HTFS dev hd (1/42)

Hello all. I am receiving this message on the console of a SCO Openserver 5.0.7 server. The hardware is IBM, running mirrored SCSI drives with a hot-swap spare off of an IBM Serveraid controller. I suspect that some permutation of fsck can help me resolve whatever is causing the error, but I am... (0 Replies)
Discussion started by: DoublePanic
0 Replies

3. 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

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

Insuficient space on /dev SCO 5.5

Unix SCO 5.5 Insuficient space on /dev - when I run df I get /dev 99% usage. I have a large number of users (most of them are not with the company since Cretacic) and I want to delete them to make more space. When I run rmuser I get rmuser: not found if I type su root rmuser rmuser: The... (6 Replies)
Discussion started by: tzveistein
6 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(7D) 							      Devices								   mem(7D)

NAME
mem, kmem, allkmem - physical or virtual memory access SYNOPSIS
/dev/mem /dev/kmem /dev/allkmem DESCRIPTION
The file /dev/mem is a special file that provides access to the physical memory of the computer. The file /dev/kmem is a special file that provides access to the virtual address space of the operating system kernel, excluding memory that is associated with an I/O device. The file /dev/allkmem is a special file that provides access to the virtual address space of the operating system kernel, including memory that is associated with an I/O device. You can use any of these devices to examine and modify the system. Byte addresses in /dev/mem are interpreted as physical memory addresses. Byte addresses in /dev/kmem and /dev/allkmem are interpreted as kernel virtual memory addresses. A reference to a non-existent location returns an error. See ERRORS for more information. The file /dev/mem accesses physical memory; the size of the file is equal to the amount of physical memory in the computer. This size may be larger than 4GB on a system running the 32-bit operating environment. In this case, you can access memory beyond 4GB using a series of read(2) and write(2) calls, a pread64() or pwrite64() call, or a combination of llseek(2) and read(2) or write(2). ERRORS
EFAULT Occurs when trying to write(2) a read-only location (allkmem), read(2) a write-only location (allkmem), or read(2) or write(2) a non-existent or unimplemented location (mem, kmem, allkmem). EIO Occurs when trying to read(2) or write(2) a memory location that is associated with an I/O device using the /dev/kmem spe- cial file. ENXIO Results from attempting to mmap(2) a non-existent physical (mem) or virtual (kmem, allkmem) memory address. FILES
/dev/mem Provides access to the computer's physical memory. /dev/kmem Provides access to the virtual address space of the operating system kernel, excluding memory that is associated with an I/O device. /dev/allkmem Provides access to the virtual address space of the operating system kernel, including memory that is associated with an I/O device. SEE ALSO
llseek(2), mmap(2), read(2), write(2) WARNINGS
Using these devices to modify (that is, write to) the address space of a live running operating system or to modify the state of a hardware device is extremely dangerous and may result in a system panic if kernel data structures are damaged or if device state is changed. SunOS 5.10 18 Feb 2002 mem(7D)
All times are GMT -4. The time now is 06:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy