Re: Filesystem errors on armv7 -current
- Reply: bob prohaska : "Re: Filesystem errors on armv7 -current"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 21 Oct 2026 20:21:02 UTC
> On Mon, Oct 19, 2026 at 06:43:59PM -0700, bob prohaska wrote: > > On Mon, Oct 19, 2026 at 11:47:56AM -0700, Mark Millard wrote: > > > > > > What about any newer security Email reports? Are they still showing find > > > reporting the various "Input/output error" messages? In the published > > > file they repeated for 2 distinct find commands. > > The security email this morning (10/21/26) contained in part: > > > Checking setuid files and devices: > find: /usr/ports/accessibility/py-atspi: Input/output error > find: /usr/ports/biology/smithwaterman: Input/output error > find: /usr/ports/devel/dwz/files: Input/output error > find: /usr/ports/devel/p5-Config-Parser: Input/output error > find: /usr/src/lib/libc/resolv: Input/output error > find: /usr/src/lib/libpmc/pmu-events/arch/arm64/ampere: Input/output error > find: /usr/src/sys/contrib/device-tree/Bindings/powerpc/nintendo: Input/output > +error > find: /usr/src/sys/contrib/device-tree/Bindings/reset: Input/output error > find: > +/usr/src/sys/contrib/libsodium/src/libsodium/crypto_stream/salsa20/xmm6int: > +Input/output error > > > Checking negative group permissions: > find: /usr/ports/accessibility/py-atspi: Input/output error > find: /usr/ports/biology/smithwaterman: Input/output error > find: /usr/ports/devel/dwz/files: Input/output error > find: /usr/ports/devel/p5-Config-Parser: Input/output error > find: /usr/src/lib/libc/resolv: Input/output error > find: /usr/src/lib/libpmc/pmu-events/arch/arm64/ampere: Input/output error > find: /usr/src/sys/contrib/device-tree/Bindings/powerpc/nintendo: Input/output > +error > find: /usr/src/sys/contrib/device-tree/Bindings/reset: Input/output error > find: > +/usr/src/sys/contrib/libsodium/src/libsodium/crypto_stream/salsa20/xmm6int: > +Input/output error There should be some clues in /var/log/messages about what these I/O errors are. > > However, buildworld/buildkernel and installation of both succeeded last > night, followed by a successful hands-off reboot. A re-run of buildworld > on the previously-built sources is underway now to get /usr/obj up to date. > > Running > # ls -l /usr/ports/accessibility/py-atspi > ls: /usr/ports/accessibility/py-atspi: Input/output error > # > but > # ls -ld /usr/ports/accessibility/py* > drwxr-xr-x 2 root wheel 512 Dec 9 2025 /usr/ports/accessibility/py-atspi > drwxr-xr-x 2 root wheel 512 Dec 9 2025 /usr/ports/accessibility/py-speech-dispatcher > # > does not > > Prior to the last OS build/install cycle /usr/src was renamed /usr/src.old > and replaced by a fresh clone. > > /usr/ports has been kept in its pre-existing form apart from git pulls > > Does this maybe suggest a problem with find? > > Thanks for reading! > > bob prohaska > > > > -- Rod Grimes rgrimes@freebsd.org