Sponsored Content
Operating Systems Linux /root filesystem size is full Post 302075529 by hegemaro on Sunday 4th of June 2006 06:36:28 PM
Old 06-04-2006
It has been my experiece that the smit log and shell histories sneak up growing very large and numerous over time. Also, do you have automated processes that cleanup or archive key files such as passwd by making copies? It could easily be one very large file or a huge number of little files once thought innocuous.

Good luck. I'd be interested in what you find.
This User Gave Thanks to hegemaro For This Post:
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Filesystem Full

I noticed that whenever something is printed from my workstation, the available disk space in the /dev/dsk/c0t0d0s0 decreases considerably. Hence, after using my workstation for sometime, I encounter an error message: "Filesystem Full" that prevents me from printing any further. Is there a way to... (16 Replies)
Discussion started by: ilak1008
16 Replies

2. SCO

Maximum size of root filesystem in SCO 5.0.7

Does anyone know the maximum size of the root filesystem in SCO 5.0.7.? It used to be 1GB max. SCO 5.0.7 with Development System does not fit in 1GB. Is there a limit or has it been removed and the documenation just was not updated? TIA, Dan (2 Replies)
Discussion started by: njsco
2 Replies

3. UNIX for Dummies Questions & Answers

filesystem full

my root filesystem is eventually full "/dev/rdsk/c1d0s0" as a result i cannot boot to the operating system, i booted into the fail safe mode to check the space using df -h command i discover that it is eventually full. Also to my amazement i found that i cannot see the filesystem which mounted on... (1 Reply)
Discussion started by: seyiisq
1 Replies

4. Red Hat

/ filesystem getting full

Hi All, How do I increase the root filesystem? It's getting full. / 90% Here's the break down, below 232 dev 5624 tmp *6764 bin 16860 root *19680 sbin *20436 lib64 28329 boot *47992 etc 150012 var *254540 lib 651708 home *2445044 usr (5 Replies)
Discussion started by: itik
5 Replies

5. UNIX for Dummies Questions & Answers

filesystem is full

Hello everybody, a very basic question. Inspite of me deleting huge files in a filesystem(AIX 5.3) in oracle folder, the filesystem when i check using df -k still shows 100% full. Does that mean there is a process still pointing to the files which i deleted. how do i work around this. Thanks!... (3 Replies)
Discussion started by: karthikosu
3 Replies

6. Solaris

Filesystem Full

In our shop we have to run a batch cycle. Every so often while we are running batch we get a filesystem full situation that causes batch to stop or slow down. Anyway, the practiced procedure is to look for large files and zip them. This takes a lot of time. We are in a sun solaris environment. What... (1 Reply)
Discussion started by: Harleyrci
1 Replies

7. Solaris

How to resolve Filesystem Full?

I have experienced Filesystem full (%iused = 100%) as below. I have tried to remove a lot of garbage but it still become full soon. # df -F ufs -o i Filesystem       iused    ifree  %iused  Mount /dev/dsk/c0t0d0s0  512000     0   100%  / /dev/dsk/c0t0d0s3   1887   382113   0%  /cms Other... (4 Replies)
Discussion started by: SwordCar
4 Replies

8. UNIX for Advanced & Expert Users

Physical disk IO size smaller than fragment block filesystem size ?

Hello, in one default UFS filesystem we have 8K block size (bsize) and 1K fragmentsize (fsize). At this scenary I thought all "FileSytem IO" will be 8K (or greater) but never smaller than the fragment size (1K). If a UFS fragment/blocksize is allwasy several ADJACENTS sectors on disk (in a ... (4 Replies)
Discussion started by: rarino2
4 Replies
PG_ARCHIVECLEANUP(1)					  PostgreSQL 9.2.7 Documentation				      PG_ARCHIVECLEANUP(1)

NAME
pg_archivecleanup - clean up PostgreSQL WAL archive files SYNOPSIS
pg_archivecleanup [option...] archivelocation oldestkeptwalfile DESCRIPTION
pg_archivecleanup is designed to be used as an archive_cleanup_command to clean up WAL file archives when running as a standby server (see Section 25.2, "Log-Shipping Standby Servers", in the documentation). pg_archivecleanup can also be used as a standalone program to clean WAL file archives. To configure a standby server to use pg_archivecleanup, put this into its recovery.conf configuration file: archive_cleanup_command = 'pg_archivecleanup archivelocation %r' where archivelocation is the directory from which WAL segment files should be removed. When used within archive_cleanup_command, all WAL files logically preceding the value of the %r argument will be removed from archivelocation. This minimizes the number of files that need to be retained, while preserving crash-restart capability. Use of this parameter is appropriate if the archivelocation is a transient staging area for this particular standby server, but not when the archivelocation is intended as a long-term WAL archive area, or when multiple standby servers are recovering from the same archive location. When used as a standalone program all WAL files logically preceding the oldestkeptwalfile will be removed from archivelocation. In this mode, if you specify a .backup file name, then only the file prefix will be used as the oldestkeptwalfile. This allows you to remove all WAL files archived prior to a specific base backup without error. For example, the following example will remove all files older than WAL file name 000000010000003700000010: pg_archivecleanup -d archive 000000010000003700000010.00000020.backup pg_archivecleanup: keep WAL file "archive/000000010000003700000010" and later pg_archivecleanup: removing file "archive/00000001000000370000000F" pg_archivecleanup: removing file "archive/00000001000000370000000E" pg_archivecleanup assumes that archivelocation is a directory readable and writable by the server-owning user. OPTIONS
pg_archivecleanup accepts the following command-line arguments: -d Print lots of debug logging output on stderr. -n Print the names of the files that would have been removed on stdout (performs a dry run). -V, --version Print the pg_archivecleanup version and exit. -x extension When using the program as a standalone utility, provide an extension that will be stripped from all file names before deciding if they should be deleted. This is typically useful for cleaning up archives that have been compressed during storage, and therefore have had an extension added by the compression program. For example: -x .gz. Note that the .backup file name passed to the program should not include the extension. -?, --help Show help about pg_archivecleanup command line arguments, and exit. NOTES
pg_archivecleanup is designed to work with PostgreSQL 8.0 and later when used as a standalone utility, or with PostgreSQL 9.0 and later when used as an archive cleanup command. pg_archivecleanup is written in C and has an easy-to-modify source code, with specifically designated sections to modify for your own needs EXAMPLES
On Linux or Unix systems, you might use: archive_cleanup_command = 'pg_archivecleanup -d /mnt/standby/archive %r 2>>cleanup.log' where the archive directory is physically located on the standby server, so that the archive_command is accessing it across NFS, but the files are local to the standby. This will: o produce debugging output in cleanup.log o remove no-longer-needed files from the archive directory AUTHOR
Simon Riggs <simon@2ndquadrant.com> SEE ALSO
pg_standby(1) PostgreSQL 9.2.7 2014-02-17 PG_ARCHIVECLEANUP(1)
All times are GMT -4. The time now is 04:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy