Date: Mon, 24 Aug 2020 07:42:41 -0600 From: Gary Aitken <freebsd@dreamchaser.org> To: Polytropon <freebsd@edvax.de>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Suggestion regarding fsck output enhancement Message-ID: <8e27f7a6-f7db-dec3-0705-e64c4e2cfdb3@dreamchaser.org> In-Reply-To: <20200824104017.4c241ec0.freebsd@edvax.de> References: <20200824104017.4c241ec0.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/24/20 2:40 AM, Polytropon wrote: > Today I came across a situation where I would think fsck should > output a little more information, which would be helpful especially > in diagnostics and dry-run sessions prior to recovery. > > Example: > > INCORRECT BLOCK COUNT I=24236 (288 should be 268) > CORRECT? yes > > Or: > > UNREF FILE I=63518082 OWNER=test1 MODE=100644 > SIZE=0 MTIME=Aug 24 09:45 2020 > RECONNECT? yes > > In both entries, the inode number is mentioned. Wouldn't it be > nice to display a file or directory name, if possible, to show > what file could be affected? +10!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8e27f7a6-f7db-dec3-0705-e64c4e2cfdb3>