search for: llc10

...[ID 936769 kern.notice] fd0 is /isa/fdc at 1,3f0/fd @0,0 Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: lockstat0 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] lockstat0 is /pseudo/loc kstat at 0 Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: llc10 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] llc10 is /pseudo/llc1 at 0 Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: lofi0 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] lofi0 is /pseudo/lofi at 0 Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] ps...

I have just recently (physically) moved a system with 16 hard drives (for the array) and 1 OS drive; and in doing so, I needed to pull out the 16 drives so that it would be light enough for me to lift. When I plugged the drives back in, initially, it went into a panic-reboot loop. After doing some digging, I deleted the file /etc/zfs/zpool.cache. When I try to import the pool using the zpool

Hi, I just had my Dell R610 reboot with a kernel panic when I threw a couple of zfs clone commands in the terminal at it. Now, after the system had rebooted zfs will not import my pool anylonger and instead the kernel will panic again. I have had the same symptom on my other host, for which this one is basically the backup, so this one is my last line if defense. I tried to run zdb -e