OK, time to diagnose some more. Just knowing that you have some commands that don't work, but zpool scrub found no problems, will not help us give any advice for how to proceed.
You say you have a directory called "camera", which is stored somewhere in ZFS. First question: Make sure that directory is actually what you think it is: Go to the parent of the directory, and do a "ls -lF", which will show you whether that directory is in reality a link, and it shows you the link count (second field), which is the number of subdirectories in "camera". Second step: Do stat -x camera
, which will show you a lot of interesting statistics about it. Anything unusual? Is it on the same device as its parent directory? How about permissions, ACLs, and such?
Actually the full directory structure looks like this: /mnt/Files/John/mnt/Media/Camera/LHouse. When I cd to Camera and do an ls -IF on LHouse, it hangs and doesn't provide any information. I am able to ^C out of that.
Here is the output of the stat command:
File: "LHouse"
Size: 20022870 FileType: Directory
Mode: (0777/drwxrwxrwx) Uid: ( 1000/ jwright) Gid: ( 1000/ admin)
Device: 103,3126263904 Inode: 73742 Links: 100
Access: Sat Jul 9 22:47:48 2016
Modify: Sun Apr 9 13:13:13 2017
Change: Sun Apr 9 13:13:13 2017
The content is video from a security camera I used to have in my shop. I shut it down a while ago, but never removed the video clips from the server.
Next thing: You say that rm -rf
, ls
and du
all hang. Do you know anything about the content of that directory? If you could get a listing of all things in that directory (not via using ls
, which will hang, but for example from prior knowledge), you might be able to see whether the problem affects every entry in that directory, or only one.
The content is video from a security camera I used to have in my shop. I shut it down a while ago, but never removed the video clips from the server.
When these commands hang, do you know what state they are in? Do they use CPU time? Can you interrupt them with control C? Are there are console messages about hardware problems or ZFS internals at that time? Ideally, you could drill down further and see exactly what they are doing: Either run ls
under a debugger and see how for it gets, or use dtrace to see what system calls it makes, and what system call it hangs up on.