10-10-2006
theres could be diff. reasons for this , some more prominent are as below:
1. there is something called as inode which affects this kind of behavior.
even if you delete the files from a filesystem, inodes do get cleared, they
still hold that address space.
run sync command 3 times. I don't know the funda of runing 3 times, but it works.
2. check fuser -cu <filesystem name>
this will give the users accessing the filesystem. this could also one of the problems.
sameer
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
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
4. 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
5. Solaris
Hi,
During package install, am getting:
WARNING: unable to write temp contents file </var/sadm/install/t.contents>
(errno 28: No space left on device)
I tried to delete some stuff under "/var" But I cannot locate who is occupying "/var" space. Because:
# df -h /var/
Filesystem ... (5 Replies)
Discussion started by: viki250
5 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. Ubuntu
I am running a build on Jenkins and I get:
No space left on device
But when I do df, I get:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/ROOT 19249724 18267492 4380 100% /
udev 1457152 4 1457148 1% /dev
tmpfs ... (4 Replies)
Discussion started by: sgffgs
4 Replies
9. 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
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 SUNOS
allocate
allocate(1) allocate(1)
NAME
allocate - device allocation
SYNOPSIS
allocate [-s] [-U uname] device
allocate [-s] [-U uname] -g dev-type
allocate [-s] [-U uname] -F device
The allocate utility manages the ownership of devices through its allocation mechanism. It ensures that each device is used by only one
qualified user at a time.
The device argument specifies the device to be manipulated. To preserve the integrity of the device's owner, the allocate operation is exe-
cuted on all the device special files associated with that device.
The argument dev-type is the device type to be operated on and can only be used with the -g option.
The default allocate operation allocates the device special files associated with device to the uid of the current process.
If the -F option is specified, the device cleaning program is executed when allocation is performed. This cleaning program is found in
/etc/security/lib. The name of this program is found in the device_allocate(4) entry for the device in the dev-exec field.
Only authorized users may allocate a device. The required authorizations are specified in device_allocate(4).
The following options are supported:
-g dev-type Allocates a non-allocated device with a device-type matching dev-type.
-s Silent. Suppresses any diagnostic output.
-F device Reallocates the device allocated to another user. This option is often used with -U to reallocate a specific device to a
specific user. Only a user with the solaris.device.revoke authorization is permitted to use this option.
-U uname Uses the user ID uname instead of the user ID of the current process when performing the allocate operation. Only a user
with the solaris.device.revoke authorization is permitted to use this option.
The following exit values are returned:
non--zero An error occurred.
/etc/security/device_allocate
/etc/security/device_maps
/etc/security/dev/*
/etc/security/lib/*
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
deallocate(1), list_devices(1), bsmconv(1M), dminfo(1M), mkdevalloc(1M), mkdevmaps(1M), device_allocate(4), device_maps(4), attributes(5)
The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for
more information.
/etc/security/dev, mkdevalloc(1M), and mkdevmaps(1M) might not be supported in a future release of the Solaris Operating Environment.
28 Mar 2005 allocate(1)