Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #286819

Re: Schrödinger's hash

From nwe <nwe@gitcoding.net>
Newsgroups linux.debian.user
Subject Re: Schrödinger's hash
Date 2026-05-22 21:50 +0200
Message-ID <MXE2B-76es-9@gated-at.bofh.it> (permalink)
References <MXAs1-73P1-5@gated-at.bofh.it> <MXCWR-75wX-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On 5/22/26 1:32 PM, Van Snyder wrote:

> I remarked to a local computer repair shop that I have a four TB 
> backup drive. He said "replace it. Four TB isn't ready yet."
How so? I though 4TB is showing its age...

I'm running 12x 4TB drives. Used SAS drives. Accumulated power on time 
ranges from 40,166 to 73,439 hours.

Smartctl informs me device /dev/sdf is worsening with increased read 
errors over time. That one shows 73408 hours powered up, 72360.67 GB 
read, 119545.193 GB written, 195 power cycles (13 since July 13 2024). 
Defect list increased from 3 to 6872.

I see two other drives have defect lists of 23 and 14, respectively. All 
others are at 0. Considering that, I should probably prioritize 
replacing at least sdf soon to avoid losing redundancy during resilver, 
considering the age of the pool.


nwe@srv01:~$ zpool status -c vendor,model,size
pool: POOL1
state: ONLINE
scan: scrub repaired 0B in 04:10:05 with 0 errors on Sun May 10 04:34:06 
2026
config:

NAME        STATE     READ WRITE CKSUM   vendor         model  size
POOL1       ONLINE       0     0     0
raidz3-0  ONLINE       0     0     0
sdb     ONLINE       0     0     0  SEAGATE  ST4000NM0023  3.6T
sdc     ONLINE       0     0     0  TOSHIBA   MG04SCA40EN  3.6T
sdd     ONLINE       0     0     0  TOSHIBA   MG04SCA40EN  3.6T
sde     ONLINE       0     0     0  SEAGATE  ST4000NM0023  3.6T
sdf     ONLINE       0     0     0  SEAGATE  ST4000NM0023  3.6T
sdh     ONLINE       0     0     0       HP   MB4000FCWDK  3.6T
sdg     ONLINE       0     0     0       HP   MB4000FCWDK  3.6T
sdi     ONLINE       0     0     0  SEAGATE  ST4000NM0023  3.6T
sdj     ONLINE       0     0     0  SEAGATE  ST4000NM0023  3.6T
sdk     ONLINE       0     0     0  SEAGATE  ST4000NM0023  3.6T
sdl     ONLINE       0     0     0       HP   MB4000FCWDK  3.6T
sdm     ONLINE       0     0     0       HP   MB4000FCWDK  3.6T

errors: No known data errors

Back to linux.debian.user | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Schrödinger's hash Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 18:00 +0200
  Re: Schrödinger's hash Andrew Latham <lathama@gmail.com> - 2026-05-22 18:10 +0200
    Re: Schrödinger's hash Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 18:20 +0200
      Re: Schrödinger's hash Andrew Latham <lathama@gmail.com> - 2026-05-22 18:30 +0200
        Re: Schrödinger's hash Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 19:00 +0200
    bad RAM (Was: Schrödinger's hash) nwe <nwe@gitcoding.net> - 2026-05-22 19:40 +0200
      Re: bad RAM (Was: Schrödinger's hash) Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 22:10 +0200
        Re: bad RAM (Was: Schrödinger's hash) nwe <nwe@gitcoding.net> - 2026-05-22 22:30 +0200
          Re: bad RAM (Was: Schrödinger's hash) Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 23:10 +0200
            Re: bad RAM (Was: Schrödinger's hash) nwe <nwe@gitcoding.net> - 2026-05-22 23:30 +0200
          Re: bad RAM (Was: Schrödinger's hash) David Christensen <dpchrist@holgerdanske.com> - 2026-05-23 02:00 +0200
            Re: bad RAM (Was: Schrödinger's  hash) Andy Smith <andy@strugglers.net> - 2026-05-25 13:20 +0200
              Re: bad RAM (Was: Schrödinger's hash) David Christensen <dpchrist@holgerdanske.com> - 2026-05-25 23:20 +0200
          Re: bad RAM Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2026-05-25 11:50 +0200
  Re: Schrödinger's hash The Wanderer <wanderer@fastmail.fm> - 2026-05-22 18:20 +0200
    Re: Schrödinger's hash Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 19:10 +0200
  Re: Schrödinger's hash David Christensen <dpchrist@holgerdanske.com> - 2026-05-22 20:10 +0200
  Re: Schrödinger's hash Van Snyder <van.snyder@sbcglobal.net> - 2026-05-22 20:40 +0200
    Re: Schrödinger's hash nwe <nwe@gitcoding.net> - 2026-05-22 21:50 +0200
      Re: Schrödinger's hash David Christensen <dpchrist@holgerdanske.com> - 2026-05-23 01:30 +0200
        Re: Schrödinger's hash Van Snyder <van.snyder@sbcglobal.net> - 2026-05-23 01:40 +0200
        Re: Schrödinger's hash nwe <nwe@gitcoding.net> - 2026-05-23 02:20 +0200
          Re: Schrödinger's hash David Christensen <dpchrist@holgerdanske.com> - 2026-05-23 07:50 +0200
            Home server (Was: Re: Schrödinger's hash) nwe <nwe@gitcoding.net> - 2026-05-23 17:00 +0200
              Re: Home server (Was: Re: Schrödinger's hash) David Christensen <dpchrist@holgerdanske.com> - 2026-05-24 04:30 +0200

csiph-web