topic Not able to create snapshot using SDU4.1 on Solaris in Data Protection https://community.netapp.com/t5/Data-Protection/Not-able-to-create-snapshot-using-SDU4-1-on-Solaris/m-p/35587#M10219 <HTML><HEAD></HEAD><BODY><P>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&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dgtype SVM hostvol: /dev/md/sun1_diskset1/dsk/d50&nbsp; state: AVAIL fs: /dev/md/sun1_diskset1/dsk/d50&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mount point: /u01 (non-persistent) fstype ufs device filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; adapter path&nbsp;&nbsp;&nbsp; size&nbsp;&nbsp;&nbsp; proto&nbsp; state&nbsp; clone&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; lun path&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; backing snapshot ----------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ------- ----&nbsp;&nbsp;&nbsp; ----&nbsp;&nbsp;&nbsp; -----&nbsp; -----&nbsp; -----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ---------------- /dev/dsk/c4t500A0982862807D9d1s2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; information not available -- LUN may be offline /dev/dsk/c4t500A0982862807D9d0s2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 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&gt; lun show&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /vol/ken_sun1_vol1/lun1.lun&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5g (5368709120)&nbsp;&nbsp;&nbsp; (r/w, online, mapped)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /vol/ken_sun1_vol2/lun2.lun&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2g (2147483648)&nbsp;&nbsp;&nbsp; (r/w, online, mapped)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /vol/ken_sun1_vol3/lun3.lun&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2g (2147483648)&nbsp;&nbsp;&nbsp; (r/w, online, mapped)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /vol/ken_sun1_vol4/lun4.lun&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2g (2147483648)&nbsp;&nbsp;&nbsp; (r/w, online, mapped)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /vol/ken_sun1_vol5/lun5.lun&nbsp;&nbsp;&nbsp; 1.2t (1318689177600) (r/w, online, mapped)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /vol/ken_sun1_vol6/lun6.lun&nbsp;&nbsp;&nbsp; 1.2t (1318689177600) (r/w, online, mapped)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /vol/ken_sun1_vol7/lun7.lun&nbsp;&nbsp;&nbsp; 8.0g (8571060224)&nbsp;&nbsp;&nbsp; (r/w, online, mapped) fas1&gt; vol status&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Volume State&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Status&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Options&nbsp;&nbsp; ken_sun1_vol6 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; nosnap=on, nosnapdir=on,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; guarantee=none&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; vol0 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; root&nbsp;&nbsp; ken_sun1_vol7 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; nosnap=on, nosnapdir=on&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; vol1 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp; ken_sun1_vol4 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; nosnap=on, nosnapdir=on&nbsp;&nbsp; ken_sun1_vol5 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; nosnap=on, nosnapdir=on,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; guarantee=none&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; test online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp; ken_sun1_vol2 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; nosnap=on, nosnapdir=on&nbsp;&nbsp; ken_sun1_vol3 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; nosnap=on, nosnapdir=on&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; volsource online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp; ken_sun1_vol1 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; nosnap=on, nosnapdir=on fas1&gt; bash-3.00# sanlun lun show&nbsp;&nbsp; filer:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; lun-pathname&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; device filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; adapter&nbsp; protocol&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; lun size&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; lun state&nbsp;&nbsp;&nbsp;&nbsp; fas1:&nbsp; /vol/ken_sun1_vol6/lun6.lun&nbsp; /dev/rdsk/c4t500A0982862807D9d5s2&nbsp; lpfc0&nbsp;&nbsp;&nbsp; FCP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1.2t (1318689177600)&nbsp; GOOD&nbsp;&nbsp;&nbsp;&nbsp; fas1:&nbsp; /vol/ken_sun1_vol5/lun5.lun&nbsp; /dev/rdsk/c4t500A0982862807D9d4s2&nbsp; lpfc0&nbsp;&nbsp;&nbsp; FCP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1.2t (1318689177600)&nbsp; GOOD&nbsp;&nbsp;&nbsp;&nbsp; fas1:&nbsp; /vol/ken_sun1_vol4/lun4.lun&nbsp; /dev/rdsk/c4t500A0982862807D9d3s2&nbsp; lpfc0&nbsp;&nbsp;&nbsp; FCP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2g (2147483648)&nbsp;&nbsp;&nbsp; GOOD&nbsp;&nbsp;&nbsp;&nbsp; fas1:&nbsp; /vol/ken_sun1_vol3/lun3.lun&nbsp; /dev/rdsk/c4t500A0982862807D9d2s2&nbsp; lpfc0&nbsp;&nbsp;&nbsp; FCP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2g (2147483648)&nbsp;&nbsp;&nbsp; GOOD&nbsp;&nbsp;&nbsp;&nbsp; fas1:&nbsp; /vol/ken_sun1_vol2/lun2.lun&nbsp; /dev/rdsk/c4t500A0982862807D9d1s2&nbsp; lpfc0&nbsp;&nbsp;&nbsp; FCP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2g (2147483648)&nbsp;&nbsp;&nbsp; GOOD&nbsp;&nbsp;&nbsp;&nbsp; fas1:&nbsp; /vol/ken_sun1_vol1/lun1.lun&nbsp; /dev/rdsk/c4t500A0982862807D9d0s2&nbsp; lpfc0&nbsp;&nbsp;&nbsp; FCP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5g (5368709120)&nbsp;&nbsp;&nbsp; GOOD&nbsp;&nbsp;&nbsp;&nbsp; fas1:&nbsp; /vol/ken_sun1_vol7/lun7.lun&nbsp; /dev/rdsk/c4t500A0982862807D9d6s2&nbsp; lpfc0&nbsp;&nbsp;&nbsp; FCP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8.0g (8571060224)&nbsp;&nbsp;&nbsp; GOOD bash-3.00# I have attached the sd-trace.log file for reference. Thanks! regards, Ken</P></BODY></HTML> Thu, 05 Jun 2025 07:27:42 GMT limk 2025-06-05T07:27:42Z Not able to create snapshot using SDU4.1 on Solaris https://community.netapp.com/t5/Data-Protection/Not-able-to-create-snapshot-using-SDU4-1-on-Solaris/m-p/35587#M10219 <HTML><HEAD></HEAD><BODY><P>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&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dgtype SVM hostvol: /dev/md/sun1_diskset1/dsk/d50&nbsp; state: AVAIL fs: /dev/md/sun1_diskset1/dsk/d50&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mount point: /u01 (non-persistent) fstype ufs device filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; adapter path&nbsp;&nbsp;&nbsp; size&nbsp;&nbsp;&nbsp; proto&nbsp; state&nbsp; clone&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; lun path&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; backing snapshot ----------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ------- ----&nbsp;&nbsp;&nbsp; ----&nbsp;&nbsp;&nbsp; -----&nbsp; -----&nbsp; -----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ---------------- /dev/dsk/c4t500A0982862807D9d1s2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; information not available -- LUN may be offline /dev/dsk/c4t500A0982862807D9d0s2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 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&gt; lun show&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /vol/ken_sun1_vol1/lun1.lun&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5g (5368709120)&nbsp;&nbsp;&nbsp; (r/w, online, mapped)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /vol/ken_sun1_vol2/lun2.lun&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2g (2147483648)&nbsp;&nbsp;&nbsp; (r/w, online, mapped)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /vol/ken_sun1_vol3/lun3.lun&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2g (2147483648)&nbsp;&nbsp;&nbsp; (r/w, online, mapped)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /vol/ken_sun1_vol4/lun4.lun&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2g (2147483648)&nbsp;&nbsp;&nbsp; (r/w, online, mapped)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /vol/ken_sun1_vol5/lun5.lun&nbsp;&nbsp;&nbsp; 1.2t (1318689177600) (r/w, online, mapped)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /vol/ken_sun1_vol6/lun6.lun&nbsp;&nbsp;&nbsp; 1.2t (1318689177600) (r/w, online, mapped)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /vol/ken_sun1_vol7/lun7.lun&nbsp;&nbsp;&nbsp; 8.0g (8571060224)&nbsp;&nbsp;&nbsp; (r/w, online, mapped) fas1&gt; vol status&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Volume State&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Status&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Options&nbsp;&nbsp; ken_sun1_vol6 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; nosnap=on, nosnapdir=on,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; guarantee=none&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; vol0 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; root&nbsp;&nbsp; ken_sun1_vol7 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; nosnap=on, nosnapdir=on&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; vol1 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp; ken_sun1_vol4 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; nosnap=on, nosnapdir=on&nbsp;&nbsp; ken_sun1_vol5 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; nosnap=on, nosnapdir=on,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; guarantee=none&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; test online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp; ken_sun1_vol2 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; nosnap=on, nosnapdir=on&nbsp;&nbsp; ken_sun1_vol3 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; nosnap=on, nosnapdir=on&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; volsource online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp; ken_sun1_vol1 online&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raid_dp, flex&nbsp;&nbsp;&nbsp; nosnap=on, nosnapdir=on fas1&gt; bash-3.00# sanlun lun show&nbsp;&nbsp; filer:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; lun-pathname&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; device filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; adapter&nbsp; protocol&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; lun size&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; lun state&nbsp;&nbsp;&nbsp;&nbsp; fas1:&nbsp; /vol/ken_sun1_vol6/lun6.lun&nbsp; /dev/rdsk/c4t500A0982862807D9d5s2&nbsp; lpfc0&nbsp;&nbsp;&nbsp; FCP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1.2t (1318689177600)&nbsp; GOOD&nbsp;&nbsp;&nbsp;&nbsp; fas1:&nbsp; /vol/ken_sun1_vol5/lun5.lun&nbsp; /dev/rdsk/c4t500A0982862807D9d4s2&nbsp; lpfc0&nbsp;&nbsp;&nbsp; FCP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1.2t (1318689177600)&nbsp; GOOD&nbsp;&nbsp;&nbsp;&nbsp; fas1:&nbsp; /vol/ken_sun1_vol4/lun4.lun&nbsp; /dev/rdsk/c4t500A0982862807D9d3s2&nbsp; lpfc0&nbsp;&nbsp;&nbsp; FCP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2g (2147483648)&nbsp;&nbsp;&nbsp; GOOD&nbsp;&nbsp;&nbsp;&nbsp; fas1:&nbsp; /vol/ken_sun1_vol3/lun3.lun&nbsp; /dev/rdsk/c4t500A0982862807D9d2s2&nbsp; lpfc0&nbsp;&nbsp;&nbsp; FCP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2g (2147483648)&nbsp;&nbsp;&nbsp; GOOD&nbsp;&nbsp;&nbsp;&nbsp; fas1:&nbsp; /vol/ken_sun1_vol2/lun2.lun&nbsp; /dev/rdsk/c4t500A0982862807D9d1s2&nbsp; lpfc0&nbsp;&nbsp;&nbsp; FCP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2g (2147483648)&nbsp;&nbsp;&nbsp; GOOD&nbsp;&nbsp;&nbsp;&nbsp; fas1:&nbsp; /vol/ken_sun1_vol1/lun1.lun&nbsp; /dev/rdsk/c4t500A0982862807D9d0s2&nbsp; lpfc0&nbsp;&nbsp;&nbsp; FCP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5g (5368709120)&nbsp;&nbsp;&nbsp; GOOD&nbsp;&nbsp;&nbsp;&nbsp; fas1:&nbsp; /vol/ken_sun1_vol7/lun7.lun&nbsp; /dev/rdsk/c4t500A0982862807D9d6s2&nbsp; lpfc0&nbsp;&nbsp;&nbsp; FCP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8.0g (8571060224)&nbsp;&nbsp;&nbsp; GOOD bash-3.00# I have attached the sd-trace.log file for reference. Thanks! regards, Ken</P></BODY></HTML> Thu, 05 Jun 2025 07:27:42 GMT https://community.netapp.com/t5/Data-Protection/Not-able-to-create-snapshot-using-SDU4-1-on-Solaris/m-p/35587#M10219 limk 2025-06-05T07:27:42Z Re: Not able to create snapshot using SDU4.1 on Solaris https://community.netapp.com/t5/Data-Protection/Not-able-to-create-snapshot-using-SDU4-1-on-Solaris/m-p/35592#M10220 <HTML><HEAD></HEAD><BODY><P>Ken, how did you create /u01.. was it through snapdrive?</P><P></P><P>can you provide output of "snapdrive storage list -all"?</P></BODY></HTML> Thu, 09 Jul 2009 10:40:28 GMT https://community.netapp.com/t5/Data-Protection/Not-able-to-create-snapshot-using-SDU4-1-on-Solaris/m-p/35592#M10220 nagendrk 2009-07-09T10:40:28Z