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 16EC2138350 for ; Sun, 5 Apr 2020 18:37:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4D3A9E0BFE; Sun, 5 Apr 2020 18:37:09 +0000 (UTC) Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (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 C572CE0B43 for ; Sun, 5 Apr 2020 18:37:08 +0000 (UTC) Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id E921A2400FB for ; Sun, 5 Apr 2020 20:37:05 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1586111825; bh=XO9MtoAg8vJ7dqY9SwCo1UvrEmpZEwRgVia1CTIgNBI=; h=Date:From:To:Subject:From; b=M0S976xE5sQ6JzJKET0TunOaybfo7XuL8gWLsB7ifrMY137uS6emosPTYbEWlsxKq X30bBIn0FHU3E7Lyw0p/GQlit4CA/fHcVQYlClqGdEGZXJJsLiFz2My82RALtivZ9F MbPmimJID2pEyu4UW+oi1EisBgnKkj/fW+cPQTpvMxNbRNibChVHga/hqICzhWUlfx 59zFClgNVrgHy05dJu/aQf0kE60I9UNoKqo1Vd+tafZlAcLAjYehRezumVe67LZKT+ rT0MBEw+ArIMUpUeusXnHpldHkFUAVw/htc8fFujhC+grxM9YUtgfPkJlPQPqR2dSG Py0QlrbiNGgmA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 48wMpT1BWdz9rxb for ; Sun, 5 Apr 2020 20:37:04 +0200 (CEST) Date: Sun, 5 Apr 2020 20:37:04 +0200 From: tuxic@posteo.de To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Copying root to SSD in one go...a good idea...or? Message-ID: <20200405183704.djcsxqtnrn2equd5@solfire> Mail-Followup-To: gentoo-user@lists.gentoo.org References: <20200405171245.w7l2oyp63rt5i2qw@solfire> <20200405175425.fuytrt5nphj2335f@solfire> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Archives-Salt: 079a7d89-b6d6-461f-995d-ed87ab87778b X-Archives-Hash: e7782d78e69394552032910bb7ad093e On 04/05 11:12, Mark Knecht wrote: > 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 ...I just wanted to check, whether there is water in the pool... :) I minute ago I found this: https://unix.stackexchange.com/questions/203018/interrupting-rsync-with-ctrl-c-should-i-use-partial-or-append which rises a question about how to resume an interrypted rsync-session. It looks like the final answer was not found... Any additional ideas about that? Cheers! Meino