UFS Filesystem issues, and the loss of my hair...

[John Baldwin]

On Monday 10 August 2009 4:15:44 pm Hearn, Trevor wrote:
> Here is the chunk that I grabbed from the screen to save as a memento. :)
> 
> Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=16384)]error = 5
> Aug 10 10:53:43 XXXX last message repeated 20 times
> Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=1638d)]error = 5
> Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=16384)]error = 5
> Aug 10 10:53:43 XXXX last message repeated 18 times
> Aug 10 10:53:43 XXXX kernel: g_vfs_done()-da1p7[READ(offset=
> Aug 10 10:53:43 XXXX kernel: -6419569950008350720, length=16384)]error = 5
> Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=16384)]error = 5
> Aug 10 10:53:43 XXXX last message repeated 19 times
> Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, l=ngth=16384)]error 1 5
> Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=16384)]error = 5
> Aug 10 10:53:43 XXXX last message repeated 6 times
> Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=16384o]error = 5
> Aug 10 10:53:43 XXXX kernel:
> Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=16384)]error = 5
> Aug 10 10:53:43 XXXX last message repeated 22 times
> Aug 10 10:53:44 XXXX kernel: READ(offset=-6419569950008350720, length=16384)]error = 5
> Aug 10 10:53:44 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=16384)]error = 5
> Aug 10 10:53:44 XXXX last message repeated 849 times
> 
> As you can see, it's a little disjointed. I would assume that the screwed up length information is from the speed at which it was coming out, and possibly another message got throw in at the same time? 

Yes, it does seem like it was part of one of the other messages.  The isp(4)
driver was just recently updated in HEAD by mjacob@ who has maintained that
driver in the past.  He may have some insight if there is an isp(4)-specific
problem.

-- 
John Baldwin