Am 30.04.2020 um 20:06 schrieb Warner Losh :
>
> I'm thinking percent used 110 may be the thing it's alerting on, the standard
> says:
Thanks! I figured as much, but I wasn't sure how to interpret the data.
I've noticed that filesystem access appears to have slowed on that box. It's
sister
On Thu, Apr 30, 2020 at 11:48 AM Stefan Bethke wrote:
> nvme0: async event occurred (type 0x1, info 0x00, page 0x02)
> nvme0: device reliability degraded
>
type 1: SMART event
info 0: reliability error
page 2: look at what's up here
1.4 standard says:
NVM subsystem Reliability: NVM subsystem
nvme0: async event occurred (type 0x1, info 0x00, page 0x02)
nvme0: device reliability degraded
Should I be concerned? I'm using this Samsung SSD as cache and log for ZFS on a
12-stable machine.
nvd0: NVMe namespace
nvd0: 122104MB (250069680 512 byte sectors)
# nvmecontrol logpage -p 2 nvme0
The vt (4) man page brings out some inconsistency in its configuration.
"sys/dev/vt/vt.h" header file requires the definition of a prepocessor
macro called "VT_FB_MAX_WIDTH" while a kernel option defines
"VT_FB_DEFAULT_WIDTH" which will be be setup in the file
"opt_syscons.h". This last file
