Sponsored Content
Top Forums UNIX for Advanced & Expert Users NOTICE: HTFS: No space on dev hd (1/42) Post 302125045 by jeya on Tuesday 3rd of July 2007 01:45:04 PM
Old 07-03-2007
Quote:
Originally Posted by blowtorch
One of your filesystems is full. Check which one it is and clear some space.
NOTICE: HTFS: No space on dev hd (1/42)
 

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
SHELL-QUOTE(1p) 					User Contributed Perl Documentation					   SHELL-QUOTE(1p)

NAME
shell-quote - quote arguments for safe use, unmodified in a shell command SYNOPSIS
shell-quote [switch]... arg... DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands or files with embedded white space or shell globbing characters safely. Here are a few examples. EXAMPLES
ssh preserving args When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and passes them to "$SHELL -c". This doesn't work as intended: ssh host touch 'hi there' # fails It creates 2 files, hi and there. Instead, do this: cmd=`shell-quote touch 'hi there'` ssh host "$cmd" This gives you just 1 file, hi there. process find output It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote: eval set -- `find -type f -print0 | xargs -0 shell-quote --` debug shell scripts shell-quote is better than echo for debugging shell scripts. debug() { [ -z "$debug" ] || shell-quote "debug:" "$@" } With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can. save a command for later shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are things the user can't pass through), you can do something like this: user_switches= while [ $# != 0 ] do case x$1 in x--pass-through) [ $# -gt 1 ] || die "need an argument for $1" user_switches="$user_switches "`shell-quote -- "$2"` shift;; # process other switches esac shift done # later eval "shell-quote some-command $user_switches my args" OPTIONS
--debug Turn debugging on. --help Show the usage message and die. --version Show the version number and exit. AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions. AUTHOR
Roderick Schertler <roderick@argon.org> perl v5.8.4 2005-05-03 SHELL-QUOTE(1p)
All times are GMT -4. The time now is 08:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy