Date: Mon, 29 May 2023 00:04:41 -0700 From: David Christensen <dpchrist@holgerdanske.com> To: questions@freebsd.org Subject: Re: read and write back full disk to trigger relocation Message-ID: <0d0186c5-9542-1af3-2ce3-e28480b4b6d7@holgerdanske.com> In-Reply-To: <1957739901.520492.1685310340560@ichabod.co-bxl> References: <a111b6a7-0bf8-d3b9-9611-a7fbf36635b3@artem.ru> <1957739901.520492.1685310340560@ichabod.co-bxl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/28/23 04:12, Artem Kuchin wrote: > I have a 3TB gmirror raid On 5/28/23 14:45, Sysadmin Lists wrote: > Artem Kuchin May 28, 2023, 4:12:21 AM >> If course i can run full disk read once in a while, but i'd rather >> prefer to read and write the data back, so it sector >> is damaged it can trigger relocation. > > From the dd(1) manpage: > > Do a refresh of a disk drive, in order to prevent presently recoverable > read errors from progressing into unrecoverable read errors: > > dd if=/dev/ada0 of=/dev/ada0 bs=1m gmirror(8) examples indicate the device node should be: /dev/mirror/name Where "name" is the argument provided when the mirror was created: # gmirror label name prov ... > That won't trigger relocation, but it will refresh the decaying data. Do you have a URL for an engineering document or standard that describes drive sector reallocation? STFW "drive sector reallocation" I do not see anything that looks authoritative (e.g. disk manufacturer or standards body). David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0d0186c5-9542-1af3-2ce3-e28480b4b6d7>