SUSECON
Results 1 to 8 of 8

Thread: Problems with Shutdown/Boot in a multipathed Environment

Threaded View

  1. Problems with Shutdown/Boot in a multipathed Environment

    Hello!

    We use SLES 11 SP2
    Linux <HOSTNAME> 3.0.26-0.7-default #1 SMP Tue Apr 17 10:27:57 UTC 2012 (3829766) x86_64 x86_64 x86_64 GNU/Linux

    on an Intel Modular Server with Dual Storage Controller Setup.

    Content of /etc/multipath.conf:
    blacklist {
    devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
    devnode "^(hd|xvd)[a-z][[0-9]*]"
    devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*]"
    }

    devices {
    device {
    vendor "Intel"
    product "Multi-Flex"
    path_grouping_policy "group_by_prio"
    getuid_callout "/lib/udev/scsi_id -g -u /dev/%n"
    prio "alua"
    path_checker tur
    path_selector "round-robin 0"
    hardware_handler "1 alua"
    failback immediate
    rr_weight uniform
    rr_min_io 100
    no_path_retry queue
    features "1 queue_if_no_path"
    }
    }



    Output of "multipath -ll"
    222d60001557a1912 dm-1 Intel,Multi-Flex
    size=550G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
    |-+- policy='round-robin 0' prio=130 status=active
    | `- 0:0:0:1 sdb 8:16 active ready running
    `-+- policy='round-robin 0' prio=1 status=enabled
    `- 0:0:1:1 sdd 8:48 active ready running
    2228900015565f670 dm-0 Intel,Multi-Flex
    size=40G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
    |-+- policy='round-robin 0' prio=130 status=active
    | `- 0:0:0:0 sda 8:0 active ready running
    `-+- policy='round-robin 0' prio=1 status=enabled
    `- 0:0:1:0 sdc 8:32 active ready running





    The redundant Storage connection just works fine. We can remove one of the controllers and the Server switches
    to the other path.
    But when we shutdown the server, SuSE Linux is not able to do a clean unmount.
    The following message is printed to the console:

    "Not shutting down MD Raid - reboot/halt scripts do this." missing
    Removing multipath targets: May 21 08:53:52 | 22289xxxxx_part2: map in use
    May 21 08:53:52 | failed to remove multipath map 22289xxxxx



    As a consequence it happened one time, that on bootup, fsck (File-System-Check) found
    an orphaned inode and remove it.

    How can we configure SLES 11 SP2 that it does a clean shutdown? Or is this normal behaviour?

    Thanks for your reply in advance!
    Last edited by kaiwindheuser; 21-May-2012 at 10:16.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •