public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Ten Harmsel <alec@alectenharmsel.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Safeguarding strategies against SSD data loss
Date: Mon, 27 Oct 2014 06:30:27 -0400	[thread overview]
Message-ID: <544E1EC3.6060401@alectenharmsel.com> (raw)
In-Reply-To: <201410270924.40381.michaelkintzios@gmail.com>


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



  reply	other threads:[~2014-10-27 10:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27  9:24 [gentoo-user] Safeguarding strategies against SSD data loss Mick
2014-10-27 10:30 ` Alec Ten Harmsel [this message]
2014-10-27 11:11 ` Alan McKinnon
2014-10-27 13:13   ` Rich Freeman
2014-10-27 15:15     ` [gentoo-user] " James
2014-10-27 15:23       ` Mick
2014-10-27 15:22     ` [gentoo-user] " Mick
2014-10-27 15:36       ` Rich Freeman
2014-10-27 16:52         ` Pandu Poluan
2014-10-27 17:26           ` Volker Armin Hemmann
2014-10-27 17:30           ` Rich Freeman
2014-10-28  0:41             ` Pandu Poluan
2014-10-28  1:13               ` Rich Freeman
2014-10-28  3:45           ` Tom H
2014-10-27 17:23         ` Volker Armin Hemmann
2014-10-27 17:37           ` Rich Freeman
2014-10-28  0:56             ` Pandu Poluan
2014-10-28  3:49             ` Tom H
2014-10-27 17:20       ` Volker Armin Hemmann
2014-10-27 17:17     ` Volker Armin Hemmann
2014-10-27 12:27 ` Philip Webb
2014-10-27 14:12   ` [gentoo-user] Safeguarding strategies against SSD data loss : PS Philip Webb
2014-10-27 15:16   ` [gentoo-user] Safeguarding strategies against SSD data loss Mick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=544E1EC3.6060401@alectenharmsel.com \
    --to=alec@alectenharmsel.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox