Celerra(七)---Dedup:file-level or block-level??

简介:

  之前的一篇文章《netapp学习(十二)---Dedup:file-level or block-level??》中证明了DataOntap8.0只是file-level级别的dedup,而并不是block级别的。本篇使用EMC的Celerra做实验,验证其到底是什么级别的dedup。file-level?block-level?byte-level?

1、查看nfs这个文件系统此时是没有开启dedup的

[root@VNX bin]# ./nas_fs -info nfs

id = 11

name = cifs_fs

acl = 0

in_use = True

type = uxfs

worm = off

volume = v114

pool = clar_r5_performance

member_of = root_avm_fs_group_3

rw_servers= server_2

ro_servers=

rw_vdms =

ro_vdms =

auto_ext = hwm=90%,max_size=18000M (reached),thin=yes

deduplication = Off

2、并没有任何文件,此时已占用608K

clip_image002

3、

将如下图的1.exe和2.exe传上去

clip_image004

开启dedup之前是8736KB

clip_image006

4、开启dedup

[root@localhost bin]# ./nas_fs -info fs_3

id = 26

name = fs_3

acl = 0

in_use = True

type = uxfs

worm = off

volume = v106

pool = clar_r5_performance

member_of = root_avm_fs_group_3

rw_servers= server_2

ro_servers=

rw_vdms =

ro_vdms =

auto_ext = hwm=90%,max_size=3000M,virtual_provision=no

 

deduplication = On

 

5、[root@localhost bin]# ./fs_dedupe -modify nfs -state on

Done

6、可以看到容量变成6880K,比之前的8736KB少了近2000K。

clip_image004[4]

上面的实验已经证明了Celerra确实是file-level级别的dedup,那么会不会是块级别或者是字节级别的dedup呢?因此笔者做了如下实验,和DataOntap8.0的实验一样。

1、此时nfs这个文件系统下没有任何文件

clip_image002[6]

2、将下图2个ppt传上去

clip_image004[6]

3、可以看到容量增加到4448KB

clip_image006[4]

4、开启dedup后

[root@localhost bin]# ./fs_dedupe -modify fs_3 -state on

Done

5、观察容量变化从4448变成3936减少了512K,如果Celerra是block级别的,那么此时容量就应该减少,反之,容量则不会有任何变化。通过实验证明,Celerra容量确实减少了,则证明是block级别的。【注意--但是EMC的官方文档说Celerra也是文件级别的重复数据删除,请高手指点!】

clip_image008

 

  通过《netapp学习(十二)---Dedup:file-level or block-level??》和本篇的实验对比,读者不难发现DataOntap8.0仅仅是file-level的,而Celerra不仅支持file-level,而且支持block-level【同上注意】。但是同样是file-level级别的dedup,为什么DataOntap8.0由105M减少到102M,减少了3M;而Celerra仅由8736KB减少到6880K,减少2M。都是1.exe和2.exe完全一样的文件。由此可见Celerra的重复删除比没有DataOntap8.0

 





本文转自 taojin1240 51CTO博客,原文链接:http://blog.51cto.com/taotao1240/699325,如需转载请自行联系原作者

目录
相关文章
|
2月前
|
Docker 容器
ADD failed: file not found in build context or excluded by .dockerignore: stat irap_rule_center: fil
ADD failed: file not found in build context or excluded by .dockerignore: stat irap_rule_center: fil
|
5月前
|
物联网
zigbee配置及常见错误总结---(Segment BANKED_CODE must be defined in a segment definition option)
zigbee配置及常见错误总结---(Segment BANKED_CODE must be defined in a segment definition option)
|
11月前
|
JavaScript
Uncaught runtime errors: × ERROR Avoided redundant navigation to current location: “/xxx“.
Uncaught runtime errors: × ERROR Avoided redundant navigation to current location: “/xxx“.
173 0
【问题】Log writing failed, No space left on device @ io_write - /mnt/project/log/development.log
【问题】Log writing failed, No space left on device @ io_write - /mnt/project/log/development.log
180 0
【问题】Log writing failed, No space left on device @ io_write - /mnt/project/log/development.log
The Soft Link between IM Level Storage Location and WM level Storage Type?(1)
The Soft Link between IM Level Storage Location and WM level Storage Type?(1)
The Soft Link between IM Level Storage Location and WM level Storage Type?(1)
The Soft Link between IM Level Storage Location and WM level Storage Type?(2)
The Soft Link between IM Level Storage Location and WM level Storage Type?(2)
The Soft Link between IM Level Storage Location and WM level Storage Type?(2)
PAT (Advanced Level) Practice - 1111 Online Map(30 分)
PAT (Advanced Level) Practice - 1111 Online Map(30 分)
115 0
|
Web App开发 Java
错误:Reference file contains errors http://www.ibm.com/webservices/xsd/j2ee_web_services_client_1_1.xsdv......
引用:http://topic.csdn.net/u/20070125/18/8d676afd-868a-4c2d-9a1b-07eed6b5683d.html   6楼 xsi:schemaLocation= "http://java.
1544 0