"Team Foundation Server" (Microsoft's version control server) is what goes through my mind... poor choice of naming...
TFS: A file system built for performance, space efficiency, and scalability
11–20 of 126 posts
Re: TFS: A file system built for performance, space efficiency, and scalability
#12What 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?
Re: TFS: A file system built for performance, space efficiency, and scalability
#14>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
#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?
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?
Re: TFS: A file system built for performance, space efficiency, and scalability
#17"Team Foundation Server" (Microsoft's version control server) is what goes through my mind... poor choice of naming...
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
#18I do not buy the argument against AES. On both ARM and x86 you have side-channel secure hardware implementations of AES.
Re: TFS: A file system built for performance, space efficiency, and scalability
#19"Team Foundation Server" (Microsoft's version control server) is what goes through my mind... poor choice of naming...
Re: TFS: A file system built for performance, space efficiency, and scalability
#20Both 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.