On Wed, Oct 28, 2026 at 08:09:15AM -0700, bob prohaska wrote:
On Wed, Oct 28, 2026 at 04:11:02AM +0000, void wrote:On Wed, Oct 21, 2026 at 11:33:06AM -0700, bob prohaska wrote: [filesystem errors]Have you tried making an nfs server on a more powerful box and exporting /usr/src ports obj and optionally ccache to your rpi2b? I have a setup like this and it works well. --I haven't, simply because I'd like to understand what went wrong, to the extent of my ability. In the meantime I've added a few files to the repository of errors at http://www.zefox.net/~fbsd/rpi2/disktrouble/ In particular, there are now two diskscan reports taken while accessing the disk via the same powered hub (and hub power supply) that presided over the initial problem. Near as I can tell, the hub does not interfere with the performance of the disk.
The reason I suggested (nfs) was that long ago I had issues with both the pi2b & pi3b read/writing to usb in an OS context.
The breakage becoming particulatly obvious in a read/write of small files situation, like git clone. I put it down to the usb2 ports [1] on both boards not really being up to this OS task. nfs negates this issue, even though the port is only 100Mbit. The issue is not present on fast media plugged into the usb3 port of a pi4. I have not tested something like a git update on the microsd but I'd expect the same issues as encountered on the pi2b & pi3b usb, because the microsd media isn't designed for fast small reads/writes. I'd expect errors. [1] maybe the boards in general. -- void<at>f-m.fm | GPG fingerprint: BD97 5B52 1B78 B7A9 AFFE 7DD4 FD32 D1F9 0814 DECD Please don't Cc: as I'm already subscribed to the list.
signature.asc
Description: PGP signature
