Sponsored Content
Top Forums Shell Programming and Scripting Write to 1 failed [No space left on device] Post 302938252 by agent.kgb on Friday 13th of March 2015 02:37:46 PM
Old 03-13-2015
what is your OS?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

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 (3 Replies)
Discussion started by: igandu
3 Replies

2. UNIX for Dummies Questions & Answers

No space left on device

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

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. Shell Programming and Scripting

No Space left On Device

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

6. Linux

No space left on device when using rm

Hello people I have a small fileserver running busybox (very small linux distro with most essential stuff on it) and I am trying to remove some unused directories on it. When I try this: rm -R test/I get: rm: cannot remove 'test': No space left on devicedf shows: Filesystem ... (8 Replies)
Discussion started by: GTCG
8 Replies

7. AIX

Cpio: copy failed - No space left on device when I use rpm

Hello, I want to install GCC gcc-4.8.1-2.src.rpm for AIX 6.1 when I lance my command rpm -i gcc-4.8.1-2.src.rpm I have this error unpacking of archive failed on file gcc-4.8.1.tar.bz2: cpio: copy failed - No space left on device I checked the free space and I am surpise becouse I have... (7 Replies)
Discussion started by: tatab355
7 Replies

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

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

10. 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
NASH(8) 						      System Manager's Manual							   NASH(8)

NAME
nash - script interpretor to interpret linuxrc images SYNOPSIS
nash [--quiet] [--force] script DESCRIPTION
nash is a very simple script interpretor designed to be as small as possible. It is primarily designed to run simple linuxrc scripts on an initrd image. Arguments to commands may be enclosed in either single or double quotes to allow spaces to be included in the arguments. Spa- ces outside of quotations always delineate arguments, and so backslash escaping is supported. Additionally, if nash is invoked as modprobe, it will immediately exit with a return code of zero. This is to allow initrd's to prevent some extraneous kernel error messages during startup. There are two types of commands, built in and external. External commands are run from the filesystem via execve(). If commands names are given without a path, nash will search it's builtin PATH, which is /usr/bin, /bin, /sbin, /usr/sbin. Currently, nash supports the following built in commands. access -[r][w][x][f] path Tells whether the current user has sufficient permissions to read, write, or execture path, or if the file exists (see access(2) for more information). echo [item]* [> filename] Echos the text strings given to a file, with a space in between each item. The output may be optionally redirected to a file. exec <command> The command given is execed, overlaying the nash process. find dir -name name Display the path to files named name in or below directory dir. This is a very limited implementation of find(1). findlodev Prints the full path to the first unused loopback block device on the system. If none is available, no output is displayed. losetup /dev/loopdev file Binds file to the loopback device /dev/loopdev. See losetup(8) for information on loopback devices. mkdevices path Creates device files for all of the block devices listed in /proc/partitions in the directory specfied by path. mkdir [-p] path Creates the directory path. If -p is specified, this command will not complain if the directory exists. Note this is a subset of the standard mkdir -p behavior. mknod path [c|b] major minor Creates a device inode for path. This is identical to mkdev(1) which the exceptions that it will not create named pipes and if the directories in path do not exist they will be automatically created. mkrootdev path Makes path a block inode for the device which should be mounted as root. To determine this device nash uses the device suggested by the root= kernel command line argument (if root=LABEL is used devices are probed to find one with that label). If no root= argument is available, /proc/sys/kernel/real-root-dev provides the device number. mount [--ro] -o opts -t type device mntpoint Mounts a filesystem. It does not support NFS, and it must be used in the form given above (arguments must go first). If device is of the form LABEL=foo the devices listed in /fB/proc/partitions will be searched, and the first device with a volume label of foo will be mounted. Normal mount(2) options are supported, and --ro will mount the filesystem read only for compatibility with older versions of nash. The defaults mount option is silently ignored. pivot_root newrootpath oldrootpath Makes the filesystem mounted at newrootpath the new root filesystem, and mounts the current root filesystem as oldrootpath. raidautorun mddevice Runs raid autodetection on all raid-typed partitions. mddevice must be a raid device (any will do). showlabels Display a table of devices, their filesystem labels, and their uuids. umount path Unmounts the filesystem mounted at path. RETURN VALUE
Returns 0 is the last command succeeded or 1 if it failed. OPTIONS
--force Allows force really execute the script, even though nash doesn't appear to be running from an initrd image. BUGS
Probably many. nash is not a shell, and it shouldn't be thought of as one. It isn't entirely different from a shell, but that's mostly by accident. AUTHOR
Erik Troan <ewt@redhat.com> 4th Berkeley Distribution Sat Mar 27 1999 NASH(8)
All times are GMT -4. The time now is 08:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy