From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 69A83138350 for ; Sun, 5 Apr 2020 18:12:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 111F2E0B34; Sun, 5 Apr 2020 18:12:17 +0000 (UTC) Received: from mail-qv1-xf41.google.com (mail-qv1-xf41.google.com [IPv6:2607:f8b0:4864:20::f41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B2557E0A65 for ; Sun, 5 Apr 2020 18:12:16 +0000 (UTC) Received: by mail-qv1-xf41.google.com with SMTP id v38so6373291qvf.6 for ; Sun, 05 Apr 2020 11:12:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=o+7Fru1QuiuL9G/64qtwlRwnPt8Hr/Qpi9X/TJ9HfzQ=; b=bNo9EGv05qtDcSI7+P6Y+njIhH+oNCd9ePpn4pqAGZSIFl9Kz6Fr6vrfRqIHr1jmlQ kzbIKZw/LOiQxvA8rUtI969y1ur7AYl4T6WZQL/qbZT/vhsOkH8EbDy4ZVqcRkxTAez7 70YRweM4qC53qoAGDJqw/nbTon7L1bj4X4NNEX9Kl2pEhnDo0BHR0kzUhqA0jHrJBCHc KXhdUYZNYMe7OLOg2Q2ubRo07JU8jZ3DCJ1Da5Q0tsZfUxcBkmsF7RD8TUWmxye5kr6c iS7jebl+abWtDqW4WpNmxvXYgencfHxeYIihzllNiCuZp5tzRDxr+a63XN8ezhVqR7Eo romQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=o+7Fru1QuiuL9G/64qtwlRwnPt8Hr/Qpi9X/TJ9HfzQ=; b=OXgZyt0vdyZy+BD+//MZBJboffaNAWb/UQrRk6taqcbPRcrmTdli/GtsCrzqv4ZVYF 5A2qDL3VQpN8mkMVSVOrXvZuGHDaslD8hDfNGnk4RLfzJ1oGo+5JNcuCuq7P7eETrmOK +B1oFATsaA/Xmch8ntziyKNfZq9wTolQfbQ3VJO9NfwFg/adBNON4O9FbWCw1H5mLZ/M shlmgJkmkKodzZrt4XYHdNThdIgsHaHkoi6yXSxSqR7mtbP881BWRqeXKhy0uxvXzp3u 9IeICvApgVw9ZV8baRPwoe3QL37h/pPwXHzwhcxKb1y/cnGCF3nVCS8A/3TfHr8yQ+AM UJYQ== X-Gm-Message-State: AGi0Pub7Bd5r++3OT7iD4+LPOpvrudW58ndhEYl1KUKcY98SxQA+df0m EPjiCgOlFcXkq5OQC9HBoAje4tHppsr5PxbY2zguJw== X-Google-Smtp-Source: APiQypInPT8NR++yzH5oQC4hPh0jBmZdLVy/u9mfHPlPKiLX/2rtbuYIx0rt2dieoVZLhJ0Z7y0dUqm7M/CalGki5hs= X-Received: by 2002:a0c:e610:: with SMTP id z16mr17880007qvm.49.1586110335723; Sun, 05 Apr 2020 11:12:15 -0700 (PDT) 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <20200405171245.w7l2oyp63rt5i2qw@solfire> <20200405175425.fuytrt5nphj2335f@solfire> In-Reply-To: <20200405175425.fuytrt5nphj2335f@solfire> From: Mark Knecht Date: Sun, 5 Apr 2020 11:12:04 -0700 Message-ID: Subject: Re: [gentoo-user] Copying root to SSD in one go...a good idea...or? To: Gentoo User Content-Type: multipart/alternative; boundary="00000000000022ae2c05a28f1741" X-Archives-Salt: c20e44d9-3684-4c7f-92e3-e2ead5bbcfe7 X-Archives-Hash: 30f998f86ebb0e355a6394d5cc69573b --00000000000022ae2c05a28f1741 Content-Type: text/plain; charset="UTF-8" On Sun, Apr 5, 2020 at 10:54 AM wrote: > > On 04/05 10:33, Mark Knecht wrote: > > On Sun, Apr 5, 2020 at 10:13 AM 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. > > Thanks a lot for any helpful advice in advance! > Cheers! > Meino > If copying 100GB causes too much heat watching smartctl will show you before it gets too hot and you can stop it. 100GB of data as a copy is only 1 write cycle to any given data block on the drive. It's not going to matter how you get it there but something like rsync _might_ allow a restart in the middle of the copy if your rsync operation was to fail part way through. I don't personally think there's anything at all for you to worry about with this but I can see it's not my words that will get you there. I will only offer that I've used SSDs for 5-6 years now and only had the first one I purchased fail. I ran Gentoo with nightly code compiles for about 2 years before moving away from Gentoo and never had a problem with any of that. I think you're just going to have to hold your nose and jump in the pool. We welcome you. The water is fine! Mark --00000000000022ae2c05a28f1741 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, Apr 5, 2020 at 10:54 AM <tuxic@posteo.de> wrote:
>
> On 04/0= 5 10:33, Mark Knecht wrote:
> > On Sun, Apr 5, 2020 at 10:13 AM &l= t;tuxic@posteo.de> wrote:
>= > >
> > > Hi,
> > >
> > > curren= tlu I am preparing a new Gentoo Linux by compiling all
> > > th= e application I had on my old system.
> > >
> > > D= ue to delivery problems (corona) my SSD was delivered today
> > &g= t; (or yesterday...it depends...;) .
> > >
> > > Wh= en 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 o= ne go
> > > in respect to a not so healthy heat increase?
&g= t; > >
> > > 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 metho= ds of copying
> > > greater chunks of data to a SSD (rsync, tar= -pipe, cp....)?
> > > What is recommended here?
> > &g= t;
> > > 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&#= 39;t think you should be overly worried
> > about this but I do un= derstand it's new technology so you want to be
> > careful. Br= avo for that.
> >
> > Possibly to ease your concerns a li= ttle bit use smartctl -a /dev/SSD and
> > get to know your drive t= hat way. You can most likely watch the drive temp
> > as recorded = by the drive.
> >
> > Best wishes,
> > Mark
&= gt;
> Hi Mark,
>
> Yes, if a SSD could not survive writes= , something is wrong with the
> SSD. But that was not my point.
&g= t; 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 crea= te noticeable heat (mine has a minimalistic heat
> spreader therefore= . Faster SSDs come with a substancial heatspreader).
>
> Smartc= tl will report problems when they are already there.
> I want to prev= ent problems beforehand.
>
> So -- does copying about 100 GB cr= eates so much heat in the sillicone
> of the SSD, that it ages more t= han 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.
>
> Thanks a lot for any helpf= ul advice in advance!
> Cheers!
> Meino
>

If copying 100GB causes too much heat watching smartctl will show y= ou before it gets too hot and you can stop it.

100= GB of data as a copy is only 1 write cycle to any given data block on the d= rive. It's not going to matter how you get it there but something like = rsync _might_ allow a restart in the middle of the copy if your rsync opera= tion was to fail part way through.

I don't per= sonally think there's anything at all for you to worry about with this = but I can see it's not my words that will get you there. I will only of= fer that I've used SSDs for 5-6 years now and only had the first one I = purchased fail. I ran Gentoo with nightly code compiles for about 2 years b= efore moving away from Gentoo and never had a problem with any of that.=C2= =A0

I think you're just going to have to hold = your nose and jump in the pool. We welcome you. The water is fine!

Mark
--00000000000022ae2c05a28f1741--