[
https://issues.apache.org/jira/browse/HADOOP-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631875#action_12631875
]
Konstantin Shvachko commented on HADOOP-3938:
---------------------------------------------
Steve, what I meant is that you cannot (naturally, using hdfs methods) create
an image which violates a quota.
You can obviously write an arbitrary number instead of the existing quota value
directly in the fsimage file if you know where, but this is not a "valid" way.
BTW, this issue is about hdfs (distributed) space quotas, not sure that
determining "disk space use" helps a lot.
> Quotas for disk space management
> --------------------------------
>
> Key: HADOOP-3938
> URL: https://issues.apache.org/jira/browse/HADOOP-3938
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Reporter: Robert Chansler
> Assignee: Raghu Angadi
> Fix For: 0.19.0
>
> Attachments: HADOOP-3938.patch, HADOOP-3938.patch, HADOOP-3938.patch,
> HADOOP-3938.patch, HADOOP-3938.patch, HADOOP-3938.patch,
> hdfs_quota_admin_guide.pdf, hdfs_quota_admin_guide.xml
>
>
> Directory quotas for bytes limit the number of bytes used by files in and
> below the directory. Operation is independent of name quotas (HADOOP-3187),
> but the implementation is parallel. Each file is charged according to its
> length multiplied by its intended replication factor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
