Subscribe

Not able to create snapshot using SDU4.1 on Solaris

Hi All, I had a question, I am trying to create a snapshot using the snapdrive command for the filesystem on Solaris using SVM, and met with the following errors. Wonder if anyone have met with the similar issue and can throw some lights to it. BTW, the storage is using ONTAP version 7.3.1P3. bash-3.00# snapdrive snap create -fs /u01 -snapname testsnap -fstype ufs 0001-023 Admin error: Unable to discover all LUNs in file system /u01. Devices not responding: /dev/dsk/c4t500A0982862807D9d1s2, /dev/dsk/c4t500A0982862807D9d0s2 Please check the LUN status on the storage system and bring the LUN online if necessary or add the host to the trusted hosts (options trusted.hosts) on the storage system or retry after changing snapdrive.conf to use https for storage system communication and restarting snapdrive daemon. bash-3.00# bash-3.00# snapdrive storage list -fs /u01 -fstype ufs dg: sun1_diskset1              dgtype SVM hostvol: /dev/md/sun1_diskset1/dsk/d50  state: AVAIL fs: /dev/md/sun1_diskset1/dsk/d50      mount point: /u01 (non-persistent) fstype ufs device filename        adapter path    size    proto  state  clone      lun path                    backing snapshot ----------------        ------- ----    ----    -----  -----  -----      --------                    ---------------- /dev/dsk/c4t500A0982862807D9d1s2        information not available -- LUN may be offline /dev/dsk/c4t500A0982862807D9d0s2        information not available -- LUN may be offline bash-3.00# It shows that the “information not available – LUN may be offline”. I have checked on the storage side, the luns and volume are all online: fas1> lun show         /vol/ken_sun1_vol1/lun1.lun      5g (5368709120)    (r/w, online, mapped)         /vol/ken_sun1_vol2/lun2.lun      2g (2147483648)    (r/w, online, mapped)         /vol/ken_sun1_vol3/lun3.lun      2g (2147483648)    (r/w, online, mapped)         /vol/ken_sun1_vol4/lun4.lun      2g (2147483648)    (r/w, online, mapped)         /vol/ken_sun1_vol5/lun5.lun    1.2t (1318689177600) (r/w, online, mapped)         /vol/ken_sun1_vol6/lun6.lun    1.2t (1318689177600) (r/w, online, mapped)         /vol/ken_sun1_vol7/lun7.lun    8.0g (8571060224)    (r/w, online, mapped) fas1> vol status         Volume State          Status            Options   ken_sun1_vol6 online          raid_dp, flex    nosnap=on, nosnapdir=on,                                                   guarantee=none           vol0 online          raid_dp, flex    root   ken_sun1_vol7 online          raid_dp, flex    nosnap=on, nosnapdir=on           vol1 online          raid_dp, flex   ken_sun1_vol4 online          raid_dp, flex    nosnap=on, nosnapdir=on   ken_sun1_vol5 online          raid_dp, flex    nosnap=on, nosnapdir=on,                                                   guarantee=none           test online          raid_dp, flex   ken_sun1_vol2 online          raid_dp, flex    nosnap=on, nosnapdir=on   ken_sun1_vol3 online          raid_dp, flex    nosnap=on, nosnapdir=on       volsource online          raid_dp, flex   ken_sun1_vol1 online          raid_dp, flex    nosnap=on, nosnapdir=on fas1> bash-3.00# sanlun lun show   filer:          lun-pathname                  device filename          adapter  protocol          lun size        lun state     fas1:  /vol/ken_sun1_vol6/lun6.lun  /dev/rdsk/c4t500A0982862807D9d5s2  lpfc0    FCP          1.2t (1318689177600)  GOOD     fas1:  /vol/ken_sun1_vol5/lun5.lun  /dev/rdsk/c4t500A0982862807D9d4s2  lpfc0    FCP          1.2t (1318689177600)  GOOD     fas1:  /vol/ken_sun1_vol4/lun4.lun  /dev/rdsk/c4t500A0982862807D9d3s2  lpfc0    FCP            2g (2147483648)    GOOD     fas1:  /vol/ken_sun1_vol3/lun3.lun  /dev/rdsk/c4t500A0982862807D9d2s2  lpfc0    FCP            2g (2147483648)    GOOD     fas1:  /vol/ken_sun1_vol2/lun2.lun  /dev/rdsk/c4t500A0982862807D9d1s2  lpfc0    FCP            2g (2147483648)    GOOD     fas1:  /vol/ken_sun1_vol1/lun1.lun  /dev/rdsk/c4t500A0982862807D9d0s2  lpfc0    FCP            5g (5368709120)    GOOD     fas1:  /vol/ken_sun1_vol7/lun7.lun  /dev/rdsk/c4t500A0982862807D9d6s2  lpfc0    FCP          8.0g (8571060224)    GOOD bash-3.00# I have attached the sd-trace.log file for reference. Thanks! regards, Ken

Re: Not able to create snapshot using SDU4.1 on Solaris

Ken, how did you create /u01.. was it through snapdrive?

can you provide output of "snapdrive storage list -all"?