HPE GreenLake Administration
Operating System - HP-UX
1842553
Members
2570
Online
110189
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-28-2009 05:33 AM
12-28-2009 05:33 AM
Hello,
Can you define inodes and how it is being used in hp for troubleshooting and the relation on on lost+found directories while fsck.
thanks in advance
Can you define inodes and how it is being used in hp for troubleshooting and the relation on on lost+found directories while fsck.
thanks in advance
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-28-2009 07:03 AM
12-28-2009 07:03 AM
Solution
http://en.wikipedia.org/wiki/Inode
In a unix-style filesystem, a file can have multiple names if it has multiple hard links (directory entries) pointing to it. Therefore, the fundamental identifier for the file is *not* the filename, but the inode number.
The inode itself is a filesystem meta-data structure that contains the basic information about the file: how to find the file's data blocks on the disk, the file's length, timestamps, permissions and ownership information.
Usually the filesystem is allowed to manage the inode numbers, because filenames are so much more convenient for humans.
But if someone has accidentally created a file that has a strange name (e.g. it contains strange Unicode characters you cannot properly display or type), you can use "-inum" option of the find command to manipulate the file based on its inode number.
Also if filesystem's directory structure is corrupted so that the names of some files are completely lost, the fsck will rescue such orphaned files by placing them into the filesystem's /lost+found directory and giving them new names that match their inode numbers. The inode numbers are guaranteed to be unique on the disk, so the generated names should not collide with anything that already exists in /lost+found.
The sysadmin must then try and identify the files, based on the file content and ownership information.
MK
In a unix-style filesystem, a file can have multiple names if it has multiple hard links (directory entries) pointing to it. Therefore, the fundamental identifier for the file is *not* the filename, but the inode number.
The inode itself is a filesystem meta-data structure that contains the basic information about the file: how to find the file's data blocks on the disk, the file's length, timestamps, permissions and ownership information.
Usually the filesystem is allowed to manage the inode numbers, because filenames are so much more convenient for humans.
But if someone has accidentally created a file that has a strange name (e.g. it contains strange Unicode characters you cannot properly display or type), you can use "-inum" option of the find command to manipulate the file based on its inode number.
Also if filesystem's directory structure is corrupted so that the names of some files are completely lost, the fsck will rescue such orphaned files by placing them into the filesystem's /lost+found directory and giving them new names that match their inode numbers. The inode numbers are guaranteed to be unique on the disk, so the generated names should not collide with anything that already exists in /lost+found.
The sysadmin must then try and identify the files, based on the file content and ownership information.
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-28-2009 07:27 AM
12-28-2009 07:27 AM
Re: inodes
Hi:
To add to Matti's excellent post, an inode number is only unique within a filesystem. That is, a file in the mounted '/usr' filesystem can have the same inode number as a file in the mounted '/opt' filesystem.
Therefore, be very careful if you are searching a removing files by inode number. Doing a 'find()' in the '/' directory would visit all subordinate mountpoints unless you used the '-xdev' option to confine searching to the '/' mountpoint (which would include the '/etc', and '/sbin' directories since they are not mountpoints).
It can be useful to know, too, that the inode number of a mounted filesystem is always two (2).
Regards!
...JRF...
To add to Matti's excellent post, an inode number is only unique within a filesystem. That is, a file in the mounted '/usr' filesystem can have the same inode number as a file in the mounted '/opt' filesystem.
Therefore, be very careful if you are searching a removing files by inode number. Doing a 'find()' in the '/' directory would visit all subordinate mountpoints unless you used the '-xdev' option to confine searching to the '/' mountpoint (which would include the '/etc', and '/sbin' directories since they are not mountpoints).
It can be useful to know, too, that the inode number of a mounted filesystem is always two (2).
Regards!
...JRF...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP