Sponsored Content
Top Forums UNIX for Advanced & Expert Users How to access inode information Post 302280661 by jim mcnamara on Tuesday 27th of January 2009 10:56:39 AM
Old 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

file access inode update

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

INode

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

Inode number

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

inode no and fd path

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

about inode

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

FS inode 58%

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

C++ application: how to access AIX process and cpu information?

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

inode filename

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

inode in 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 max filesize with inode information ?

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
FFIND(1)						      General Commands Manual							  FFIND(1)

NAME
ffind - Finds the name of the file or directory using a given inode SYNOPSIS
ffind [-aduvV] [-f fstype] [-i imgtype] [-o imgoffset] [-b dev_sector_size] image inode DESCRIPTION
ffind finds the names of files or directories that are allocated to inode on disk image image. By default it only will only return the first name it finds. With some file systems, this will find deleted file names. ARGUMENTS
image [images] One (or more if split) disk or partition images whose format is given with '-i'. inode Integer of inode to find. The optional arguments are: -a Find all occurrences of inode. -d Find deleted entries only. -f fstype Identify the file system type of the image. Use '-f list' to list the supported file system types. If not given, autodetection methods are used. -u Find undeleted entries only. -i imgtype Identify the type of image file, such as raw or split. Use '-i list' to list the supported types. If not given, autodetection methods are used. -o imgoffset The sector offset where the file system starts in the image. -b dev_sector_size The size, in bytes, of the underlying device sectors. If not given, the value in the image format is used (if it exists) or 512-bytes is assumed. -v Verbose output to stderr. -V Display version. This program searches all directory entries looking for the given inode. This is useful when an inode has been identified from a disk unit address using ifind(1). EXAMPLE
# ffind -a image 212 SEE ALSO
ifind(1) AUTHOR
Brian Carrier <carrier at sleuthkit dot org> Send documentation updates to <doc-updates at sleuthkit dot org> FFIND(1)
All times are GMT -4. The time now is 02:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy