[
https://issues.apache.org/jira/browse/HADOOP-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571701#action_12571701
]
Martin Traverso commented on HADOOP-2845:
-----------------------------------------
> Can't believe ZFS doesn't have meta-data synchronization
It does, but apparently space usage calculation doesn't qualify. From zfs man
page:
"Committing a change to a disk using fsync(3c) or
O_SYNC does not necessarily guarantee that the space
usage information is updated immediately."
> Yes, 0 is stable. I du files that's been created last year and get the same
> result.
I was able to reproduce that. Not sure why, but files up to 64 bytes show 0
utilization on NFS according to DU. I guess this can be fixed by writing a
bigger file.
> dfsadmin disk utilization report on Solaris is wrong
> ----------------------------------------------------
>
> Key: HADOOP-2845
> URL: https://issues.apache.org/jira/browse/HADOOP-2845
> Project: Hadoop Core
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.16.0
> Reporter: Martin Traverso
> Assignee: Martin Traverso
> Fix For: 0.17.0
>
> Attachments: HADOOP-2845-1.patch, HADOOP-2845.patch
>
>
> dfsadmin reports 2x disk utilization on some platforms (Solaris, MacOS). The
> reason for this is that org.apache.hadoop.fs.DU is relying on du's default
> block size when reporting sizes and assuming they are 1024 byte blocks. This
> works fine on Linux, but du Solaris and MacOS uses 512-byte blocks to report
> disk usage.
> DU should use "du -sk" instead of "du -s" to force the command to report
> sizes based on 1024 byte blocks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
