SUMMARY: Can't umount failed disk.

From: Maglinger, Paul (PMAGLINGER_at_scvl.com)
Date: 02/21/05

  • Next message: Praveen Patle: "iPlanet Directory Server 5.1 on TruCluster" 
    Date: Mon, 21 Feb 2005 16:44:50 -0600
To: 'Tru64 Unix Managers list' <tru64-unix-managers@ornl.gov>

    Thanks to Tom Blinn, Arne Steinkamm, Howard Arnold, and Jim Fitzmaurice.
    The conclusion is unanimous. The belief is that it could be the result of
    file system metadata operations, or items in the kernel that are queued up
    (like reads and writes). The way to fix it is to bounce the servers. Now I
    just need to schedule a convenient time to do so.

    Thanks again!
    Happy President's Day!

    -----Original Message-----
    From: Maglinger, Paul
    Sent: Monday, February 21, 2005 10:34
    To: 'Tru64 Unix Managers list'
    Subject: Can't umount failed disk.

    ES40 cluster with HSG80 storage running 5.1B PK3. Had a JBOD fail and want
    to move the mount point to another JBOD. When I try to umount the drive I
    get a "device busy" error. fuser shows no active processes on it and no one
    is attempting to access the drive. HP tech support is telling me the only
    way to resolve is to reboot the cluster. This is a production machine and I
    don't really want to take her down now. Anyone have any other suggestions?
     
    Thanks!
     
    A hammer is a great tool... but not for cutting glass.
     
    ________________________________

    Paul Maglinger, A+, CA, CCA, CET, MCSE

    Systems Administrator
    Shoe Carnival Inc.
    (812)867-4674
    pmaglinger@scvl.com

    ________________________________

     

  • Next message: Praveen Patle: "iPlanet Directory Server 5.1 on TruCluster"