public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
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 19:22:43 +0100	[thread overview]
Message-ID: <4576983.31r3eYUQgx@dell_xps> (raw)
In-Reply-To: <20200405175425.fuytrt5nphj2335f@solfire>

[-- Attachment #1: Type: text/plain, Size: 3133 bytes --]

On Sunday, 5 April 2020 18:54:25 BST tuxic@posteo.de wrote:
> On 04/05 10:33, Mark Knecht wrote:
> > On Sun, Apr 5, 2020 at 10:13 AM <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
> > 
> > Just my 2 cents...
> > 
> > If the SSD cannot survive having data copied to it there's something
> > seriously wrong with the drive. I don't think you should be overly worried
> > about this but I do understand it's new technology so you want to be
> > careful. Bravo for that.
> > 
> > Possibly to ease your concerns a little bit use smartctl -a /dev/SSD and
> > get to know your drive that way. You can most likely watch the drive temp
> > as recorded by the drive.
> > 
> > Best wishes,
> > Mark
> 
> Hi Mark,
> 
> Yes, if a SSD could not survive writes, something is wrong with the
> SSD. But that was not my point.
> Copying about 100GB (roughly guessed) data in one go to the SSD is a
> use case, which is not common. And therefore possibly not taken into
> account by the company, which create that SSD.
> SSDs can create noticeable heat (mine has a minimalistic heat
> spreader therefore. Faster SSDs come with a substancial heatspreader).
> 
> Smartctl will report problems when they are already there.
> I want to prevent problems beforehand.
> 
> So -- does copying about 100 GB creates so much heat in the sillicone
> of the SSD, that it ages more than preferred?
> 
> And if so, how can I prevent it by appluing other techniques to copy
> the data?
> See additional questions in my initial posting for that.

With rsync you could add the option:

--bwlimit=RATE          limit socket I/O bandwidth

and select a low enough bandwidth limit to keep the packets flowing at a low 
rate to remain cool enough for your liking.  

However, I'll echo what other have said about not worrying about these things.  
The OEMs must run some rudimentary tests to establish performance envelopes 
and keep everything tuned just so.

Nevertheless, if you do not trust them to produce the best quality products, 
then we share something in common!  LOL!

In this case, you may want to open the PC case and use a desktop fan to keep 
the interior of the case even cooler than usual, during your copying process.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-04-05 18:23 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     ` Michael [this message]
2020-04-05 19:03       ` [gentoo-user] " tuxic
2020-04-05 19:31         ` Neil Bothwick
2020-04-05 18:41 ` J. Roeleveld
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=4576983.31r3eYUQgx@dell_xps \
    --to=confabulate@kintzios.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