On Sun, 27 Sep 2015, 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'.
Exactly, but in the Unix world even backups are often just filesystem copies. Much programs use the filesystem as a database engine, and so they store like every email as a small file (think MailDir) instead of storing it as e.g. some mbox or whatever format. There are many backup scenarios that use e.g. rsync even using hard links to create incremental archives, but the archives are just complete filesystems being stored as duplicates on some other disk or volume. I tend to migrate always to real archives, but it is hard when so many people do the reverse.
Not if the storage was optimized to begin with by grouping -- with access as easy as access to a mountable file system (pointing to /cygwin's /proc/registry tree).
Word. I have felt like this a long time, because even the big game makers all do this. E.g. Blizzard has its own file system inside of their MPQ files since ages past. This was around 2000 that games like Starcraft and Diablo had this structure, and they still do. Many many files is a liability and it actually, believe it or not, cost me 3 months of email that I lost due to a backup solution (IMAPSize) using a MailDir format. A backup using small files is like spreading your belongings across a soccer field and then thinking they are safe. They proved not to be :(. I hate it, but there was no other (and still is not) backup solution at the time. There aren't many any IMAP backup tools. I guess I just have myself to blame for being stupid. The registry could be improved by making it more of a cascading system such that applications can be removed from the addition-set at will, but still, I agree that it functions quite well as opposed to many small files. However for configuration it is not really the same as for resources, because the amount of configuration files is rather limited on any Unix/Linux system. The registry is also almost impossible to maintain by hand (particularly, for instance, if you have suffered some malware infestation that you are trying to clear out). Let's hunt and kill something that an automated program created, but now you have to rid it by hand :(. Okay, stupid again.
Just saying -- that much of that space wasting was due to space-wasting design.
This should be in the Book of all Truths. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org