NetApp Technology Network: Message List - SnapDrive process failure in Linux

Re: SnapDrive process failure in Linux

community@netapp.com — Thu, 04 Jun 2009 21:24:54 GMT

OK I think I may have found the solution.

After digging through the snapdrive and snapdrived binaries I noticed that the check it does between RHEL4 and RHEL5 are different.

For RHEL4 it does a 'cat /etc/redhat-release' to get the OS version information.

For RHEL5 id does a 'cat /etc/issue' for the OS information.

As to why this changed I have no idea, just modify '/etc/issue' with:

Red Hat Enterprise Linux Server release 5.3 (Tikanga)

Kernel \r on an \m

Don't forget to set '/etc/redhat-release' back to the original for your system. For RHEL5 it is:

Red Hat Enterprise Linux Server release 5.3 (Tikanga)

Restart snapdrived.

I tested with 'snapdrive storage list -all' and it gave me the correct output.

Hope this helps.

Re: SnapDrive process failure in Linux

community@netapp.com — Thu, 04 Jun 2009 05:14:26 GMT

Mark,

Good luck with the fix. Luckily RHEL is a supported distribution so you're getting much better support with SnapDrive than those of us using CentOS. I look forward to hearing how the resolution turns out and more about the 'hack' they suggested you use and their final fix for you. Perhaps it can shed some light for CentOS users. Thanks for updating the community, it's interesting to hear this problem is now coming up in a supported distribution.

Jesse

Re: SnapDrive process failure in Linux

community@netapp.com — Thu, 04 Jun 2009 03:58:11 GMT

We have RHEL 5.3 with Emulex HBA, Host Utils 5.0, Snapdrive 4.1 and were running into the same issue as above. Netapp has released a fix to make this work, but does not work. This did fix the problem but we need a supportable fix and this is a hack. I have heard Netapp is working on officially releasing the "broken" fix soon. We are trying to figure out what is wrong with our environment that the fix does not work, as they have not released the docs yet. We are supposed to be on the line with the product managers tonight.

Keep you updated.

Re: SnapDrive process failure in Linux

community@netapp.com — Fri, 15 May 2009 22:29:00 GMT

It's great to see so many other users in the last 6 months that have also wanted this. I wonder if NetApp will choose to support it's users any time soon.

Re: SnapDrive process failure in Linux

community@netapp.com — Wed, 06 May 2009 07:17:42 GMT

SnapDrive for UNIX v4.1 works with Redhat v5.2.

What was the original value in the /etc/redhat-release file? What were the commands that were failing?

I do not suspect this to be an an issue with the /etc/redhat-release file. We need to analyze the trace logs and system configuration to understand the problem.

Kindly file a ticket with NetApp and provide them with the output of "snapdrive.dc" and linux_info diagnostic scripts.

Re: SnapDrive process failure in Linux

community@netapp.com — Mon, 04 May 2009 20:03:11 GMT

This post is directed primarily to the NetApp engineers that check these threads.

I was having the same problems as stated above. I have installed SnapDrive for Unix(Linux) 4.1 on a RHEL 5.2 server. The install works fine and the SDU daemon appears to be working properly. However, when running the majority of the snapdrive commands, I receive that following error:

Status call to SDU daemon failed

I tried troubleshooting this problem for a few days, but didn't have much luck. Just today though, I saw the post form Michael Mattsson stating that changing the /etc/redhat-release file to read "Red Hat Enterprise Linux Server release 4 (Tikanga)", makes everything magically work. I tried the fix myself, and sure enough, he is correct.

I have been messing around with SnapDrive in our lab, but we are getting ready to deploy it in our production environments. I don't want to have to make this change across thousands of servers, especially since it seems to be a rather "dirty" fix.

Is there any supported fix that is being developed or a patch in a later release? This seems to be a large bug in the SnapDrive code since it claims to be compatible up to RHEL 5.3.

Please let me know.

Thanks.

Re: SnapDrive process failure in Linux

community@netapp.com — Fri, 24 Apr 2009 08:37:19 GMT

Please provide the ticket number.

Re: SnapDrive process failure in Linux

community@netapp.com — Tue, 21 Apr 2009 23:12:35 GMT

Good luck with any type of solid support from NetApp regarding SnapDrive for Unix. I've had a ticket open with them for over 2 weeks with absolutely no hint of resolution.

Funny thing is, the snapdrive utility actually creates the iSCSI LUN on the filer as well as the iGroup but then fails to 'discover' the new LUNs after they have been created:

mapping new lun(s) ... done
discovering new lun(s) ... *failed*

Not so fun times with NetApp.......

Re: SnapDrive process failure in Linux

community@netapp.com — Tue, 17 Mar 2009 21:12:37 GMT

Thanks Michael,

your post made my day. Now I've my proof of concept running, using CentOs 5.1 as a Xen host with VMs (also CentOs 5.1) running a simulator and two Oracle 11g RAC nodes, all controlled by Snapmanager for Oracle.Tested all combinations (NFS, DNFS both directly using the simulators NFS shares as well as ASM on top of NFS shares).

Works great.

Mark

Re: SnapDrive process failure in Linux

community@netapp.com — Wed, 25 Feb 2009 15:33:50 GMT

It should work with FCP. It could be that some settings are not configured properly. Please make sure you have followed SnapDrive for Unix Installation and Administration Guide properly. Please contact NetApp support, if you still have issues.