public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Copying root to SSD in one go...a good idea...or?
Date: Sun, 05 Apr 2020 20:41:58 +0200	[thread overview]
Message-ID: <E4DC1EBA-61C3-46F7-8950-3615DE11516B@antarean.org> (raw)
In-Reply-To: <20200405171245.w7l2oyp63rt5i2qw@solfire>

On 5 April 2020 19:12:45 CEST, tuxic@posteo.de wrote:
>Hi,
>
>currentlu I am preparing a new Gentoo Linux by compiling all
>the application I had on my old system.
>
>Due to delivery problems (corona) my SSD was delivered today
>(or yesterday...it depends...;) .
>
>When the whole compilation has finished and the system boots it
>needs to be transfered to the SSD.
>
>The SSD has a heat spreader...so it gets hot, when used.
>
>Is it wise to copy the whole root system to the SSD in one go
>in respect to a not so healthy heat increase?
>
>And if not...how can I copy the root system in portions
>to the SSD and do not miss anything?
>
>Are there SDD-friendly and SSD-unfriendlu methods of copying
>greater chunks of data to a SSD (rsync, tar-pipe, cp....)?
>What is recommended here?
>
>Thanks a lot for any help for a SSD newbie in advance!
>
>Cheers! And stay heathy!
>Meino

I have been using SSDs for over 7 years now and never worried about them overheating.
In my opinion, if the drive can't handle a copy operation of 20GB (how much bigger is your root partition?) it should be replaced from day one.

I only keep the portage compile dir and browser caches in RAM, the rest stays on the SSD. And as I mentioned in a previous thread about SSDs, I only had one failure after 6.5 years. (That drive also had SWAP on it and I didn't offload the browser caches yet on that one).

Like Mark said, it is good to keep an eye on it, but if you use decent brand SSDs (Samsung and Intel), you should be able to expect 5+ years of heavy usage.

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.


  parent reply	other threads:[~2020-04-05 18:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-05 17:12 [gentoo-user] Copying root to SSD in one go...a good idea...or? tuxic
2020-04-05 17:33 ` Mark Knecht
2020-04-05 17:54   ` tuxic
2020-04-05 18:08     ` Dale
2020-04-05 18:29       ` Neil Bothwick
2020-04-05 19:09         ` Dale
2020-04-05 19:28           ` Neil Bothwick
2020-04-05 19:43             ` Dale
2020-04-05 18:39       ` tuxic
2020-04-05 19:19         ` Dale
2020-04-05 18:12     ` Mark Knecht
2020-04-05 18:37       ` tuxic
2020-04-05 19:25         ` Dale
2020-04-05 19:29         ` Neil Bothwick
2020-04-05 20:05       ` [gentoo-user] " Grant Edwards
2020-04-05 18:22     ` [gentoo-user] " Michael
2020-04-05 19:03       ` tuxic
2020-04-05 19:31         ` Neil Bothwick
2020-04-05 18:41 ` J. Roeleveld [this message]
2020-04-05 20:12   ` tuxic
2020-04-06  6:06 ` William Kenworthy
2020-04-06 13:35   ` [gentoo-user] " Grant Edwards
2020-04-06 14:19     ` Jack
2020-04-06 14:34       ` Grant Edwards

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=E4DC1EBA-61C3-46F7-8950-3615DE11516B@antarean.org \
    --to=joost@antarean.org \
    --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