On 09/27/2015 12:10 PM, Xen wrote:
On Sun, 27 Sep 2015, Anton Aylward wrote:
On 09/27/2015 03:53 AM, Linda Walsh wrote:
--- ??? You lost me on this one. W/a backup, you usually concatenate all of the files -- so it doesn't matter if the block size of the source is 512b or 4k, the only thing backed up is actual size of the data (or less if you still use compression). So the really, wouldn't matter if you went to a 1MB block size WRT backups, as the backups only store the original data -- not the 'slack'.
Linda, you've made a generalization that isn't valid.
Not everyone uses the same backup strategy.
That doesn't mean every backup strategy is just as sound.
It doesn't need to be. I have a one line backup any one of my less and 5G partitions to 'the cloud' using rsync. That got a few bells and whistles added so it has some defaults and looks at environment variables. Its 'sound' as long as *I* am using it, but is a piece of scrap to anyone else. personal 'oneliners' are like that.
And most of it revolves around not needing high-level or sophisticated tools.
Indeed.
See, in Linux it is often easier to build a weak system on existing tools that seem to do the job, than it is to really build something good but that would require more development.
No "seems" about it. A lot of the time you don't need something sophisticated. And when you do, you can evolve it. That's how many of the more 'complex' applications came about. "A minimis incipe"
This tendency to reuse what exist and to end up with a solution with the minimal amount of effort is what produces such bad designs all the time. It is not designed based on beauty, but just on economy.
Strike "bad" from that. "Adequate" and "sufficient unto the job at hand" is very far from "bad". Each day has its own problems. If a minimalist solution, a quick-and-dirty does the job, you can get on with the real issues, the real pressing problems. Which are more likely to be people problems than technical problems.
Does that mean those sparse files are 'registered' on disk as being, like, huge, while their actual space requirement is very slim, but if you were to put it in a tar file it would suddenly take up all that "real space"?.
In short, yes; in reality it depends on the version of tar/cpio you use. RTFM. Also note that cpio can, like rsync, punt the output over the net to another machine :-)
It is very easy and fast to write such a thing, which is why it is being done. But that doesn't mean it is sound or well thought out. It is just fast to code.
You're not paying attention. It may be sound and well thought out *FOR* *MY* *PERSONAL* USE*. It's just not packaged and generalized for the world at large. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org