From nobody Fri Sep 6 22:28:31 2024 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4X0rVP5jCSz5W7SR for ; Fri, 06 Sep 2024 22:28:45 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-vs1-f46.google.com (mail-vs1-f46.google.com [209.85.217.46]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X0rVN0sQxz4MWT for ; Fri, 6 Sep 2024 22:28:44 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none); spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.217.46 as permitted sender) smtp.mailfrom=asomers@gmail.com Received: by mail-vs1-f46.google.com with SMTP id ada2fe7eead31-49bc44e52d0so697075137.1 for ; Fri, 06 Sep 2024 15:28:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725661723; x=1726266523; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ZxN5J7058hwez0kyVB857a4f13F0NHoHHjEfJ4ZYx6I=; b=wAi20JAv8gUDbUjMUrTV/ApMWofFl6t+P+TbGhjnJ4L0AeD5XiHznJih/FurnsK2Tr /tRwehEOr3GiWgk0u3Cra+9+jEdUyBNB9B4xJuHM/EVmDQ0qhCbnhh07wPXG9GKrY+i+ n6YnUJAU7V/PdnWQ3ApgY+8XzHoeV0XUFe7tfM3v90fqwT18wp82nOsrkKJYTN0IS1pW wIzDOm0MK/y6xVopsNPyWXIS1QaT1eA4sO/9qjR4X0x02pkBP9+u5ySFaK6JC1+SBBd7 fTCTtiSG2Bxzg9VX06hcfJNrvgom2emnuJhKZBn3AfS9Jg79Guy05HbkvaXdxVXGK/Bl lWXQ== X-Forwarded-Encrypted: i=1; AJvYcCXAhcQMC7v9Sccwi9y6H2mhuDaR9bk3KM+FHyn3Y5x0rWbgaFbSFZdS5mvQn31z7dN8QsFgLC59R9W2@freebsd.org X-Gm-Message-State: AOJu0Yyq6/Fx/8hrc+o4vUVoHilBz2PwrIvSMGmLPVr+H4J1RRegvnXH MpSAEepxrjF7mMRZxxITkAsENTEpc+ZaFZU+XmaBJ45ud3BKuCOA7m5ohsODd5m9aCXO3QSW0LM bcnedsIn/lHRpxIYs0RTwH0oK7f7KGX6A X-Google-Smtp-Source: AGHT+IGaxVqZJ1m3gx0CeQZVuHrQJ2QxzuY3Jd88Ic0EtxGD5pJ0+IzeTnUVfdh0w6Mie8Fqq+lJJE4cbPOIUtLE6Do= X-Received: by 2002:a05:6102:c0f:b0:49b:e3fd:b6d0 with SMTP id ada2fe7eead31-49bedb7464cmr497225137.5.1725661723000; Fri, 06 Sep 2024 15:28:43 -0700 (PDT) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 References: <5ED5CB56-2E2A-4D83-8CDA-6D6A0719ED19@distal.com> <6A20ABDA-9BEA-4526-94C1-5768AA564C13@distal.com> <0CF1E2D7-6C82-4A8B-82C3-A5BF1ED939CF@distal.com> <29003A7C-745D-4A06-8558-AE64310813EA@distal.com> <42346193-AD06-4D26-B0C6-4392953D21A3@gmail.com> <50B791D8-F0CC-431E-93B8-834D57AB3C14@gmail.com> In-Reply-To: From: Alan Somers Date: Fri, 6 Sep 2024 16:28:31 -0600 Message-ID: Subject: Re: Unable to replace drive in raidz1 To: Chris Ross Cc: Wes Morgan , FreeBSD Filesystems Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.90 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; MIME_GOOD(-0.10)[text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; RCPT_COUNT_THREE(0.00)[3]; FREEMAIL_CC(0.00)[gmail.com,freebsd.org]; TO_DN_ALL(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; MISSING_XM_UA(0.00)[]; FREEFALL_USER(0.00)[asomers]; FREEMAIL_ENVFROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; TAGGED_RCPT(0.00)[freebsd]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.217.46:from]; RCVD_IN_DNSWL_NONE(0.00)[209.85.217.46:from] X-Rspamd-Queue-Id: 4X0rVN0sQxz4MWT On Fri, Sep 6, 2024 at 4:22=E2=80=AFPM Chris Ross wrote: > > > > > On Sep 6, 2024, at 18:02, Alan Somers wrote: > > Another user reports the same error message. In their case, it's an > > inappropriate error message from /sbin/zpool. Can you try a "zpool > > status -v" and "diskinfo -f /dev/da10"? That will show you if you > > have the same problem. If your pool has a 512B block size but the new > > disk is 4kn, then you cannot use it as a replacement. > > > > https://github.com/openzfs/zfs/issues/14730 > > Yeah, I came across that in my searching. Although, I thought people > had found success adding =E2=80=9C-o ashift=3D9=E2=80=9D to the replace c= ommand. > I can confirm that this raidz1 is ashift=3D9, and the disks in it 512 > byte sectorsize. The other two raidz=E2=80=99s are ashift=3D12. > > diskinfo shows 512 as sectorsize for one of the older disks > (matching model to the removed da3), and 4096 sectorsize > for the new disk. > > Is this totally impossible? I know I have replaced smaller disks with > much larger ones in the past, though it=E2=80=99s been a few years and > I don=E2=80=99t remember the details. Is there really no way to put a 4k > block disk in a set with 512 byte blocks? I thought they were still > able to =E2=80=9Cact=E2=80=9D like 512-byte block disks? (512e) > > - Chris If it's a 4kn disk, then what you ask for is impossible. If it's 512e, then it should've already worked. With diskinfo, a 512e disk will have 512 sectorsize and 4096 stripesize. A 4kn disk will show 4096 sectorsize. If you cannot obtain a 512n or 512e disk, then I'm afraid that you'll have to recreate your whole pool. -Alan