Sponsored Content
Full Discussion: file system full
Operating Systems Solaris file system full Post 302199262 by melanie_pfefer on Monday 26th of May 2008 08:25:10 AM
Old 05-26-2008
file system full

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 that might cause this behavior?

I also issue du (disk usage) and the result was conform with the result of df.

thx
 

9 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

file system full

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

Full File System

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. Filesystems, Disks and Memory

root file system full

Hi I have a Solaris 2.5.1 system. Recently my file system is full and i couldn't find what flood my root file system. Anyone can suggext any directories i should look out for. I am using Samba and Patrol agent. I am just usng this server as a file server, users cannot login into the system,... (1 Reply)
Discussion started by: owls
1 Replies

4. Solaris

File system full?

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

5. Solaris

Full file system?

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

6. Solaris

file system full

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

7. Solaris

/ file system full issue

Hi All, This is Babu working as a system administrator. Here I am getting one problem with one of my Sun server's root (/) file system. In df -h command / file system showing 7.8 GB used space.But in du -hd command it showing 5.2 gb only. Please can any one help me resolve this issue... (2 Replies)
Discussion started by: lbreddy
2 Replies

8. UNIX for Advanced & Expert Users

/opt file system full !!!

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

9. Red Hat

File system full, but not really.

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

NAME
diskusg - Generates disk accounting data by user ID SYNOPSIS
diskusg [-U number] [-s] [-v] [-p pw_filename] [-u u_filename] [-i ignlist] [ file_spec ...] The diskusg command generates intermediate disk accounting information and writes one record per user to standard output. PARAMETERS
Specifies one or more file systems. How you specify a file system depends on whether it is UFS or AdvFS and whether it is mounted. To specify a UFS file system that is mounted, enter the name of its character device special file, for example: /dev/rrz3c. To specify a UFS file system that is not mounted, enter the name of its block device special file, for example: /dev/rz3c. To specify an AdvFS fileset that is mounted, enter the name of the file domain, a pound-sign(#) character, and the name of the file- set, for example: root_domain#root. You cannot specify an AdvFS file system that is not mounted. FLAGS
Sets the number of internal allocated user structures to the specified number, one for each user. The default is 1000. Ignores the data in the specified ignlist file system. The ignlist parameter specifies a list of file system names, separated with commas or enclosed by quotation marks. Uses the specified pw_filename file as the password file used to generate login names. The default password file is /etc/passwd. Combines all records for a single user into a single record. Input data must be in the same format as the output of the diskusg command. If you specify the file_spec parameter with the -s flag, the parameter must be an ASCII file containing data in the appropriate format. If the file_spec parameter is not specified, input data will be taken from standard input. Writes a record to u_file- name for each file that has changed its user ID to user no one. Each record consists of the special file name, the inode number, and the user ID. Writes a list of all files charged to user no one to standard error. DESCRIPTION
The diskusg command generates intermediate disk accounting information about files in the specified file_spec or from standard input. The diskusg command obtains user login names from the /etc/passwd file, by default, and reports one record per user to standard output. The command usually reads only the inodes of the specified file system. The diskusg command is usually called from the dodisk shell procedure when the cron daemon executes commands in the /usr/spool/cron/crontabs/root file. You can also manually invoke the command. If the diskusg command is executed from the dodisk command, its output is directed to the /var/adm/dtmp file, which is used as input to the acctdisk command to produce a total accounting record. This total accounting record can be merged with other total accounting records to produce a daily report. Note that if the -o flag is specified with the dodisk command, the acctdusg command is used instead of the diskusg command. The acctdusg command provides a more thorough accounting of disk usage than the diskusg command. Records output by the diskusg command are in the following format: user_ID login_name disk_blocks The output contains the following information: Assigned user number User login name Total number of disk blocks allocated to the user NOTES
This command can be used only for local devices. The command's behavior when it encounters a nonexisting UFS file system is different from its behavior when it encounters a nonexisting AdvFS fileset. If the nonexisting file_spec is a UFS file system, the command produces an error and continue to display output for other file systems and filesets. If the missing file_spec is an AdvFS fileset, the command exits without producing any output. EXAMPLES
To manually invoke the diskusg command, you must be logged in as superuser. For example, you could enter the following command: # /usr/sbin/acct/diskusg /dev/rrz3a 0 root 63652 1 daemon 84 2 bin 71144 4 adm 976 5 uucp 3324 322 homer 2 521 whistler 2 943 cellini 363 1016 pollock 92 1098 hopper 317 To generate daily disk accounting information, add a line similar to the following to the /usr/spool/cron/crontabs/root file: 0 2 * * 4 /usr/sbin/acct/dodisk The previous example shows a typical, periodically invoked command that the cron daemon reads and executes. The time period is expressed by a 6-field entry using the format: mm hh dayofmonth month wkday command The previous format shows the following information: The number of minutes past the hour, from 0 to 59 The hour of the day in 24-hour clock notation The day of the month The month, from 1 to 12 The day or days of the week, from 0 to 6, where 0 is Sunday and inclusive days are separated with a - (hyphen) The command that the cron daemon must execute. Unspecified times must use an * (asterisk) to define an empty field. In the previous example, the dodisk shell procedure runs at 02:00 hours (2) every Thursday (4). Usually, the dodisk shell procedure calls the diskusg command to redirect its output to a temporary file and then calls acctdisk to redirect disk usage records from the temporary file as input to the /var/adm/acct/nite/[filename] file as output. The file stored in the /var/adm/acct/nite subdirectory is a permanent binary record of disk usage for the specified period. FILES
Specifies the command path. Accounting header files that define formats for writing accounting files. User database file. RELATED INFORMATION
Commands: acct(8), dodisk(8), runacct(8), acctmerg(8), acctdusg(8), acctdisk(8) Functions: acct(2) System Administration delim off diskusg(8)
All times are GMT -4. The time now is 09:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy