Date: Thu, 16 Apr 2020 16:59:42 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Eugene Grosbein <eugen@grosbein.net> Cc: Wojciech Puchar <wojtek@puchar.net>, freebsd-hackers@freebsd.org Subject: Re: fsck parallel check Message-ID: <25031.1587056382@critter.freebsd.dk> In-Reply-To: <571d8b81-f4f9-d371-6cf2-2e7aeb82a09b@grosbein.net> References: <alpine.BSF.2.20.2004161748390.20589@puchar.net> <e5742016-81bb-2ba3-74a4-c633d3627b23@grosbein.net> <alpine.BSF.2.20.2004161824360.3899@puchar.net> <571d8b81-f4f9-d371-6cf2-2e7aeb82a09b@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- In message <571d8b81-f4f9-d371-6cf2-2e7aeb82a09b@grosbein.net>, Eugene Gro= sbein writes: >Not necessary. Fsck tries to parse device name this way: /path/to/nameNUM= BERrest >so it skips all chars upto last /, then extracts "name" part not containi= ng any digits, >then extracts NUMBER part containing only digits, upto maximum lenght. >Then is uses nameNUMBER for "disk name". Yeah, that part sucks... I think it would make sense to make the heuristic that if there are any entries with pass > 2, then ignore the "disk name" and simply run all entries for each pass number in parallel, trusting root to have it figured out. If the highest passnumber is 2, retain the "disk name" heuristic. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25031.1587056382>