07-18-2013
Quote:
Originally Posted by
achenle
If the file is still being written to, depending on exactly how the file is being written to, what flags were used to open the file, and the specifics of the underlying file system, a single write to the file could cause it to balloon right back up in size.
Not usually. Most UNIX filesystems have 'sparse' files... You can open a new file, seek ahead 99 gigabytes, and write 1 byte there, to get a file that looks like 99 gigabytes in ls, but only takes 512 bytes on disk. The 99 gigabytes of empty space are not stored.
The same happens when you truncate a file, and they keep writing at the far end. It'll look funny, but you're no longer out of disk space.
You may have problems reading or copying such a file of course, since most programs will just blithely read the sparse sections.
Last edited by Corona688; 07-18-2013 at 01:09 PM..
These 2 Users Gave Thanks to Corona688 For This Post:
10 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
When I try to log in as root I get the following message
realloccg /: file system full sendmail :NO Queue:low on space (have 0,SMTP-DAEMON needs 101 in /var/spool/mqueue) What should I do? (1 Reply)
Discussion started by: hopeless
1 Replies
2. UNIX for Advanced & Expert Users
Hi All,
There was a background process running on a Solaris 2.8 machine, and appeared to have filled all available disk-space. I done a killall, and upon re-booting found that the file system had filled up, and will not boot as normal as a result. For example, I'm getting
/usr/adm/messages: No... (8 Replies)
Discussion started by: Breen
8 Replies
3. Solaris
Hi, I just started working with UNIX on an old semi-fossilized Sun workstation which I use to process LOTS of images,however, I just started to get an error message that the file system is full and then my shell tool or/and text editor freeze up. Help? (8 Replies)
Discussion started by: Bend
8 Replies
4. Solaris
I read the sticky and thought of a script I use on a regular basis. Since unless you patch/upgrade the df command on solaris you have a very tought time teling how full the system truly is.
Output looks like
$ biggest.sh /tmp
Filesystem kbytes used avail capacity Mounted... (0 Replies)
Discussion started by: meyerder
0 Replies
5. Solaris
I am receving following Error message in /var/adm/messages
"NOTICE: alloc: /: file system full"
Disk space usage is as beklow:
df -k
$ Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 76678257 56962561 18948914 76% /
/proc ... (8 Replies)
Discussion started by: Asteroid
8 Replies
6. Solaris
hello
Even though I am not out of inodes or of space, the /var/adm/messages shows messages:
file system full
I am doing now fcsk -m (400G) and I am still waiting to see the fragmentation results (should I add another option to df to have a faster output?)
Do you have any other hints... (6 Replies)
Discussion started by: melanie_pfefer
6 Replies
7. UNIX for Advanced & Expert Users
Can anyone help me in cleaning /opt filesystem..
i have checked all the options and i have cleared all the logs and the total size of the files in /opt is shown as 1.8GB were as the size of /opt is 4.8GB
but wen i run the command
# df -h /opt
it gives
capacity
99%
Please help... (17 Replies)
Discussion started by: kjamsheed
17 Replies
8. Red Hat
Hey all,
What do you think mostly happened in the following situation?
I have a Red Hat 5.5 server. Someone, somehow, managed to get two .nfs000.... type files that totaled over a terabyte in size. I removed them and thought things were back to normal. Then I started getting complains from... (2 Replies)
Discussion started by: geelsu
2 Replies
9. AIX
Hi,
I would like to know if /tmp file system is full, wheather it will affect the peformance of application installed on AIX. if Memory and CPU are not heavily utilized.
Regards,
Manoj. (1 Reply)
Discussion started by: manoj.solaris
1 Replies
10. UNIX for Dummies Questions & Answers
Hi guys,
In sun E250 server,root file system is full. we cleared log files in var/adm folder
syslogs,mail logs,crash logs are empty. This is a production server. we are not able to run fsck from single user mode. I have given output of df and du command.How to create space in root... (3 Replies)
Discussion started by: PUSHPARAJA
3 Replies
LEARN ABOUT REDHAT
e2image
E2IMAGE(8) System Manager's Manual E2IMAGE(8)
NAME
e2image - Save critical ext2 filesystem data to a file
SYNOPSIS
e2image [ -r ] device image-file
DESCRIPTION
The e2image program will save critical filesystem data on the ext2 filesystem located on device to a file specified by image-file. The
image file may be examined by dumpe2fs and debugfs, by using the -i option to those programs. This can be used by an expert in assisting
the recovery of catastrophically corrupted filesystems. In the future, e2fsck will be enhanced to be able to use the image file to help
recover a badly damaged filesystem.
If image-file is -, then the output of e2image will be sent to standard output.
The -r option will create a raw image file instead of a normal image file. A raw image file differs from a normal image file in two ways.
First, the filesystem metadata is placed in the proper position so that e2fsck, dumpe2fs, debugfs, etc. can be run directly on the raw
image file. In order to minimize the amount of disk space consumed by a raw image file, the file is created as a sparse file. (Beware of
copying or compressing/decompressing this file with utilities that don't understand how to create sparse files; the file will become as
large as the filesystem itself!) Secondly, the raw image file also includes indirect blocks and data blocks, which the current image file
does not have, although this may change in the future.
It is a very good idea to periodically (at boot time and every week or so) to create image files for all of filesystems on a system, as
well as saving the partition layout (which can be generated using the using fdisk -l command). Ideally the image file should be stored on
some filesystem other that the filesystem whose data it contains, to ensure that its data is accessible in the case where the filesystem
has been badly damaged.
To save disk space, e2image creates the image file as a sparse file. Hence, if the image file needs to be copied to another location, it
should either be compressed first or copied using the --sparse=always option to GNU version of cp.
The size of an ext2 image file depends primarily on the size of the filesystems and how many inodes are in use. For a typical 10 gigabyte
filesystem, with 200,000 inodes in use out of 1.2 million inodes, the image file be approximately 35 megabytes; a 4 gigabyte filesystem
with 15,000 inodes in use out of 550,000 inodes will result in a 3 megabyte image file. Image files tend to be quite compressible; an
image file taking up 32 megabytes of space on disk will generally compress down to 3 or 4 megabytes.
AUTHOR
e2image was written by Theodore Ts'o (tytso@mit.edu).
AVAILABILITY
e2image is part of the e2fsprogs package and is available from anonymous http://e2fsprogs.sourceforge.net.
SEE ALSO
dumpe2fs(8), debugfs(8)
E2fsprogs version 1.32 November 2002 E2IMAGE(8)