01-27-2009
Usually UNIX systems are picky about using an inode to reference a file for reading or writing -specifically because it bypasses security. If that is what you want it may be a problem.
You will have to use direct I/O - in other words, write a driver or (what Otheus is telling you) to do physical (sometimes called direct) I/O to a disk to retrieve the inode object.
This means you will have to understand filesystem internals.
What exact data are you after in the inode?
Last edited by otheus; 01-27-2009 at 12:04 PM..
Reason: inserted meaningful conjunction
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
When is a file "accessed" according to UNIX? For example: gzipping a file will not change the access time. (1 Reply)
Discussion started by: dangral
1 Replies
2. Shell Programming and Scripting
hi i am nitin...
jus a new kid on the block... my query is...
does the concept of region invovle sharin of inodes wen the sticky it is set... eg... if two process share two text regions... wat actually happens
thank u (1 Reply)
Discussion started by: nitinsharma_ssn
1 Replies
3. Filesystems, Disks and Memory
as kernel keeps track of user activities on a file by its INODE number and I node table .
what is the structure of Inode table. and where does this Inode table mapped into?user space or kernel space?
is the Inode Number is fixed for a file till its deletion?
thanks (1 Reply)
Discussion started by: compbug
1 Replies
4. Red Hat
hi,
can anyone please tell me where i can extract inode numbers and path associated with all file descriptors. i want these informations only. is there any system call or functions to get these things? i hav a RHEL 4. also /proc/pid/fd shows some file descriptor list. is that the proper path to... (1 Reply)
Discussion started by: sanjaykhuntia
1 Replies
5. Solaris
how can i see inode table information of a perticler inode.anybody knows pls tell me.
Than.Q (3 Replies)
Discussion started by: nag.mi2000
3 Replies
6. AIX
Hi Guys,
I have this filesystem got big with inode:
/dev/hd4 3670016 183664 95% 63705 58% /var
I don't know why the system doesn't give alerts on this FS although it's 95% and why the inode is 58%.
Any comments will be highly appreciated.
Thanks,
itik (1 Reply)
Discussion started by: itik
1 Replies
7. Programming
Hi,
may be this is an AIX noob question:
my current C++ application runs on Linux and is quite memory consuming. Therefore, the application writes a logfile after it has finished containing memory information, CPU information, information on the running other processes besides my application... (0 Replies)
Discussion started by: DarthVader77
0 Replies
8. UNIX for Dummies Questions & Answers
can someone please tell me why is the filename not inlcuded in the inode of the file? (2 Replies)
Discussion started by: wowman
2 Replies
9. Solaris
Dear,
How can i check inode information in my Solaris box?
With Regards,
Mjoshi (4 Replies)
Discussion started by: mjoshi87
4 Replies
10. UNIX for Dummies Questions & Answers
How do you find the maximum file size with the following information -:
A unix filesystem has 1024 bytes block size with 32-bit address. The i-node has 12 direct and 1 indirect, 1 double indirect, and 1 triple indirect addresses. What is the maximum file size it can access ?
What is the... (1 Reply)
Discussion started by: sreyan32
1 Replies
LEARN ABOUT REDHAT
xfs_ncheck
xfs_ncheck(8) System Manager's Manual xfs_ncheck(8)
NAME
xfs_ncheck - generate pathnames from i-numbers for XFS
SYNOPSIS
xfs_ncheck [ -i ino ] ... [ -f ] [ -s ] [ -l logdev ] device
DESCRIPTION
xfs_ncheck with no -i arguments generates an inode number and pathname list of all files on the given filesystem. Names of directory files
are followed by /.. The output is not sorted in any particular order. The filesystem to be examined is specified by the device argument,
which should be the disk or volume device for the filesystem. Filesystems stored in files can also be checked, using the -f flag.
OPTIONS
-f Specifies that the filesystem image to be processed is stored in a regular file at device (see the mkfs.xfs -d file option). This
might happen if an image copy of a filesystem has been made into an ordinary file.
-l logdev
Specifies the device where the filesystem's external log resides. Only for those filesystems which use an external log. See the
mkfs.xfs -l option, and refer to xfs(5) for a detailed description of the XFS log.
-s Limits the report to special files and files with setuserid mode. This option may be used to detect violations of security pol-
icy.
-i ino Limits the report to only those files whose inode numbers follow. May be given multiple times to select multiple inode numbers.
If the filesystem is seriously corrupted, or very busy and looks like it is corrupt, a message of the form that would be generated by
xfs_check(8) may appear.
xfs_ncheck is only useful with XFS filesystems.
SEE ALSO
mkfs.xfs(8), xfs_check(8), xfs(5).
xfs_ncheck(8)