kernel: g_vfs_done error = 5 and initiate_write_inodeblock_ufs2: already started (panic)

[Bas Smeelen]

Ivan Voras wrote:
> Bas Smeelen wrote:
>> Hi,
>>
>> We have a FreeBSD 7.2 Release amd64 running at a customers site in a
>> vmware esx 3.5 environment with a san.
>> This server is sometimes throwing errors and sometimes panicing or
>> locking up in ways I have not seen before.
>> I would say this has something to do with a failing disk, but this is a
>> virtual disk so I'm a little bit puzzled.
>> I have suggested to the vmware administrator that this could be
>> something within their environment, but they cannot find anything.
>>
>> Has someone seen these errors before and maybe have a suggestion how to
>> find out what the culprit is?
>>
>> Dec  1 01:58:25 tnras166 kernel:
>> g_vfs_done():da0s1e[WRITE(offset=4045619200, length=16384)]error = 5
>> Dec  1 01:58:25 tnras166 kernel:
>> g_vfs_done():da0s1e[WRITE(offset=6742622208, length=16384)]error = 5
>> Dec  1 01:58:26 tnras166 kernel:
>> g_vfs_done():da0s1f[WRITE(offset=15796846592, length=16384)]error = 5
>>
>>
>> I have been running FreeBSD for a long time on real hardware and in
>> vmware environments, but never encountered these type of errors before.
>> There is no filesystem corruption after these messages or after the
>> panic mentioned in the subject. This situation is now happening
>> approximately once every six weeks.
>
> I have a number of FreeBSD systems running under various versions of
> VMWare products (ESX, ESXi, Server) and can tell you that this is
> almost certainly a problem on the host side.
>
> It can happen if the SAN is timeouting, for example if it's doing disk
> scrubbing too diligently, etc. or the FC connections are problematic.
> Try to get the vmware admin to look at the logs more closely both on
> the host and on other machines hosted on the same VMWare instance or
> the same SAN.
>
> Btw. which SAN product is it?
Hi thanks for the fast response.
I think this is a Dell/EMC san attached to two Dell PowerEdge (2950)
servers.

So basically it would be advisable to recommend to look in the vmkernel
and san logs around the same timestamps as I see this happening in the
FreeBSD guest?



DISCLAIMER:
This e-mail is for the intended recipient(s) only

If you have received it by mistake please let us know by reply and then delete it from your system;
Access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited.

If you as intended recipient have received this e-mail incorrectly, please notify the sender (via e-mail).