Date: Thu, 17 Dec 2009 15:12:48 +0100 From: Bas Smeelen <b.smeelen@ose.nl> To: freebsd-questions@freebsd.org Subject: Re: kernel: g_vfs_done error = 5 and initiate_write_inodeblock_ufs2: already started (panic) Message-ID: <4B2A3C60.7050003@ose.nl> In-Reply-To: <hgdchq$6d3$1@ger.gmane.org> References: <4B2A2DE1.6050908@ose.nl> <hgdchq$6d3$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Ivan Voras wrote=3A =3E Bas Smeelen wrote=3A =3E=3E Hi=2C =3E=3E =3E=3E We have a FreeBSD 7=2E2 Release amd64 running at a customers site in= a =3E=3E vmware esx 3=2E5 environment with a san=2E =3E=3E This server is sometimes throwing errors and sometimes panicing or= =3E=3E locking up in ways I have not seen before=2E =3E=3E I would say this has something to do with a failing disk=2C but this= is a =3E=3E virtual disk so I=27m a little bit puzzled=2E =3E=3E I have suggested to the vmware administrator that this could be =3E=3E something within their environment=2C but they cannot find anything= =2E =3E=3E =3E=3E Has someone seen these errors before and maybe have a suggestion how= to =3E=3E find out what the culprit is=3F =3E=3E =3E=3E Dec 1 01=3A58=3A25 tnras166 kernel=3A =3E=3E g=5Fvfs=5Fdone=28=29=3Ada0s1e=5BWRITE=28offset=3D4045619200=2C lengt= h=3D16384=29=5Derror =3D 5 =3E=3E Dec 1 01=3A58=3A25 tnras166 kernel=3A =3E=3E g=5Fvfs=5Fdone=28=29=3Ada0s1e=5BWRITE=28offset=3D6742622208=2C lengt= h=3D16384=29=5Derror =3D 5 =3E=3E Dec 1 01=3A58=3A26 tnras166 kernel=3A =3E=3E g=5Fvfs=5Fdone=28=29=3Ada0s1f=5BWRITE=28offset=3D15796846592=2C leng= th=3D16384=29=5Derror =3D 5 =3E=3E =3E=3E =3E=3E I have been running FreeBSD for a long time on real hardware and in= =3E=3E vmware environments=2C but never encountered these type of errors be= fore=2E =3E=3E There is no filesystem corruption after these messages or after the= =3E=3E panic mentioned in the subject=2E This situation is now happening =3E=3E approximately once every six weeks=2E =3E =3E I have a number of FreeBSD systems running under various versions of =3E VMWare products =28ESX=2C ESXi=2C Server=29 and can tell you that this= is =3E almost certainly a problem on the host side=2E =3E =3E It can happen if the SAN is timeouting=2C for example if it=27s doing d= isk =3E scrubbing too diligently=2C etc=2E or the FC connections are problemati= c=2E =3E Try to get the vmware admin to look at the logs more closely both on =3E the host and on other machines hosted on the same VMWare instance or =3E the same SAN=2E =3E =3E Btw=2E which SAN product is it=3F Hi thanks for the fast response=2E I think this is a Dell/EMC san attached to two Dell PowerEdge =282950=29 servers=2E 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=3F DISCLAIMER=3A This e-mail is for the intended recipient=28s=29 only If you have received it by mistake please let us know by reply and then del= ete it from your system=3B Access=2C disclosure=2C copying=2C distribution or reliance on any of it by= anyone else is prohibited=2E If you as intended recipient have received this e-mail incorrectly=2C pleas= e notify the sender =28via e-mail=29=2E
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B2A3C60.7050003>