Sponsored Content
Full Discussion: File system full?
Operating Systems Solaris File system full? Post 46122 by RTM on Thursday 8th of January 2004 01:15:12 PM
Old 01-08-2004
/dev/dsk/c0t0d0s0 - that also doesn't give enough information. Normally that could be the / partition. But, if that is the only partition, then your real problem may be under / in either var, export/home, or some other directory.

More assistance can be given if you post the output from the df -k command. Also post what OS and version.

And I just can't resist - the blank one is the space bar.
 

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

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

5. 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

6. Solaris

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... (6 Replies)
Discussion started by: melanie_pfefer
6 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
disktab(5)							File Formats Manual							disktab(5)

Name
       disktab - disk description file

Syntax
       #include <disktab.h>

Description
       The file is a simple data base that describes disk geometries and disk partition characteristics.  The format is patterned after the termi-
       nal data base.  Entries in consist of a number of fields separated by colons (:).  The first entry for each disk gives the names  that  are
       known for the disk, separated by vertical bars (|).  The last name given should be a long name fully identifying the disk.

       The following list indicates the normal values stored for each disk entry:
       Name Type Description
       ns   num  Number of sectors per track
       nt   num  Number of tracks per cylinder
       nc   num  Total number of cylinders on the disk
       ba   num  Block size for partition `a' (bytes)
       bd   num  Block size for partition `d' (bytes)
       be   num  Block size for partition `e' (bytes)
       bf   num  Block size for partition `f' (bytes)
       bg   num  Block size for partition `g' (bytes)
       bh   num  Block size for partition `h' (bytes)
       fa   num  Fragment size for partition `a' (bytes)
       fd   num  Fragment size for partition `d' (bytes)
       fe   num  Fragment size for partition `e' (bytes)
       ff   num  Fragment size for partition `f' (bytes)
       fg   num  Fragment size for partition `g' (bytes)
       fh   num  Fragment size for partition `h' (bytes)
       pa   num  Size of partition `a' in sectors
       pb   num  Size of partition `b' in sectors
       pc   num  Size of partition `c' in sectors
       pd   num  Size of partition `d' in sectors
       pe   num  Size of partition `e' in sectors
       pf   num  Size of partition `f' in sectors
       pg   num  Size of partition `g' in sectors
       ph   num  Size of partition `h' in sectors
       se   num  Sector size in bytes
       ty   str  Type of disk (e.g. removable, winchester)

       The entries can be automatically generated with the program.

Files
See Also
       chpt(8), newfs(8)

																	disktab(5)
All times are GMT -4. The time now is 11:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy