<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic SnapDrive process failure in Linux  -- more in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/SnapDrive-process-failure-in-Linux-more/m-p/132630#M28923</link>
    <description>The 'SnapDrive process failure in Linux" was closed to add more comments. I had same issue with SDU v5.3.1 and after tried "export LVM_SUPPRESS_FD_WARNINGS=1" under /etc/profile. it did not help me. Later I found the issue from /etc/multipath.conf, after fixing it. The SDU works fine. Just want to share this out.</description>
    <pubDate>Wed, 04 Jun 2025 14:52:27 GMT</pubDate>
    <dc:creator>GLENYU5820</dc:creator>
    <dc:date>2025-06-04T14:52:27Z</dc:date>
    <item>
      <title>SnapDrive process failure in Linux  -- more</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SnapDrive-process-failure-in-Linux-more/m-p/132630#M28923</link>
      <description>The 'SnapDrive process failure in Linux" was closed to add more comments. I had same issue with SDU v5.3.1 and after tried "export LVM_SUPPRESS_FD_WARNINGS=1" under /etc/profile. it did not help me. Later I found the issue from /etc/multipath.conf, after fixing it. The SDU works fine. Just want to share this out.</description>
      <pubDate>Wed, 04 Jun 2025 14:52:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SnapDrive-process-failure-in-Linux-more/m-p/132630#M28923</guid>
      <dc:creator>GLENYU5820</dc:creator>
      <dc:date>2025-06-04T14:52:27Z</dc:date>
    </item>
    <item>
      <title>Re: SnapDrive process failure in Linux  -- more</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SnapDrive-process-failure-in-Linux-more/m-p/132631#M28924</link>
      <description>And what was the issue with multipath.conf?</description>
      <pubDate>Sat, 08 Jul 2017 13:46:09 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SnapDrive-process-failure-in-Linux-more/m-p/132631#M28924</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2017-07-08T13:46:09Z</dc:date>
    </item>
    <item>
      <title>Re: SnapDrive process failure in Linux  -- more</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SnapDrive-process-failure-in-Linux-more/m-p/132709#M28951</link>
      <description>We did not have NetApp suggests settings. Here is what we have working now. ---------------------------------------------------------------------------- blacklist { # wwid 26353900f02796769 devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" devnode "^hd[a-z]" } #multipaths { # multipath { # wwid 3600508b4000156d700012000000b0000 # alias yellow # path_grouping_policy multibus # path_checker readsector0 # path_selector "round-robin 0" # failback manual # rr_weight priorities # no_path_retry 5 # } # multipath { # wwid 1DEC_____321816758474 # alias red # } #} devices { device { vendor "NETAPP" product "LUN" path_grouping_policy group_by_prio features "3 queue_if_no_path pg_init_retries 50" prio "alua" path_checker tur failback immediate path_selector "round-robin 0" hardware_handler "1 alua" rr_weight uniform rr_min_io 128 retain_attached_hw_handler "yes" getuid_callout "/lib/udev/scsi_id -g -u -d /dev/%n" } }</description>
      <pubDate>Tue, 11 Jul 2017 15:03:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SnapDrive-process-failure-in-Linux-more/m-p/132709#M28951</guid>
      <dc:creator>GLENYU5820</dc:creator>
      <dc:date>2017-07-11T15:03:56Z</dc:date>
    </item>
  </channel>
</rss>

