Re: Following a panic (271945): zpool status reports 1 data error but identifies no file

On 11/06/2023 19:06, Graham Perrin wrote: … I think it likely that the reportedly permanent error will simply disappear when the scrub completes. True; % date ; zpool status -x Mon 12 Jun 2023 02:00:49 BST all pools are healthy % zdb … might be looking for a needle in a haystack, when ther

Directory 1002/ missing from /var/run/user/

What normally takes care of creation of the numbered directories? A few hours ago, it was unexpectedly missing: % whoami grahamperrin % ls -dhln ~ drwxr-xr-x  143 1002  1002   240B 11 Jun 13:38 /home/grahamperrin % ls -hl /var/run/user total 1 drwx--  2 root    wheel  2B 19 May 0

Re: Following a panic (271945): zpool status reports 1 data error but identifies no file

On 11/06/2023 18:51, Cy Schubert wrote: Zpool export/import or reboot may fix this. Thanks, it's my boot pool, and there have been two boots since my first email: % grep BOOT /var/log/messages Jun 11 13:29:13 mowa219-gjp4-8570p-freebsd kernel: ---<>--- Jun 11 13:50:04 mowa219-gjp4-8570p-fre

Re: Following a panic (271945): zpool status reports 1 data error but identifies no file

On June 11, 2023 5:58:49 AM PDT, Miroslav Lachman <000.f...@quip.cz> wrote: >On 11/06/2023 14:02, Graham Perrin wrote: >> See below, should I begin scrubbing? Or (before I begin) might zdb reveal >> something useful? >> >> The supposed error was observable after >>

Re: Following a panic (271945): zpool status reports 1 data error but identifies no file

On 11/06/2023 14:48, Alexander Motin wrote: On 11.06.2023 08:02, Graham Perrin wrote: See below, should I begin scrubbing? Or (before I begin) might zdb reveal something useful? The only case when I would not recommend to run scrub is if there is a suspicion of memory corruptions on the syste

Re: Following a panic (271945): zpool status reports 1 data error but identifies no file

On 11/06/2023 14:02, Graham Perrin wrote: See below, should I begin scrubbing? Or (before I begin) might zdb reveal something useful? The supposed error was observable after /271945 – panic: deadlres_td_sleep_q: possible deadlock det

Following a panic (271945): zpool status reports 1 data error but identifies no file

See below, should I begin scrubbing? Or (before I begin) might zdb reveal something useful? The supposed error was observable after /271945 – panic: deadlres_td_sleep_q: possible deadlock detected for 0xfe0133324ac0 (stat), block