Date: Sun, 11 Jun 2023 10:51:01 -0700 From: Cy Schubert <Cy.Schubert@cschubert.com> To: freebsd-current@freebsd.org Subject: =?US-ASCII?Q?Re=3A_Following_a_panic_=28271945=29=3A_zpool_status?= =?US-ASCII?Q?_reports_1_data_error_but_identifies_no_file?= Message-ID: <51E59251-BC66-4BCB-AA31-05863EBE6FC4@cschubert.com> In-Reply-To: <ae1fd2fd-63b9-f872-84cd-a90217604edb@quip.cz> References: <64407335-27be-ca28-68e3-3d3b39afc5a5@freebsd.org> <ae1fd2fd-63b9-f872-84cd-a90217604edb@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On June 11, 2023 5:58:49 AM PDT, Miroslav Lachman <000=2Efbsd@quip=2Ecz> wr= ote: >On 11/06/2023 14:02, Graham Perrin wrote: >> See below, should I begin scrubbing? Or (before I begin) might zdb reve= al something useful? >>=20 >> The supposed error was observable after <https://bugs=2Efreebsd=2Eorg/b= ugzilla/show_bug=2Ecgi?id=3D271945> >>=20 >> /271945 =E2=80=93 panic: deadlres_td_sleep_q: possible deadlock detecte= d for 0xfffffe0133324ac0 (stat), blocked for 1801328 ticks// >> / > >[=2E=2E] > >> errors: Permanent errors have been detected in the following files: > > >Can it be that the error was in file which is deleted now? Or was in snap= shot which was already destroyed by some automatic script? > >Kind regards >Miroslav Lachman > > Zpool export/import or reboot may fix this=2E --=20 Cheers, Cy Schubert <Cy=2ESchubert@cschubert=2Ecom> FreeBSD UNIX: <cy@FreeBSD=2Eorg> Web: https://FreeBSD=2Eorg NTP: <cy@nwtime=2Eorg> Web: https://nwtime=2Eorg e^(i*pi)+1=3D0 Pardon the typos=2E Small keyboard in use=2E
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51E59251-BC66-4BCB-AA31-05863EBE6FC4>