From owner-freebsd-stable@freebsd.org Tue Feb 25 23:19:05 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9CE44243B93 for ; Tue, 25 Feb 2020 23:19:05 +0000 (UTC) (envelope-from mario.olofo@gmail.com) Received: from mail-qk1-x743.google.com (mail-qk1-x743.google.com [IPv6:2607:f8b0:4864:20::743]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48RvyJ3Vklz3K9X for ; Tue, 25 Feb 2020 23:19:04 +0000 (UTC) (envelope-from mario.olofo@gmail.com) Received: by mail-qk1-x743.google.com with SMTP id o28so888907qkj.9 for ; Tue, 25 Feb 2020 15:19:04 -0800 (PST) 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 :cc; bh=4Uc5kl011rDVm2Vcu5/Z60nCPZZSlu1QCRhi+X2/kas=; b=X1jQzbBCY0G7IVq8/ARh93agBmSZe+xB9UTvztrbfcDEhnhknjK7Pxtf+KaFyoGeWv m42SaL6fW8OxD9Uf3CoJrikDfYvj7I91+fDGovxOn2aW7lchvlR1r4r+s28LK1GTs8Lb 9mzMwjIMoes0/WMgcEP3m7gZvVjWf276FmgtlargFt7vGVXIMIOJvEFWhhbAb0AIQon+ f/QKrzPbFoV6WTCBDHyZJg+0+MyoDVR4bGMEO4XVdsKlZiLK0vNoGtrvYCr2jEvfbqXN qTFa3V7Q/UIfiq9Dt28NtsaXwh2qD1NpwvtTCh/tkU9WiF/Ku32r/8FGhoV39hGxRmRG hMYg== 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:cc; bh=4Uc5kl011rDVm2Vcu5/Z60nCPZZSlu1QCRhi+X2/kas=; b=JdykT9gR+zRciac9udfTehc1cDyNYDOBUgZMvp+AwkRTJMf8ll+khCKzTchtAO5EeG J8Jnr64hPzcYHJjseB1ld06ANwGuX1KO77sgVyFsNGFqsYKt0Yy0nJPi0mbIZ3nVAIW8 ZgL0qh0wboXNE43GqUibV/A0OFfTNoMlA6zLJIZM/ETnZYtlsYf6qFzNGVSchZhH0xzk ioeq+XKI/B2rWr+nrAlg3+QYYP/9h05isotpTo7uwtdrqrXz0hIpPSPUrFSeK2BEw+Lr 1nD3hDBcOJDZpTDFcFx1r9U/sDOlOQ7WvBOZblQJ21WyODvvXzmPD8J+XgbUASSAZclq GpGA== X-Gm-Message-State: APjAAAXntljVKN8QTRbyZ+5MFqm4KseP8zeCFLv2mTHDPPEmTk11WnhS U3KpjUdvNtNuh5X09c0jpiNvpDLPlIyd3ow44MxRyBq2Dho= X-Google-Smtp-Source: APXvYqzAUWZNoD29c+H4srlu0hJNH052NZuwRPc37r7Odk35yBDQDkJwuS2uBDugfpvc86kzdrp/oG5OJKjizt6f8MQ= X-Received: by 2002:a37:610d:: with SMTP id v13mr1621751qkb.484.1582672742983; Tue, 25 Feb 2020 15:19:02 -0800 (PST) MIME-Version: 1.0 References: <202002250115.01P1F9KX090465@mail.karels.net> <188F34DA-192C-4D44-96B5-18A7DAE8EC67@digsys.bg> <6028c786-8610-01d9-818e-6f69a2fe9645@ingresso.co.uk> <20200225145346.GA42880@phouka1.phouka.net> <6e329bb8-b96e-fa16-cc73-426685593943@denninger.net> In-Reply-To: From: Mario Olofo Date: Tue, 25 Feb 2020 20:18:51 -0300 Message-ID: Subject: Re: Running FreeBSD on M.2 SSD To: Karl Denninger Cc: freebsd-stable@freebsd.org X-Rspamd-Queue-Id: 48RvyJ3Vklz3K9X X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=X1jQzbBC; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of marioolofo@gmail.com designates 2607:f8b0:4864:20::743 as permitted sender) smtp.mailfrom=marioolofo@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; HAS_ATTACHMENT(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (1.77), ipnet: 2607:f8b0::/32(-1.88), asn: 15169(-1.67), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~,4:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/mixed,multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[3.4.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-Mailman-Approved-At: Wed, 26 Feb 2020 06:22:53 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Feb 2020 23:19:05 -0000 Hello, I reinstalled FreeBSD 12.1 on my SSD (in the swap partition of my Linux to test) and on my Hybrid HDD. Just configured and rc.conf to start my wifi dongle, downoaded git, node and npm via pkg and... as you can see in my screenshot, the ZFS already shows corrupted data... Can't been able to load the FreeBSD from the HDD though, don't know why, if someone direct me how to load the kernel from the HDD via loader or grub2, I'll try =3D) Em ter., 25 de fev. de 2020 =C3=A0s 18:56, Mario Olofo escreveu: > Hello, > > I reinstalled FreeBSD 12.1 on my SSD (in the swap partition of my Linux t= o > test) and on my Hybrid HDD. > > Just configured and rc.conf to start my wifi dongle, downoaded git, node > and npm via pkg and... as you can see in my screenshot, > the ZFS already shows corrupted data... > > Can't been able to load the FreeBSD from the HDD though, don't know why, > if someone direct me how to load the > kernel from the HDD via loader or grub2, I'll try =3D) > > Mario > > Em ter., 25 de fev. de 2020 =C3=A0s 12:11, Karl Denninger > escreveu: > >> >> On 2/25/2020 9:53 AM, John Kennedy wrote: >> > On Tue, Feb 25, 2020 at 11:07:48AM +0000, Pete French wrote: >> >> I have often wondered if ZFS is more aggressive with discs, because >> until >> >> very recently any solid state drive I have used ZFS on broke very >> quicky. ... >> > I've always wondered if ZFS (and other snapshotting file systems) >> would help >> > kill SSD disks by locking up blocks longer than other filesystems >> might. For >> > example, I've got snapshot-backups going back, say, a year then those >> blocks >> > that haven't changed aren't going back into the pool to be rewritten >> (and >> > perhaps favored because of low write-cycle count). As the disk fills >> up, the >> > blocks that aren't locked up get reused more and more, leading to extr= a >> wear >> > on them. Eventually one of those will get to the point of erroring ou= t. >> > >> > Personally, I just size generously but that isn't always an option >> for >> > everybody. >> >> I have a ZFS RaidZ2 on SSDs that has been running for several /years >> /without any problems. The drives are Intel 730s, which Intel CLAIMS >> don't have power-loss protection but in fact appear to; not only do they >> have caps in them but in addition they pass a "pull the cord out of the >> wall and then check to see if the data is corrupted on restart" test on >> a repeated basis, which I did several times before trusting them. >> >> BTW essentially all non-data-center SSDs fail that test and some fail it >> spectacularly (destroying the OS due to some of the in-flight data being >> comingled on an allocated block with something important; if the >> read/erase/write cycle interrupts you're cooked as the "other" data that >> was not being modified gets destroyed too!) -- the Intels are one of the >> very, very few that have passed it. >> >> -- >> -- Karl Denninger >> /The Market-Ticker/ >> S/MIME Email accepted and preferred >> >