Live data from Hacker News

TFS: A file system built for performance, space efficiency, and scalability

github.com

11–20 of 126 posts

Re: TFS: A file system built for performance, space efficiency, and scalability

#11
post #4

"Team Foundation Server" (Microsoft's version control server) is what goes through my mind... poor choice of naming...

I read the TFS github landing page and it didn't explain what the 'T' stood for. I then noticed the author's name is "Ticki"[1]. Therefore, I can only guess that TFS stands for "Ticki's File System".

[1]http://ticki.github.io/about/

Re: TFS: A file system built for performance, space efficiency, and scalability

#12
>The system will never enter an inconsistent state (unless there is hardware failure), meaning that unexpected power-off won't ever damage the system.

What is the difference here between a hardware failure and a unexpected power failure?

Re: TFS: A file system built for performance, space efficiency, and scalability

#13

>The system will never enter an inconsistent state (unless there is hardware failure), meaning that unexpected power-off won't ever damage the system. What is the difference here between a hardware failure and a unexpected power failure?

Hardware failures could imply "flipped bits" (depending on failure mode) whereas loss of power should just mean "truncated bits".

Re: TFS: A file system built for performance, space efficiency, and scalability

#15

>The system will never enter an inconsistent state (unless there is hardware failure), meaning that unexpected power-off won't ever damage the system. What is the difference here between a hardware failure and a unexpected power failure?

And what about a kernel panic?

Re: TFS: A file system built for performance, space efficiency, and scalability

#16

>The system will never enter an inconsistent state (unless there is hardware failure), meaning that unexpected power-off won't ever damage the system. What is the difference here between a hardware failure and a unexpected power failure?

Yea, I'd like a little more detail on this point too.

Re: TFS: A file system built for performance, space efficiency, and scalability

#17
post #4

"Team Foundation Server" (Microsoft's version control server) is what goes through my mind... poor choice of naming...

So you have to add “fs” or “filesystem“ to your search queries, or not even that if the rest of the query gives sufficient context.

Everyone makes name conflicts in independent domains to be a much bigger problem than they are in reality.

There’s Amazon rainforest, Amazon the ecommerce website, and Amazon the cloud company. How often do you have any problem differentiating between them?

Re: TFS: A file system built for performance, space efficiency, and scalability

#19
post #4

"Team Foundation Server" (Microsoft's version control server) is what goes through my mind... poor choice of naming...

There is already a tfs file system for flash memory storage. It is prolific in feature phones and other embedded systems. Stands for tiny file system.

Re: TFS: A file system built for performance, space efficiency, and scalability

#20
Good luck. There is long road ahead.

Both ZFS and Btrfs were initially developed by really high caliber people and experts with good track record. ZFS had five years for full time development until release, next five years to get close to the features and stability that ZFS has now. Btrfs started 10 years ago and it's still trying to catch up.

Post reply on HN