[Lustre-discuss] FIDs and client side 64 bit inodes

[Kristen J. Webb]

Here is my current lustre version for testing:

# cat /proc/fs/lustre/version
lustre: 2.6.92
kernel: patchless_client

I've noticed that my changelog records look a lot like generated inodes.  From a 
changelog entry:

	[0x200000bd2:0x13a:0x0]

And from ls -i on a lustre client:

	144115238843711802 (0x200000BD200013A)

This is nice, if I split the inode number into the sequence and oid numbers 
(ignoring the version for now) I can use this in calls like

	lfs fid2path

Will I always be able to do this with 64 bit inodes that I get with calls like 
ls -i on a lustre client?

If not, then is it accurate to say that at any point in time, for each unique 
file in a lustre file system, there is only one FID=[seq:oid:ver] that can be 
used to generate a unique 64 bit inode for clients (even if the value of the 
inode does not map backwards like the example above)?


Kris
-- 
This message is NOT encrypted
--------------------------------
Mr. Kristen J. Webb
Chief Technology Officer
Teradactyl LLC.
2450 Baylor Dr. S.E.
Albuquerque, New Mexico 87106
Phone: 1-505-338-6000
Email: kwebb at teradactyl.com
Web: http://www.teradactyl.com

Providers of Scalable Backup Solutions
    for Unique Data Environments

--------------------------------
NOTICE TO RECIPIENTS: Any information contained in or attached to this message 
is intended solely for the use of the intended recipient(s). If you are not the 
intended recipient of this transmittal, you are hereby notified that you 
received this transmittal in error, and we request that you please delete and 
destroy all copies and attachments in your possession, notify the sender that 
you have received this communication in error, and note that any review or 
dissemination of, or the taking of any action in reliance on, this communication 
is expressly prohibited.


Regular internet e-mail transmission cannot be guaranteed to be secure or 
error-free. Therefore, we do not represent that this information is complete or 
accurate, and it should not be relied upon as such. If you prefer to communicate 
with Teradactyl LLC. using secure (i.e., encrypted and/or digitally signed) 
e-mail transmission, please notify the sender. Otherwise, you will be deemed to 
have consented to communicate with Teradactyl via regular internet e-mail 
transmission. Please note that Teradactyl reserves the right to intercept, 
monitor, and retain all e-mail messages (including secure e-mail messages) sent 
to or from its systems as permitted by applicable law.