11-02-2012
Ok how do I give it more space? Novice here. Thanks so much.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
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
Hi all,
A very strange problem I have this morning with my Solaris 8.
I have a FS full, I deleted some files but the system doesn't seems to reallocate the free space (I'm using Veritas):
df -k :
/dev/vx/dsk/dlds02vg/dlds02oralv 4194304 4194304 0 100% /dlds02/lds/oracle
... (4 Replies)
Discussion started by: unclefab
4 Replies
4. Solaris
We are using this function tmpfile() :
FILE *tmpfp ;
if ((tmpfp = tmpfile()) == NULL)
{
fprintf(stderr, "%s: ERROR: init_operator(): ", ROUTINE);
perror("tmpfile()");
exit(ERR_OPEN);
}
and the above is raising error :
MSMD0603: ERROR:... (3 Replies)
Discussion started by: atiato
3 Replies
5. UNIX for Dummies Questions & Answers
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
6. Solaris
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
7. Shell Programming and Scripting
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
8. Linux
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
9. Shell Programming and Scripting
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
10. Linux
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
LEARN ABOUT V7
posix_fallocate
POSIX_FALLOCATE(3) Linux Programmer's Manual POSIX_FALLOCATE(3)
NAME
posix_fallocate - allocate file space
SYNOPSIS
#include <fcntl.h>
int posix_fallocate(int fd, off_t offset, off_t len);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
posix_fallocate():
_POSIX_C_SOURCE >= 200112L
DESCRIPTION
The function posix_fallocate() ensures that disk space is allocated for the file referred to by the file descriptor fd for the bytes in the
range starting at offset and continuing for len bytes. After a successful call to posix_fallocate(), subsequent writes to bytes in the
specified range are guaranteed not to fail because of lack of disk space.
If the size of the file is less than offset+len, then the file is increased to this size; otherwise the file size is left unchanged.
RETURN VALUE
posix_fallocate() returns zero on success, or an error number on failure. Note that errno is not set.
ERRORS
EBADF fd is not a valid file descriptor, or is not opened for writing.
EFBIG offset+len exceeds the maximum file size.
EINTR A signal was caught during execution.
EINVAL offset was less than 0, or len was less than or equal to 0, or the underlying filesystem does not support the operation.
ENODEV fd does not refer to a regular file.
ENOSPC There is not enough space left on the device containing the file referred to by fd.
ESPIPE fd refers to a pipe.
VERSIONS
posix_fallocate() is available since glibc 2.1.94.
ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7).
+------------------+---------------+-------------------------+
|Interface | Attribute | Value |
+------------------+---------------+-------------------------+
|posix_fallocate() | Thread safety | MT-Safe (but see NOTES) |
+------------------+---------------+-------------------------+
CONFORMING TO
POSIX.1-2001.
POSIX.1-2008 says that an implementation shall give the EINVAL error if len was 0, or offset was less than 0. POSIX.1-2001 says that an
implementation shall give the EINVAL error if len is less than 0, or offset was less than 0, and may give the error if len equals zero.
NOTES
In the glibc implementation, posix_fallocate() is implemented using the fallocate(2) system call, which is MT-safe. If the underlying
filesystem does not support fallocate(2), then the operation is emulated with the following caveats:
* The emulation is inefficient.
* There is a race condition where concurrent writes from another thread or process could be overwritten with null bytes.
* There is a race condition where concurrent file size increases by another thread or process could result in a file whose size is smaller
than expected.
* If fd has been opened with the O_APPEND or O_WRONLY flags, the function fails with the error EBADF.
In general, the emulation is not MT-safe. On Linux, applications may use fallocate(2) if they cannot tolerate the emulation caveats. In
general, this is only recommended if the application plans to terminate the operation if EOPNOTSUPP is returned, otherwise the application
itself will need to implement a fallback with all the same problems as the emulation provided by glibc.
SEE ALSO
fallocate(1), fallocate(2), lseek(2), posix_fadvise(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/.
GNU
2017-09-15 POSIX_FALLOCATE(3)