Quote:
Originally Posted by dnanian
Perhaps a difference in the spotlight indexes in the two drives, Marc (one's inside the TM archive, too)? Could also be that the compression was preserved in the source but not when copied.
|
I have always had Spotlight indexing disabled on the clones. I just checked the exclusion list again, and the TM copy is still listed as excluded. Then I did a
du on both the source and target Spotlight dirs:
Code:
root@jupiter
/Volumes/Amalthea $du /Volumes/Amalthea/.Spotlight-V100/
175648 /Volumes/Amalthea/.Spotlight-V100//Store-V1/Stores/BA8038CE-F979-4651-912B-3A0FEF836D6C
175648 /Volumes/Amalthea/.Spotlight-V100//Store-V1/Stores
175664 /Volumes/Amalthea/.Spotlight-V100//Store-V1
175664 /Volumes/Amalthea/.Spotlight-V100/
root@jupiter
/Volumes/Amalthea $du /Volumes/Himalia/.Spotlight-V100/
4102416 /Volumes/Himalia/.Spotlight-V100//Store-V1/Stores/38C02202-C9B6-4154-AAC9-B1A851A00BBE
4102416 /Volumes/Himalia/.Spotlight-V100//Store-V1/Stores
4102432 /Volumes/Himalia/.Spotlight-V100//Store-V1
4102432 /Volumes/Himalia/.Spotlight-V100/
So this does explain part of the 5.42 GB difference, but it's not the whole story.
So why would a copy result in expansion of compressed data?
-- Marc