[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::advfs_support

Title:AdvFS Support/Info/Questions Notefile
Notice:note 187 is Freq Asked Questions;note 7 is support policy
Moderator:DECWET::DADDAMIO
Created:Wed Jun 02 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1077
Total number of notes:4417

1063.0. "msfs_unmount failed message osf 3.2c" by NNTPD::"[email protected]" (Thierry FAIDHERBE) Thu May 22 1997 00:36

Hello boys,

I received a customer problem : msfs_unmount /usr failed message osf 3.2c.
Customer received first time these error after installing 
a (or some) Computer assosciation product, kernel rebuild and reboot.

I explained to customer that these problem may come from a not killed process
using /usr or an opened file on these partition.

Customer paniced when he saw that and called quickly.

Why does the message "msfs_unmount failed for /usr with error 16 during
shutdown" appear on the console during shutdown ?

I found two notes (849 and 893). One replier spoke about patch for 3.2c but
I rode the Readme file for the last -but not least- 3.2c patch release
but .... nothing for that problem.


New problem? Ignore these message ? ??? ??? ???

I saw in one reply that was maybe a but in shutdown command.
I also toke a look for a shutdown patch. but ... ... ...

Can someone have an explanation ???


Hope replies ...

Kind Regards,

+---++---++---++---++---++---++---+ TM  Digital Equipment Belgium
|   ||   ||   ||   ||   ||   ||   |   Multivendor Customer Services
| d || i || g || i || t || a || l |         Thierry FAIDHERBE 
|   ||   ||   ||   ||   ||   ||   |      DIGITAL Unix Support Team
+---++---++---++---++---++---++---+  Email [email protected] 
            Phone : +32 2 729 77 44  Fax : +32 2 729 77 65
 
         I haven't lost my mind, it's backed up on tape somewhere.

[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
1063.1Some things to tryUNIFIX::HARRISJuggling has its ups and downsThu May 22 1997 08:3440
    I just read notes 849 and 893, and I'm guessing that this problem is
    mostly associated with the installation of the Computer assosciation
    product.  I only say that because generally if you change something and
    after that there are problems, the first place to look is at the
    change.
    
    However, I have also had customers say they didn't change anything and
    then remember later that they had installed several patches a few weeks
    before, but just didn't reboot at the time and forgot about when the
    trouble started happening (heck, I've even done that to my self :-)
    
    ----
    
    What you could do is use the lsof utility to see if you can find the
    open file (lsof can be found on the Digital UNIX Freeware CD or at
    <ftp://vic.cc.purdue.edu/pub/tools/unix/lsof/>.  
    
    You could also try using the 'ps' and 'kill' commands to stop as may
    applications as possible before issuing the shutdown command.  If the
    layered products have their own shutdown procedures, then I would try
    using those first, and resort to kill only after that didn't work.
    
    Finally, if the Computer assosciation product has hooks into the
    kernel, it is possible that it has a kernel thread which has the file
    open.  The kernel thread would not normally be stopped by a shutdown
    operation unless the application had its own shutdown procedure as part
    of the /sbin/rc* files.
    
    The customer could always try to build a kernel without the Computer
    assosciation product and see if the problem goes away.
    
    ----
    
    The chances are that this is not a serious problem.  The worse that
    could happen is that the application that has the file open, may not
    have written all its private in-memory buffers to the file.  That would
    affect only the application, it would _NOT_ hurt the file system
    itself.
    
    					Bob Harris
1063.2more infos ....NNTPD::&quot;[email protected]&quot;Thierry FAIDHERBEThu May 22 1997 09:1035
Hi, 

First, thanks for long reply.

Second. I already thaught to stop all computer assosciation process 
before shutdown but not yet done it.

I also thaugth to lsof but these messsage is shortly displaied when shutting
down. In this way, I cannot use lsof   ...

Someone in two other note reply spoke about bug : a misplaced printf.
What do you think about.... really bug or no ??? Patch ???
I toke a look in last release but .... nothing ...

For the kernel, customer added semaphore configuration in the
sysconfigtab file (IPC and INF ssection).

After kernel rebuild and reboot, he saw these error on screen
when system is shutting down ..... 

Is it a ownership problem in /sbin/rc3.d ????

Tomorrow, I will call customer and ask him to kill/stop all new CA process and
after try shutdown.

If problem doesn't occur, it's maybe a Computer Assosciation prob.

Will keep you informed via next reply.

Thanks. Have a nice day.

Thierry


[Posted by WWW Notes gateway]
1063.3DECWET::MARTINThu May 22 1997 11:038
That message is a misplaced printf().  It was introduced to try to track down a
couple of problems, but didn't manage to get removed before we shipped certain
versions of v3.2x.  I don't remember what versions this is in, but I do know it
was fixed for v4.0.

Your customer can safely ignore the message.

--Ken
1063.4NNTPD::&quot;[email protected]&quot;Thierry FAIDHERBEThu May 22 1997 23:538
Hi,

Thanks for .1 and .3 for reply !!!

Have very nice day,

Thierry.
[Posted by WWW Notes gateway]