Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 Jan 2021 03:58:01 +0300
From:      Rozhuk Ivan <rozhuk.im@gmail.com>
To:        "Poul-Henning Kamp" <phk@phk.freebsd.dk>
Cc:        freebsd-current@freebsd.org, Kirk McKusick <mckusick@FreeBSD.org>
Subject:   Re: fsck strange output
Message-ID:  <20210126035801.4cddd775@rimwks.local>
In-Reply-To: <68616.1611607910@critter.freebsd.dk>
References:  <20210125232933.1ad108d1@rimwks.local> <68616.1611607910@critter.freebsd.dk>

index | next in thread | previous in thread | raw e-mail

On Mon, 25 Jan 2021 20:51:50 +0000
"Poul-Henning Kamp" <phk@phk.freebsd.dk> wrote:
> > Disk is 100% alive, got same on other HW.  
> 
> A disk can be alive and still have individually unreadable sectors,
> that is, IMO, the most common failure mode.
> 
> Try:
> 	recoverdisk -v /dev/whatever
> 
> That will attempt to read all sectors on the disk.
> 

This happen on 4 different systems, that:
- based on Ryzen zen/zen+
- FreeBSD 13

2 systems have ECC that works and show no errors.

At least on 12 and prev on read error - kernel show
messages from drivers/geom.

recoverdisk -v - show no error.

I can reproduce this in VBox after disable "soft update journaling".
(I hope that you will not require from me to check VBox HW too :) ) 

VBOx - no "CANNOT READ BLK":
# tunefs -p /dev/ada0p2
tunefs: POSIX.1e ACLs: (-a)                                disabled
tunefs: NFSv4 ACLs: (-N)                                   disabled
tunefs: MAC multilabel: (-l)                               disabled
tunefs: soft updates: (-n)                                 enabled
tunefs: soft update journaling: (-j)                       enabled
tunefs: gjournal: (-J)                                     disabled
tunefs: trim: (-t)                                         disabled
tunefs: maximum blocks per file in a cylinder group: (-e)  4096
tunefs: average file size: (-f)                            16384
tunefs: average number of files in a directory: (-s)       64
tunefs: minimum percentage of free space: (-m)             2%
tunefs: space to hold for metadata blocks: (-k)            1600
tunefs: optimization preference: (-o)                      space
tunefs: volume label: (-L)                                 


VBOx - "CANNOT READ BLK" is present:
# tunefs -p /dev/ada0p2
tunefs: POSIX.1e ACLs: (-a)                                disabled
tunefs: NFSv4 ACLs: (-N)                                   disabled
tunefs: MAC multilabel: (-l)                               disabled
tunefs: soft updates: (-n)                                 enabled
tunefs: soft update journaling: (-j)                       disabled
tunefs: gjournal: (-J)                                     disabled
tunefs: trim: (-t)                                         disabled
tunefs: maximum blocks per file in a cylinder group: (-e)  4096
tunefs: average file size: (-f)                            16384
tunefs: average number of files in a directory: (-s)       64
tunefs: minimum percentage of free space: (-m)             2%
tunefs: space to hold for metadata blocks: (-k)            1600
tunefs: optimization preference: (-o)                      space
tunefs: volume label: (-L) 


5cc52631b3b88dfc36d8049dc8bece8573c5f9af
[PATCH] Rewrite the disk I/O management system in fsck_ffs(8). Other
Since this commit this issue started.
I check: build system from prev commit - OK, build from this - "CANNOT READ BLK".



help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210126035801.4cddd775>