From owner-freebsd-fs@freebsd.org Fri Jul 27 13:08:34 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 17FC4104A1D0 for ; Fri, 27 Jul 2018 13:08:34 +0000 (UTC) (envelope-from fuz@fuz.su) Received: from fuz.su (fuz.su [IPv6:2001:41d0:8:e508::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "amnesiac", Issuer "amnesiac" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A0FB473AAE for ; Fri, 27 Jul 2018 13:08:33 +0000 (UTC) (envelope-from fuz@fuz.su) Received: from fuz.su (localhost [127.0.0.1]) by fuz.su (8.15.2/8.15.2) with ESMTPS id w6RD7h22046647 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 27 Jul 2018 15:07:43 +0200 (CEST) (envelope-from fuz@fuz.su) Received: (from fuz@localhost) by fuz.su (8.15.2/8.15.2/Submit) id w6RD7h5K046646 for freebsd-fs@freebsd.org; Fri, 27 Jul 2018 15:07:43 +0200 (CEST) (envelope-from fuz) Date: Fri, 27 Jul 2018 15:07:43 +0200 From: Robert Clausecker To: freebsd-fs@freebsd.org Subject: badsect(8) is gone -- what now? Message-ID: <20180727130743.GB45967@fuz.su> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jul 2018 13:08:34 -0000 Good evening, I recently tried to use badsect(8) to salvage a slightly broken disk with some janky sectors which the drive doesn't remap but still likes to complain about, just to find out that kernel support for badsect(8) is no longer available in FreeBSD 11.2. This is an annoying situation as I have no way to stop these sectors from being used otherwise. Is there any way the kernel interface for badsect(8) or a utilitiy fulfilling a similar purpose is going to come back? I understand that kernel support was removed due to possible misuse of mknod(S_IFMT) leading to crashes [1], but there really ought to be some way to mark a sector as bad if the disk doesn't want to do it for you. Yours, Robert Clausecker [1]: https://www.mail-archive.com/svn-src-all@freebsd.org/msg151790.html -- () ascii ribbon campaign - for an 8-bit clean world /\ - against html email - against proprietary attachments