Question

求大神翻译下面的英文，不要机翻啊，谢谢

MCKUSICK There’s also this business where you essentially snapshot a chunk. Presumably, that’s something you use when you’re essentially replacing a replica, or whenever some chunkserver goes down and you need to replace some of its files.
QUINLAN Actually, two things are going on there. One, as you suggest, is the recovery mechanism, which definitely involves copying around replicas of the file. The way that works in GFS is that we basically revoke the lock so that the client can’t write it anymore, and this is part of that latency issue we were talking about.
There’s also a separate issue, which is to support the snapshot feature of GFS. GFS has the most general-purpose snapshot capability you can imagine. You could snapshot any directory somewhere, and then both copies would be entirely equivalent. They would share the unchanged data. You could change either one and you could further snapshot either one. So it was really more of a clone than what most people think of as a snapshot. It’s an interesting thing, but it makes for difficulties—especially as you try to build more distributed systems and you want potentially to snapshot larger chunks of the file tree.
I also think it’s interesting that the snapshot feature hasn’t been used more since it’s actually a very powerful feature. That is, from a file-system point of view, it really offers a pretty nice piece of functionality. But putting snapshots into file systems, as I’m sure you know, is a real pain.
MCKUSICK: I know. I’ve done it. It’s excruciating—especially in an overwriting file system.
QUINLAN Exactly. This is a case where we didn’t cheat, but from an implementation perspective, it’s hard to create true snapshots. Still, it seems that in this case, going the full deal was the right decision. Just the same, it’s an interesting contrast to some of the other decisions that were made early on in terms of the semantics.
FILE SYSTEMS
11
All in all, the report card on GFS nearly 10 years later seems positive. There have been problems and shortcomings, to be sure, but there’s surely no arguing with Google’s success and GFS has without a doubt played an important role in that. What’s more, its staying power has been nothing short of remarkable given that Google’s operations have scaled orders of magnitude beyond anything the system had been designed to handle, while the application mix Google currently supports is not one that anyone could have possibly imagined back in the late ‘90s.

Answer 1

McKusick的还有这项业务基本上快照一大块的地方。据推测，这东西你用你基本上是更换一个副本，或当一些块服务器停机时，你需要更换它的一些文件。
昆兰其实，有两件事情是怎么回事。一，按照你的建议，是恢复机制，这肯定涉及围绕该文件的副本复制。在政府飞行服务队的工作方式是，我们基本上撤销锁，以便客户端可以不写了，这是该延迟问题，我们正在谈论的一部分。
还有一个单独的问题，这是支持政府飞行服务队的快照功能。政府飞行服务队拥有的最通用的快照功能，你能想象。你可以快照任何目录的地方，然后两个副本将是完全等价的。他们将分享不变的数据。你可以改变任何一个，你可以进一步快照其一。因此，它是真正的克隆快照作为一个比大多数人认为的。这是一个有趣的事情，但它的困难，尤其是让您尝试建立更多的分布式系统，你可能想快照较大块的文件树。
我也觉得这是有趣的快照功能并没有被使用，因为它实际上是一个非常强大的功能。也就是说，从文件系统的视图点，它确实提供了一个功能相当不错的一块。但把文件系统的快照，因为我敢肯定你知道，是一个真正的痛苦。
McKusick的：我知道。我已经做到了。这是痛苦的，尤其是在一个覆盖文件系统。
昆兰没错。这是一个情况下，我们没有作弊，但是从实施的角度看，很难创造真正的快照。尽管如此，它似乎在这种情况下，要完整的交易是正确的决定。一样的，这是一个有趣的对比，早在语义方面作了一些其他决定。
文件系统
11
总而言之，政府飞行服务队的报告卡，近10年后似乎正。已有的问题和不足，可以肯定的，但肯定是有没有发挥重要作用的疑问有没有与谷歌的成功和政府飞行服务队的争论。更重要的是，其住权力已被无关的骄人给予，谷歌的业务已经超出任何系统已被设计来处理缩放量级，而混合谷歌目前支持的应用程序是不是1，任何人都可能想象在回90年代末