|Flickr spam||Thursday 6th February 2014|
Digital photos tend to contain meta-data from your camera when you take the photo. You can add or remove information to this. One common thing to add is copyright information, which gives you a little protection from anonymous or orphaned work laws (i.e. unless somebody or something deliberately strips this information (Facebook) then nobody can claim it's free to use).|
This is a good idea if you're sharing your photos on sites such as Flickr. I've included an e-mail address in mine so I can be contacted if the photo crops up somewhere else in the future.
I wasn't that surprised then to see spam is now being sent to that address.
So - double edged sword. EXIF can protect your works, but don't expect it not to be abused at the same time.
|VMWare ESXi NFS thin clone||Saturday 1st February 2014|
I have just got a little confused - I ran a thin clone of a *.vmdk file on an ESXi host to a NFS share:|
vmkfstools -d thin mysource.vmdk /vmfs/volumes/nas/backup.vmdk
When I checked the NAS the file appeared to be thick as it took up all the space.
A bit more digging showed that whilst the file was being reported as the full provisioned size - when using the "du" command the actual space was that of the thin on ESXi.
Now I was aware you had to do that when running on the command line on ESXi - but not on the remote backup share. It turns out that my version of Linux and filesystem (btrfs) has native support for sparse files so reports their full size to "ls" but correctly doesn't use up the space on the device.
I'm not entirely sure if this is useful as most things related to disk space rely on the reported size and not actual block usage. For the purposes of backups, I'd prefer the compacted file.