Bug 282424

Summary: p9fs: filesystem starts returning 'Invalid argument' after some time
Product: Base System Reporter: Lexi Winter <lexi>
Component: kernAssignee: freebsd-virtualization (Nobody) <virtualization>
Status: Closed FIXED    
Severity: Affects Only Me CC: markj
Priority: ---    
Version: 15.0-CURRENT   
Hardware: amd64   
OS: Any   
See Also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282378

Description Lexi Winter freebsd_triage 2024-10-30 16:24:17 UTC
bhyve guest: FreeBSD 15.0-CURRENT #2 lf/main-n269067-56dd459904b: Sat Oct 19 18:36:40 BST 2024

bhyve host: FreeBSD 15.0-CURRENT #3 lf/main-n269068-2cff93ced1d: Wed Oct 23 02:56:54 BST 2024

this is src from ~53314e34d5e8e7f781ab990805b22f7a56bc0580.  

i have a p9fs filesystem mounted into the VM from the host:

Filesystem    Size    Used   Avail Capacity  Mounted on
torrents       28T    318G     27T     1%    /data/public/Torrents

workload is qBitTorrent, which is mostly random read+write i/o on large (~100MB+) files.  this mostly works fine, but after some time, it begins to return an error:

root@ivy:~ # ls /data/public/Torrents/incomplete 
ls: /data/public/Torrents/incomplete: Invalid argument
root@ivy:~ # ls /data/public/Torrents/downloads 
ls: /data/public/Torrents/downloads: Invalid argument

after unmounting and re-mounting the filesystem, it works fine again briefly but almost immediately breaks again once the workload is started.  to restore service, i had to reboot the VM.

nothing is logged in dmesg when this happens.
Comment 1 Mark Johnston freebsd_committer freebsd_triage 2024-10-30 16:31:24 UTC
I made a few bug fixes in the 9pfs client, commits fff518117b40cbc3bca49073eed85dc725ebae4c and 1f6f247b3526abd4d5927684735012220aefe373.  I don't know if they'll fix your problem, but it's worth a try.
Comment 2 Lexi Winter freebsd_triage 2024-10-30 16:34:14 UTC
thanks, i don't want to update until bug 282378 is resolved but after that's done i'll update and see if it helps.
Comment 3 Lexi Winter freebsd_triage 2024-10-30 21:55:55 UTC
the problem started recurring every 5 minutes or so after reboot, so i updated to ~22429a464a5f4f6bb5a056aae1353985db83b721 which includes those commits.  i'll let you know how it goes but initial results seem promising.
Comment 4 Lexi Winter freebsd_triage 2024-10-31 03:27:01 UTC
it seems like your changes fixed the issues i was running into (thanks!) so i'm going to close this for now, i'll re-open it later if the problem crops up again.