"bad interpreter: Input/output error"

[Little Girl]

Hey there,

Jeff wrote:

>dmesg doesn't show anything I find obvious, though I did just try a 
>umount and mount to see what it would show. I got:
>
>2024-01-16T13:10:11,749983-08:00 evict_inodes inode
>00000000446bab82, i_count = 1, was skipped!
>2024-01-16T13:10:11,749991-08:00 evict_inodes inode
>0000000071a4b4b6, i_count = 1, was skipped!
>2024-01-16T13:10:11,749992-08:00 evict_inodes inode
>000000004c4e8a55, i_count = 1, was skipped!
>2024-01-16T13:10:12,058486-08:00 CIFS: Attempting to mount 
>//192.168.1.12/WD8TBNAS03
>
>I have no idea what "evict_inodes" means, but the drive mounted
>despite no message after the "Attempting" one.

If this page can be believed, they're nothing to worry about and are
debugging messages that got accidentally left in by the developers:

https://www.reddit.com/r/linuxquestions/comments/18g3t8l/what_is_happening_with_evict_inodes_inode_was/

>https://unix.stackexchange.com/questions/542554/got-input-output-error-when-execute-any-commands
>
>Thank you for that. It's a little overwhelming for me at the moment,
>but I'll keep it on-hand. I'm also still struggling with idea that
>it could be hardware when I have no other symptoms at all. But maybe
>I'm just in denial.

Hardware issues come in many shapes and sizes and can happen very
suddenly. The same is true for software issues, and it can be
difficult to sort out which you're facing when something strange
happens. That's why I figured it would be a good idea to do some
tests.

>It feels a bit like something incorrect is cached somewhere in 
>cifs-land, but I say that grasping at straws as I wallow in complete 
>ignorance of how this all works under the hood.

I don't know anything about CIFS, but perhaps a team that's dedicated
to it could help out here.

-- 
Little Girl

There is no spoon.