Sponsored Content
Top Forums UNIX for Dummies Questions & Answers cat: write error: No space left on device Post 302084124 by igandu on Wednesday 9th of August 2006 09:53:54 AM
Old 08-09-2006
cat: write error: No space left on device

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
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

no space left on device

This seems like it would be a common question, but I didn't find much that helped in a search... I have a script scheduled in my crontab that outputs to /dev/null ie: /dir/scripts/script1 > /dev/null I have recently started getting the error: cp /dir1/dir2/file.xls: No space left on... (1 Reply)
Discussion started by: kristy
1 Replies

2. UNIX for Advanced & Expert Users

no space left on device

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

3. Solaris

No space left on device but free space and inodes are available...

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

4. Solaris

visudo: write error: No space left on device

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

5. HP-UX

Received error as Not enough space left on device

Hi Forum, We have observed one problem in one of our HP-UX machines which runs a software which connects the radio frequency scan devices and the scanned information is stored in the database through the same software. This software has thrown an error like "Not enough space left on the... (4 Replies)
Discussion started by: Nishant.Jvk
4 Replies

6. Shell Programming and Scripting

Write to 1 failed [No space left on device]

I am getting error in a shell script having a simple date command. Error is " write to 1 failed ". We saw that /tmp folder was 100% full. When we cleared some space in /tmp folder then script worked fine. Why does date command(or any other command) require space in /tmp folder? Which settings... (6 Replies)
Discussion started by: mahish20
6 Replies

7. UNIX for Advanced & Expert Users

Sed: couldn't write 1378 items to stdout: No space left on device

Hi , In file first line start with "",when trying to remove using sed i am getting the below error .Please advise sed -e 's///g' -e 's/$]//g' segment1.txt >>segment_m1 sed: couldn't write 1378 items to stdout: No space left on device Thanks, Mohan (1 Reply)
Discussion started by: mohan705
1 Replies

8. Linux

No space left on device while there is plenty of space available

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

Write to 1 failed [No space left on device] Error

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

Sol11 - Error at prompt (no space left on device)

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
rm(1)							      General Commands Manual							     rm(1)

Name
       rm, rmdir - remove (unlink) files or directories

Syntax
       rm [-f] [-r] [-i] [-] file-or-directory-name...
       rmdir directory-name...

Description
       The command removes the entries for one or more files from a directory.	If there are no links to the file then the file is destroyed.  For
       further information, see

       The command removes entries for the named directories, which must be empty.  If they are not empty, the directories remain, and displays an
       error message (see EXAMPLES).

       To  remove  a file, you must have write permission in its directory, but you do not need read or write permission on the file itself.  When
       you are using from a terminal, and you do not have write permission on the file, the command asks for confirmation  before  destroying  the
       file.

       If  input  is redirected from the standard input device (your terminal), then checks to ensure that input is not coming from your terminal.
       If not, sets the -f option, which overrides the file protection, and removes the files silently, regardless of what you have  specified	in
       the file redirected as input to See EXAMPLES.

Options
       -    Specifies that the named files have names beginning with a minus (for example ).

       -f   Forces the removal of file or directory without first requesting confirmation.  Only system or usage messages are displayed.

       -i   Prompts  for yes or no response before removing each entry.  Does not ask when combined with the -f option.  If you type a y, followed
	    by any combination of characters, a yes response is assumed.

       -r   Recursively removes all entries from the specified directory and, then, removes the entry for that directory from  its  parent  direc-
	    tory.

Examples
       The following example shows how to remove a file in your current working directory.
       rm myfile
       This example shows use of the null option to remove a file beginning with a minus sign.
       rm - -gorp
       This example shows how a confirmation is requested for removal of a file for which you do not have write permission.
       rm testfile
       rm: override protection 400 for testfile? y
       This  example  shows  how  the combination of -i and -r options lets you examine all the files in a directory before removing them.  In the
       example, mydirectory is a subdirectory of the current working directory.  Note that the last question requests confirmation before removing
       the  directory  itself.	 Although  the user types ``y'', requesting removal of the directory, the command does not allow this, because the
       directory is not empty; the user typed ``n'' to the question about the file file2 , so file2 was not removed.
       rm -ir mydirectory
       rm: remove mydirectory/file1? y
       rm: remove mydirectory/file2? n
	     .
	     .
	     .
       rm: remove mydirectory? y
       rm: mydirectory: Directory not empty
       This example illustrates that overrides file protection when input is redirected from the standard input device.  The user creates  a  file
       named ``alfie'', with a read-only file protection.  The user then creates a file named ``ans'' to contain the character ``n''.  The command
       following destroys the file ``alfie'', even though the redirected input file requested no deletion.
       cat > alfie
       hello
       ^d
       chmod 444 alfie
       cat > ans
       n
       ^d
       rm < ans alfie

See Also
       unlink(2)

																	     rm(1)
All times are GMT -4. The time now is 02:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy