Danny Macaskill: The Ridge – YouTube

Danny Macaskill: The Ridge – YouTube.

We Gave Up by Maheshwer Peri

Somewhere along our lives

We gave up
Happiness to be victorious
Satisfaction for success
Contentment for growth
Life for a career

We gave up
Beauty to look sexy
Natural to look artificial
Health to junk
Fitness to fashion

We gave up
Letter to spirit
Correctness to fairness
Justice to Law
Courage to practicality

We gave up
Us to I
We to me
Heart to head
Smiles to frowns

We gave up
Modesty to money
Humility to pride
Nobility to showoff
Wisdom to intelligence

We gave up
Friends to prospects
Blood to money
Self to others
God to devil.

We gave up
Everything
We should have been.

Maheshwar Peri

Rebloged: Mobile Is Eating the World | Andreessen Horowitz

Mobile Is Eating the World | Andreessen Horowitz.

Reblogged: Brackets Blog – The Free, Open Source Code Editor for the Web

It’s been a lot of fun to work with all of you and see the Brackets project grow. The entire team is humbled by how many of you are using it and the time you take to contribute code, file issues, and write extensions. It’s a pleasure to be a part of the Brackets community and we’re all looking forward to continuing to work with you to grow and evolve Brackets.

via Brackets Blog – The Free, Open Source Code Editor for the Web.

Reblogging: My experience with using cp to copy a lot of files 432 millions, 39 TB

One morning I was notified that a disk had failed. No big deal, this happens
now and then. I called Dell and next day I had a replacement disk. While
rebuilding, the replacement disk failed, and in the meantime another disk had
also failed. Now Dell’s support wisely suggested that I did not just replace
the failed disks as the array may have been punctured. Apparently, and as I
understand it, disks are only reported as failed when they have sufficiently
many bad blocks, and if you’re unlucky you can lose data if 3 corresponding
blocks on different disks become bad within a short time, so that the RAID
controller does not have a chance to detect the failures, recalculate the data
from the parity, and store it somewhere else. So even though only two drives
flashed red, data might have been lost.

Having almost used up the capacity we decided to order another storage
enclosure, copy the files from the old one to the new one, and then get the old
one into a trustworthy state and use it to extend the total capacity. Normally
I’d have copied/moved the files at block-level (eg. using dd or pvmove), but
suspecting bad blocks, I went for a file-level copy because then I’d know which
files contained the bad blocks. I browsed the net for other peoples’ experience
with copying many files and quickly decided that cp would do the job nicely.
Knowing that preserving the hardlinks would require bookkeeping of which files
have already been copied I also ordered 8 GB more RAM for the server and
configured more swap space.

When the new hardware had arrived I started the copying, and at first it
proceeded nicely at around 300-400 MB/s as measured with iotop. After a while
the speed decreased considerably, because most of the time was spent creating
hardlinks, and it takes time to ensure that the filesystem is always in a
consistent state. We use XFS, and we were probably suffering for not disabling
write barriers which can be done when the RAID controller has a write cache
with a trustworthy battery backup. As expected, the memory usage of the cp
command increased steadily and was soon in the gigabytes.

For more visit: My experience with using cp to copy a lot of files 432 millions, 39 TB.