12-20-2013
Quote:
Originally Posted by
kenshinhimura
the inodes are good since the FILESYTEM is just 58%
Note: the
space on the filesystem is used to store data, the
inodes are used to store metadata. If your files are big enough you run out of space, if your files are many enough you run out of inodes.
Quote:
Originally Posted by
kenshinhimura
permission denied
Now, this is something entirely different: you do not lack space, you lack permissions.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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. UNIX for Dummies Questions & Answers
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
3. Red Hat
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
4. UNIX for Dummies Questions & Answers
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
5. Cybersecurity
User usrA creates dirA directory and runs chmod 777 on the directory. Can usrB issue another 777 on dirA? It appears the answer is no even if the usrA and usrB are part of the same group. I know this is a rare scenario but I just ran across it and found out that usrB receives an error when... (4 Replies)
Discussion started by: zlek131
4 Replies
6. Solaris
Hello Guruz,
Relay bad condition :mad:
Some has changed the permission to 777 recursively for /usr/bin directory by mistake. Now all the permission looks to be 777 on /usr/bin
Hence I am so many system related errors as 1 show below.
When I am trying to change the password, I am getting... (5 Replies)
Discussion started by: bullz26
5 Replies
7. Shell Programming and Scripting
Here is the sample code I'm trying to execute. I see that the permission on the file is set to 755 always I want to change it to 777. Please help me with this.
code :
#!/usr/bin/perl
use File::Path qw(make_path remove_tree);
my $path = "2010/sam";
make_path($path,{mode=>0777});
... (1 Reply)
Discussion started by: hansini
1 Replies
8. Shell Programming and Scripting
Hi All,
Is there any unix(solaris) command to get file permissions in 777 format or do we need to write some script for it? (7 Replies)
Discussion started by: rishav
7 Replies
9. UNIX for Dummies Questions & Answers
Hi Guys,
I want to know is there any method to create a file having 777 permission. I am aware of umask, since it is only giving max. 666 permission for files this is not fulfilling my needs.
Thanks in advance
---------- Post updated at 12:49 AM ---------- Previous update was at 12:31... (10 Replies)
Discussion started by: sanoop
10 Replies
10. Solaris
Hey Guys,
I need your help.
My NIS server filesystem is 100%, the NIS is running under solaris 10.
I am affraid if the server stops, it wont come up again.
Please help. (4 Replies)
Discussion started by: andrevicente
4 Replies
df_hfs(1M) df_hfs(1M)
NAME
df_hfs: df - report number of free CDFS, HFS, or NFS file system disk blocks
SYNOPSIS
FStype] specific_options] [special|directory]...
DESCRIPTION
The command displays the number of free 512-byte blocks and free inodes available for file systems by examining the counts kept in the
superblock or superblocks. If a special or a directory is not specified, the free space on all mounted file systems is displayed. If the
arguments to are path names, reports on the file systems containing the named files. If the argument to is a special of an unmounted file
system, the free space in the unmounted file system is displayed.
Options
recognizes the following options:
Report only the number of kilobytes (KB) free.
Report the total number of blocks allocated for swapping to the file system
as well as the number of blocks free for swapping to the file system. This option is supported on HFS file systems
only.
Report the number of files free.
Report only the actual count of the blocks in the free list
(free inodes are not reported). When this option is specified, reports on raw devices.
Report only on the
FStype file system type (see fstyp(1M)). For the purposes of this manual entry, FStype can be one of and for the
CDFS, HFS, and NFS file systems, respectively.
Report the entire structure described in
statvfs(2).
Report the total number of inodes,
the number of free inodes, number of used inodes, and the percentage of inodes in use.
Report the allocation in kilobytes (KB).
Report on local file systems only.
Report the file system name.
If used with no other options, display a list of mounted file system types.
Specify options specific to the HFS file system type.
specific_options is a comma-separated list of suboptions.
The available suboption is:
Report the number of used and free inodes.
Report the total allocated block figures and the number of free blocks.
Report the percentage of blocks used,
the number of blocks used, and the number of blocks free. This option cannot be used with other options.
Echo the completed command line, but perform no other action.
The command line is generated by incorporating the user-specified options and other information derived from This
option allows the user to verify the command line.
When is used on an HFS file system, the file space reported is the space available to the ordinary user, and does not include the reserved
file space specified by
Unreported reserved blocks are available only to users who have appropriate privileges. See tunefs(1M) for information about
When is used on NFS file systems, the number of inodes is displayed as -1 . This is due to superuser access restrictions over NFS.
EXAMPLES
Report the number of free disk blocks for all mounted file systems:
Report the number of free disk blocks for all mounted HFS file systems:
Report the number of free files for all mounted NFS file systems:
Report the total allocated block figures and the number of free blocks, for all mounted file systems:
Report the total allocated block figures and the number of free blocks, for the file system mounted as /usr:
WARNINGS
does not account for:
o Disk space reserved for swap space,
o Space used for the HFS boot block (8K bytes, 1 per file system),
o HFS superblocks (8K bytes each, 1 per disk cylinder),
o HFS cylinder group blocks (1K-8K bytes each, 1 per cylinder group),
o Inodes (currently 128 bytes reserved for each inode).
Non-HFS file systems may have other items that this command does not account for.
The option, from prior releases, has been replaced by the option.
FILES
File system devices.
Static information about the file systems
Mounted file system table
SEE ALSO
du(1), df(1M), fsck(1M), fstab(4), fstyp(1M), statvfs(2), mnttab(4).
STANDARDS CONFORMANCE
df_hfs(1M)