Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Need little help in understanding UNIX file system. Post 302970579 by Narendra Eliset on Friday 8th of April 2016 09:21:31 AM
Old 04-08-2016
Need little help in understanding UNIX file system.

statement 1 :
I see everyone saying Unix follows a tree like hierarchial structure.
Statement 2:
Unix file system has four blocks
1.boot block
2.super block
3.inodes
4.data block
My question is , in which of the above four blocks , the hierarchial structure comes.?? How could we corelate both of the above statements.please explain.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How do I send a file as an attachment (gzip file) on a Unix system

Hi, How do I send a file as an attachment (gzip file) on a Unix system ? Using sendmail. Please help me. :confused: (3 Replies)
Discussion started by: lacca
3 Replies

2. UNIX for Dummies Questions & Answers

Understanding System Vish startup scripts

I'm trying to get a clear picture of how startup scripts are executed during bootup. When run-level N is entered, the scripts in /rcN.d are executed. I understand that the S* scripts are executed in numerical order during bootup. What I don't understand is if the K* scripts are executed... (0 Replies)
Discussion started by: darkmatter14B
0 Replies

3. HP-UX

Understanding File System

Hey guys im confused with the difference of these filesystems /bin, /sbin, /usr/bin, /usr/sbin. They all look like the same. (2 Replies)
Discussion started by: sbn
2 Replies

4. Programming

compare XML/flat file with UNIX file system structure

Before i start doing something, I wanted to know whether the approach to compare XML file with UNIX file system structure. I have a pre-configured file(contains a list of paths to executables) and i need to check against the UNIX directory structure. what are the various approches should i use ? I... (6 Replies)
Discussion started by: shafi2all
6 Replies

5. Homework & Coursework Questions

fork system call understanding

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: i have a problem in understanding the behaviour of fork . i understood fork as to create a new process and... (4 Replies)
Discussion started by: MrUser
4 Replies

6. UNIX for Dummies Questions & Answers

Unix file system

which one is correct explanaton for unix file system a. Explaining about directory hierarchy or b. Explaining about boot block , super block? (1 Reply)
Discussion started by: gwgreen1
1 Replies

7. UNIX for Advanced & Expert Users

UNIX FILE SYSTEM

Dear All, We are using COMPAQ DS -10 machines with UNIX 4.0F System is behaving abnormal some directories shows full and they should not be . here is df -k output of a machines file system----1024 block-----used--available--capacity--mounted on /dev/rz17h-----8680793----- 1 --- ... (1 Reply)
Discussion started by: akash.jahangir
1 Replies

8. UNIX for Dummies Questions & Answers

Understanding File System

Can anybody provide me some good articles / links which will help me understand linux file system internals? I want to understand how a file when accessed from user mode through its file name resolves to particular memory location on memory. Where does the super, dentry and inodes come into... (2 Replies)
Discussion started by: rupeshkp728
2 Replies

9. Shell Programming and Scripting

UNIX file system to Linux file system migration

We would be migrating UNIX file system to Linux file system. We do have many directory and sub directories with files. after migrating unix to linux file system , i want to make sure all the files has been copied ? What would be the best approach to validate directory ,sub-directory and file... (1 Reply)
Discussion started by: balajikalai
1 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)
All times are GMT -4. The time now is 05:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy