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

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.

Thanks in advance.


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).

_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: kernel: g_vfs_done error = 5 and initiate_write_inodeblock_ufs2: already started (panic)
    ... We have a FreeBSD 7.2 Release amd64 running at a customers site in a ... I have suggested to the vmware administrator that this could be ... something within their environment, ... 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. ...
    (freebsd-questions)
  • Re: Linux, LDAP and the impossibility of handling editable PDFs
    ... Having FreeBSD as my favorite OS on servers AND hybrid boxes makes life easy - I thought and was touhgt wrong. ... Using 'pdftk' fails, it is not made to run in modern 64 bit environments only when using FreeBSD (linux seems to have no problem, especially Ubuntu does the thing). ... As in other professional environments we were far away from using simple user management and therefore there is a LDAP environment. ...
    (freebsd-questions)
  • Dropped/Duplicate SYN, Cisco PIX/ASA, and and random ISN w/ net.inet.ip.random_id=1
    ... We recently worked closely with some FreeBSD developers to track down ... In a high performance environment, ... random-id. ... the default random port ephemeral source port range is way ...
    (freebsd-net)
  • Re: Experiences with 7.0-CURRENT and vmware.
    ... difference to time keeping on FreeBSD 7 and nor does it seem to have any ... FreeBSD-7 uses the "em" driver. ... Has VMware changed what network hardware they emulate, ... I would advise instead setting up an SSH key ...
    (freebsd-hackers)
  • Re: FreeBSD 5.1 and VMWare
    ... > sources for your system before attempting to install vmware. ... `make buildkernel' method of building the kernel from the FreeBSD ... in the vmware3 package. ...
    (comp.unix.bsd.freebsd.misc)