Sponsored Content
Full Discussion: SCO Unix inode structure.
Top Forums UNIX for Dummies Questions & Answers SCO Unix inode structure. Post 302118874 by rbn on Thursday 24th of May 2007 07:41:40 PM
Old 05-24-2007
SCO Unix inode structure.

I have read quite a few threads here about the unix file creation date. I was interested in finding how to display it using a unix command. find did not help me so i looked at man inode. I found direction to htino.h which is described as the
structure of the inode for S51K (UNIX), HTFS, EAFS and AFS. In this file I found
a structure dinode32 which contained the atime, mtime, ctime, and crtime with the crtime being the "/*time file was created*/".

Does anyone know if this is being used by anyone and whether or not this is true for linux?

thank you
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix/Linux Directory Structure

Does anyone know of a good Internet source that explains the directory structure of Unix/Linux?? Thanks Gregg (2 Replies)
Discussion started by: gdboling
2 Replies

2. Filesystems, Disks and Memory

SCO TCP/IP runtime System for SCO Unix

Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine... (0 Replies)
Discussion started by: Cerberus
0 Replies

3. Filesystems, Disks and Memory

inode data structure

the superblock has the offset for inode table. My question is 1) whether it starts relative to the start of the first cylinder group or is it relative to the start of filesystem??? 2)and also which entry corresponds to the root(/) inode?? is it second or third entry??? My questions are... (4 Replies)
Discussion started by: anwerreyaz
4 Replies

4. UNIX for Dummies Questions & Answers

What are some benefits of the UNIX hierarchical file structure?

What are some benefits of the UNIX hierarchical file structure? I am new to UNIX and researching some information about it for a class so please help if you can. Thanks. (1 Reply)
Discussion started by: 88923JJJSDK
1 Replies

5. UNIX for Dummies Questions & Answers

Not quite related to Unix but CP/M file structure...

I'm not sure where to post this but I'm having some trouble with the directories in CP/M... I'm sorry about the length but I'm totally confused... I've seen that the directory entry in CP/M contains the following: 1 byte User Code 8 bytes Filename 3 bytes File extension 1 byte Extension 2... (3 Replies)
Discussion started by: Legend986
3 Replies

6. SCO

load sco xenix and sco unix binary ?

Hi I have some sco xenix object, bin and archive files that operate in sco unix 5.0.7. I know that sco unix kernel can support sco xenix binary. I want to know how can I link xenix and unix archives together? (0 Replies)
Discussion started by: javad1_maroofi
0 Replies

7. UNIX for Dummies Questions & Answers

UNIX command to get inode's tid and pid

Hi everyone, I am new here in www.unix.com, i found this site because I am looking for an answer to this problem of mine. I need to know a UNIX command to display an inode's thread id and process id. Hope someone can help me on this. Thanks :D (8 Replies)
Discussion started by: rodkun
8 Replies

8. Programming

Parsing unix STAT structure

Hi I am creating a utility which needs to create a log file under the path represented by an environment variable. The condition is that this path must be a valid DIRECTORY PATH. So i need to determine that the path is indeed a VALID DIRECTORY PATH. I have written a function which will return... (2 Replies)
Discussion started by: skyineyes
2 Replies

9. Shell Programming and Scripting

How can I get only FileName associated with a INODE on Unix much faster?

How can I get only FileName associated with a INODE on Unix in seconds instead of minutes, as it is the case for me as shown below. # Say I have FileDescriptor: 43, INODE: 2590784, File: abc.rdb. I want to get only filename associated with inode:2590784 and FD:43. $> time find / -inum... (7 Replies)
Discussion started by: kchinnam
7 Replies

10. Shell Programming and Scripting

Getting the Folder Structure in Unix

Hi All, I have a compute box and I want to tar directory structure under a directory and then Deploy/untar it in a new compute box so that the directory structure will be exactly the same. I do not want any of the file to be extracted and deployed but instead only the directory structure. ... (2 Replies)
Discussion started by: filter
2 Replies
VOLINFO(8)						       AFS Command Reference							VOLINFO(8)

NAME
volinfo - Produces detailed statistics about AFS volume headers SYNOPSIS
volinfo [-online] [-vnode] [-date] [-inode] [-itime] [-part <AFS partition name (default current partition)>+] [-volumeid <volume id>+] [-header] [-sizeOnly] [-fixheader] [-saveinodes] [-orphaned] [-help] DESCRIPTION
The volinfo command displays detailed statistics about one or more volume headers and the partition that houses them. The command must be issued on a file server machine and by default produces output for every volume on every AFS server partition on the machine. To display output for the volumes on one partition only, include the -part argument. To display output for one volume only, include the -volumeid argument. OPTIONS
-online Is nonoperational. -vnode Displays a table for each volume which lists the large (directory) and small (file) vnodes in it, in addition to the default output. -date When combined with the -vnode flag, adds the "ServerModTime" field to each vnode entry in the large vnode and small vnode tables, reporting its most recent modification time. -inode When combined with the -vnode flag, adds the "inode" field to each vnode entry in the large vnode and small vnode tables, reporting the associated inode number. -itime When combined with the -vnode flag, displays a change, modification, and access timestamp for each of the large vnode and small vnode tables. -part <partition name>+ Specifies the partition that houses each volume for which to produce output. Use the format /vicepxx, where xx is one or two lowercase letters. This argument can be omitted if the current working directory is the mount location for an AFS server partition; it is not the mount location for an AFS server partition, the command produces output for every volume on all local AFS server partitions. -volumeid <volume id>+ Specifies the ID number of one volume for which to produce output. The -part argument must be provided along with this one unless the current working directory is the mount location for the AFS server partition that houses the volume. -header Displays statistics about the volume header of each volume, in addition to the default output. -sizeOnly Displays a single line of output for each volume, reporting the size of various structures associated with it. The default output is suppressed and any flags that modify it (such as -vnode) are ignored. -fixheader Repairs damaged inodes in each volume if possible. If there are any, it reports the action it is taking to repair them. Otherwise, it produces no output in addition to the default output. -saveinodes Creates a file in the current working directory for each inode in each volume. Each file is called TmpInode.vnode_number and contains the inode's contents. The default output is suppressed and any flags that modify it (such as -vnode) are ignored. -orphaned Displays a large vnode and small vnode table for each volume, which lists only orphaned vnodes (vnodes that have no parent). If there are none, the tables are empty (only the headers appear). -help Prints the online help for this command. All other valid options are ignored. OUTPUT
By default, the command produces several line of statistics for each volume. Adding other options produces or substitutes additional information as described in OPTIONS. The output is intended for debugging purposes and is meaningful to someone familiar with the internal structure of volume headers. PRIVILEGE REQUIRED
The issuer must be logged in as the local superuser "root". SEE ALSO
vldb.DB0(5), volserver(8) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 VOLINFO(8)
All times are GMT -4. The time now is 09:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy