原帖由 netwinxp 于 2009-4-8 21:09 发表
因为NTFS会每次和每隔一段时间就会写入$LOG文件(属于NTFS内部使用的),而U盘最忌讳的在同一个地方多次写入。NTFS和U盘的原理就决定了U盘使用NTFS将大大缩短寿命(具体你可以看NTFS资料和U盘原理,所谓的U盘写入次 ...
原帖由 victor888 于 2009-4-9 08:04 发表
请问netwinxp版主,畸形目录NTFS也要写LOG吗?
另外,请你给出微软有关U盘不适宜使用NTFS系统的原文,网上已有的都不是微软搞的。而且,国外也有人用NTFS格式,并没有说不好。
NTFS Change Journal
As files, folders, and other NTFS objects are added, deleted, and modified, NTFS enters change journal records in streams, one for each volume on the computer.
The total size of all the records currently in the journal varies, but there is a configurable maximum size. The change journal can exceed the maximum size until the size reaches an outer threshold, at which point a portion of the oldest records are deleted until the change journal is restored to its maximum size. The maximum size of the change journal is configurable but cannot be reduced, only increased.
The change journal conveys significant scalability benefits to applications that might otherwise need to scan an entire volume for changes. File system indexing, replication managers, virus scanners, and incremental backup applications can benefit from using the change journal.
The change journal is much more efficient than time stamps or file notifications for determining changes in a particular namespace. Applications that must rescan an entire volume to determine changes can now scan once and subsequently refer to the change journal. The I/O cost depends on how many files have changed, not on how many files exist on the volume.
The APIs are fully documented and can be leveraged by independent software vendors (ISVs). Microsoft uses the change journal in Windows Server 2003 components such as the Indexing Service and File Replication Service. ISVs can use this feature to enhance the scalability and robustness of a range of products including backup, antivirus, and auditing tools.
原帖由 victor888 于 2009-9-21 10:36 发表
英文内容不过是对NTFS系统存储方式的一个说明,不是证明NTFS对U盘不利的证据。
到于您说的XP格式选项中没有NTFS格式一事,我在群里进行了求助,结果证实,在WIN7下,无论是128M的小U盘还是1G的大U盘,都有格 ...
FAT16:
Stick prepared for ~15 min. (899 secs.)
Text mode copy part with USB write-protection- 4:10
Text mode copy part without USB write-protection- 6:13
FAT32:
Stick prepared for ~21 min. (1253 secs.)
Text mode copy part with USB write-protection- 12:58
Text mode copy part without USB write-protection- 7:15
NTFS:
Stick prepared for ~4 min. (238 secs.)
Text mode copy part with USB write-protection- 1:42
Text mode copy part without USB write-protection- 1:45
It really puzzles me why FAT32 is so slow compared to FAT16![]()
If your system supports USB boot from NTFS formatted partitions AND you are not planning excessive usage of the USB stick in terms of write operations, where NTFS may wear it out (disputable with modern USB sticks), NTFS seems to be the way to go.
原帖由 victor888 于 2009-9-22 16:33 发表
哈哈哈哈哈哈,先让我大笑几声!
你给我的链接太好了,它正说明了NTFS的优点,很可惜,发这个文章的作者,他得出的结论是错误的!
现在,我用作者的原图来回复你!
看这张图:http://i.testfreaks.com ...
原帖由 victor888 于 2009-9-23 08:31 发表
好了,感谢你这么仔细的回复。
我上网也查了一下IOPS,找到的内容几乎全是衡量服务器硬盘的指标,我又搜索了一下这个sissoft remoeable disk bench,确实用来测U盘了。我现在的问题是这个软件对于非磁性介质 ...
原帖由 likehanlei 于 2009-9-23 14:30 发表
看到这里,我发现我是来关注NTFS和FAT32的了,我的移动硬盘全是ntfs,并且从不拔下,如果真的是有损的话····我好像一直在折磨它,晕,持续关注··
暂时还是拔下来吧,为了健康着想··
●由于采用可靠的CMOS移动门技术,使得芯片最大可实现100kB编程/擦除循环,该技术可以保证数据保存10年而不丢失。
原帖由 wuwuzz 于 2009-9-24 20:38 发表
一、第1个降速点是不是与“簇、闪存块对齐”有关? SK6211量产工具里
并没有“明显”定义闪存块大小的地方,难道这个分驱比例就“隐含”
着闪存块与簇对齐? 最佳比例恰好蒙对、导致两者对齐了?
二、fbinst有--align对齐选项,可有时并无提速效果,仍然是W9- R18+,
该如何解释呢?
原帖由 victor888 于 2009-9-24 20:24 发表
我们来算笔帐,就算1万次,我们每天在这个区块写一次,那么,这个区块可用10000/365=27.4年,就算写5次,那么还可以用6年多,试问,我们可能用U盘这么长时间吗?就算出现了坏块,用量产工具格式化一次就可以了。
欢迎光临 无忧启动论坛 (http://wuyou.net/) | Powered by Discuz! X3.3 |