search for: _somemagicstring_

...ak a large file into chunks and store them that way, then one can still make use of hard-links efficiently. For example, going back to a 10Gb Exchange Database file, its likely not going to change too much during use. So if the server stored the huge clumsy 'priv1.edb' as: .priv1.edb._somemagicstring_.1 .priv1.edb._somemagicstring_.2 etc... and intelligently only broke the 'hard-links' of the bits that actually change, then it all works well. One could have an option to enable this for files bigger than a certain size, and break them into specific sized chunks. One could quite rig...