From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 9489C13893E for ; Mon, 27 Oct 2014 10:30:36 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 34A7EE094E; Mon, 27 Oct 2014 10:30:30 +0000 (UTC) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 225DEE0936 for ; Mon, 27 Oct 2014 10:30:28 +0000 (UTC) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 998AC20B05 for ; Mon, 27 Oct 2014 06:30:28 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Mon, 27 Oct 2014 06:30:28 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:message-id:date:from :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=MTfadfAYYMS0/sp8yBP2dK vCRpE=; b=j3j//mjyn5a+CeJ5k4HZ8H6gk7/EhF+XJ61sOeI3sxh+WmhVlz1/0A 0JlsPZIhdj+aPjoL59R2/KmC1UClhWqPFrkpvKD0t0/H3QYqcosvdwQWjttJr143 j5FIT0pQxyOkskVXoLmoAnC977s9LbnhzK5R3aCWSLsOkpZYrwJCs= X-Sasl-enc: zn8C2gZh8NqLKtodOCIfLrHlP1h/zyrHCRhbhnKDeg+y 1414405828 Received: from [192.168.1.15] (unknown [73.2.142.203]) by mail.messagingengine.com (Postfix) with ESMTPA id 59CA3C00013 for ; Mon, 27 Oct 2014 06:30:28 -0400 (EDT) Message-ID: <544E1EC3.6060401@alectenharmsel.com> Date: Mon, 27 Oct 2014 06:30:27 -0400 From: Alec Ten Harmsel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Safeguarding strategies against SSD data loss References: <201410270924.40381.michaelkintzios@gmail.com> In-Reply-To: <201410270924.40381.michaelkintzios@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 4aabc97c-eb63-4e09-8e58-80dff430506f X-Archives-Hash: b3d2d11e0cde0f5a1c5f7701511557b8 On 10/27/2014 05:24 AM, Mick wrote: > I'm starting a new thread so as to not hijack the one about alternative > kernels, but continue with something Volker raised. > > On Sunday 26 Oct 2014 23:25:50 Volker Armin Hemmann wrote: > >> as others have written already: ssd. >> >> With a caveat: if an ssd dies, it will die suddenly. Without a warning. >> Usually 5 minutes before the start of your weekly or monthly backup run. >> And that is first hand experience. > I haven't yet started using SSD and have wondered what sort of a system should > I set up to guard against such instantaneous catastrophic failures. I am > interested to hear what strategies people deploy to avoid data loss with SSDs, > especially on laptops that don't have the luxury of raid redundancy. All the data I have on my laptop is either: * Version Controlled * Rsync'd from a server * Not important My laptop doesn't have an SSD, but it's old and probably about ready to die in general. All of my documents are version controlled - git - and therefore "automatically" backed up. I rsync other files around, like my music and some software, so that's all backed up as well. > > With spinning drives I use tar and rsync at regular intervals. There have > been a few rare cases where a drive failed without prior notice - the last one > after a reboot. In such cases I am prepared to live with the risk of some > data loss, on machines where raid is not an option. > afaik tar and rsync should continue to work for SSDs. The more places the data is in, the better. If you regularly rsync text (say /etc), I would consider version control. Alec