hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4434) Provide a mapping from INodeId to INode
Date Thu, 11 Apr 2013 16:45:16 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629097#comment-13629097
] 

Suresh Srinivas commented on HDFS-4434:
---------------------------------------

bq. I'm curious what the theorized need is for reserved inode numbers? It seems that by trying
to account for entirely unknown features, we are adding a restriction that may not be correct
and/or sufficient.
First I think Sanjay's comment meant not reserving bits, but reserving range of numbers. That
is 0-16385 is reserved for future purposes. Reserving bits and number for future purposes
is a common practice. I would like to hear your thoughts on why you think it may not be correct.
I also am not sure I understand what you mean by sufficient. Do you mean 0-16385 may not be
sufficient?

See reserved/special inodes in [ext4|https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Special_inodes].


0 is used as invalid/default inode ID. 

                
> Provide a mapping from INodeId to INode
> ---------------------------------------
>
>                 Key: HDFS-4434
>                 URL: https://issues.apache.org/jira/browse/HDFS-4434
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: 3.0.0
>            Reporter: Brandon Li
>            Assignee: Suresh Srinivas
>         Attachments: HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch,
HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch,
HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch,
HDFS-4434.patch
>
>
> This JIRA is to provide a way to access the INode via its id. The proposed solution is
to have an in-memory mapping from INodeId to INode. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message