Original Question:
> Has anybody seen this message before:
>
> Apr 22 10:55:01 sartre unix: WARNING: KERNEL: munlink: could not perform unlink ioctl, closing anyway (1)
>
> uname -a
> SunOS sartre 5.6 Generic_105181-04 sun4u sparc SUNW,Ultra-4
>
> We see this message about once a day on our E450.
>
> Can anybody tell me what the problem is?
>
> Thanks,
> Louis.
>
> ---------------
> Louis Hoo
> lhoo@fcicom.com
>
>
>
Summary:
I Received only one response from
Rahul Roy <uroy@eadev1.vanguard.com>
who pointed me to the following bug report from Sun.
Bug Id: 1178894
Category: network
Subcategory: internet
State: closed
Release summary: s495_dev_phase, s494_fcs_d
Synopsis: munlinkall during close may report failure when operation succeeded
Integrated in releases:
Patch id:
Duplicate of: 1194928
Description:
In strclose();
if (stp->sd_flag & STRHASLINKS) {
/* help unlink succeed by clearing out errors */
mutex_enter(&stp->sd_lock);
stp->sd_flag &= ~(STRDERR|STWRERR);
stp->sd_rerror = 0;
stp->sd_werror = 0;
mutex_exit(&stp->sd_lock);
(void) munlinkall(stp, LINKCLOSE|LINKNORMAL, crp, &rval);
}
the stream head takes care to clear the error flags, so that when
munlinkall()->munlink()
goes to do the I_UNLINK ioctl the error indication can be checked. However,
the stream
could receive an M_ERROR message after the error is cleared and before the
result of
the ioctl is complete and read.
This currently results in a cmn_err call:
cmn_err(CE_CONT,
"KERNEL: munlink: could not perform unlink ioctl, closing
anyway\n");
which can only result in customer confusion, and therefore service calls.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:39 CDT