test
> From: storage-discuss-requ...@opensolaris.org > Subject: storage-discuss Digest, Vol 59, Issue 5 > To: storage-discuss@opensolaris.org > Date: Thu, 11 Nov 2010 12:00:07 +0000 > > Send storage-discuss mailing list submissions to > storage-discuss@opensolaris.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.opensolaris.org/mailman/listinfo/storage-discuss > or, via email, send a message with subject or body 'help' to > storage-discuss-requ...@opensolaris.org > > You can reach the person managing the list at > storage-discuss-ow...@opensolaris.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of storage-discuss digest..." > > > Today's Topics: > > 1. Re: crash dump after comstar install (Greg Terkanian) > 2. Re: crash dump after comstar install (Greg Terkanian) > 3. Re: Relationship between volume, LU, target, target group, > etc. (Sumit Gupta) > 4. Re: crash dump after comstar install (James C. McPherson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 10 Nov 2010 05:53:50 PST > From: Greg Terkanian <gr...@crystalcomputer.com> > To: storage-discuss@opensolaris.org > Subject: Re: [storage-discuss] crash dump after comstar install > Message-ID: <1642722467.121289397261730.javamail.tweb...@sf-app1> > Content-Type: text/plain; charset=UTF-8 > > David, > Thanks for your response. I don't understand. I removed the driver from the > BE and installed the Adaptec provided package. Perhaps they are one in the > same? > > -Greg > -- > This message posted from opensolaris.org > > > ------------------------------ > > Message: 2 > Date: Wed, 10 Nov 2010 06:20:34 PST > From: Greg Terkanian <gr...@crystalcomputer.com> > To: storage-discuss@opensolaris.org > Subject: Re: [storage-discuss] crash dump after comstar install > Message-ID: <803392210.141289398865702.javamail.tweb...@sf-app1> > Content-Type: text/plain; charset=UTF-8 > > David, > Can you please explain to me how you can tell it's the snv_134 version of the > driver? Here are the steps I performed to test COMSTAR: > > - Built system > - Removed SUN provided aac driver > - Installed the adaptec provided driver > - Rebooted > - Ran system for months as-is.....when I attempted iSCSI, system became > unresponsive on regular basis > - Installed COMSTAR (on active BE) > - Reboot, panic > - Rebuilt entire system (and installed adaptec provided drivers) > - Upgraded fw/bios on adaptec card and upgraded driver on system > - Rebooted and ran for a few days > - Created a new BE and installed COMSTAR on it via "pkg install > storage-server SUNWiscsit > - Boot to new BE and kernel panic > - Reverted to prior BE > > My current output of modinfo shows: > > 189 fffffffff8026000 128d0 94 1 aac (AAC Driver 2.3.6) > > Thanks, > Greg > -- > This message posted from opensolaris.org > > > ------------------------------ > > Message: 3 > Date: Wed, 10 Nov 2010 11:17:23 -0800 > From: Sumit Gupta <sumitgu...@vmware.com> > To: Peter Taps <ptr...@yahoo.com>, "storage-discuss@opensolaris.org" > <storage-discuss@opensolaris.org> > Subject: Re: [storage-discuss] Relationship between volume, LU, > target, target group, etc. > Message-ID: > <cfea42e5b243a14cb0a85079c670cd5103e16c4ed...@exch-mbx-5.vmware.com> > Content-Type: text/plain; charset="us-ascii" > > Hi Peter > > Before going into details, overall what you are doing is emulating SCSI disks > for access by initiators on the SAN. So for "each disk", one should be able > to say things like: > > - Which initiators can access it. > - Through which targets can the initiators access it. > - What is the SCSI LUN number a given initiator sees when they access this > disk. > > These setting are known as "lun mappings". > > Also you should be able to specify the storage where the data for this > emulated disk is stored. This can be a zvol, a file etc. This is known as > "backing store". > > Also even though you are specifying the LUN mappings for each lun, COMSTAR > does not also you to specify initiators and targets individually. You have to > specify a list of initiators and targets known as "host groups" and "target > groups" (even if the list has only one member). > > So to put everything together: > > A LU is an actual emulated SCSI device (mostly a disk, but you can also > emulate other SCSI devices like tape etc.). If the LU is a disk, then it > needs a backing store which is mostly specified as a zvol (also known as > volume). > > A target is simply an access point for an initiator to come in. When an > initiator logs into a target, it sees a bunch of LUs depending upon the LUN > mappings you specify. > > A view is simply another name for a single LUN mapping entry. > > Target portal group is an iSCSI construct. It is basically a way to tie in a > bunch of IP addresses with an iSCSI target. I think it is described in > COMSTAR Admin guide. But it is different from "target group" which is > basically a list or targets which is then used inside LUN mappings. > > Sumit > > > -----Original Message----- > > From: storage-discuss-boun...@opensolaris.org [mailto:storage-discuss- > > boun...@opensolaris.org] On Behalf Of Peter Taps > > Sent: Monday, November 08, 2010 4:08 PM > > To: storage-discuss@opensolaris.org > > Subject: [storage-discuss] Relationship between volume, LU, target, > > target group, etc. > > > > Folks, > > > > I have gone through various articles on setting up iSCSI initiator and > > have successfully managed to share an iSCSI volume following the steps. > > This was a simple test scenario. Now, I am trying to set up a specific > > scenario but I am confused on proper relationship between various terms > > that are used. I would appreciate your help in making me understand the > > relationship between the following terms: > > > > - Volume > > - LU > > - Target > > - Target Group > > - Target Portal Group > > - Host Group > > - View > > > > As I understand: > > 1. There is a one-to-one relationship between a volume and its LU. > > 2. A target group consists of targets and a host group consists of > > hosts. > > 2. A view consists of one host group, one target group, and one or more > > LUs. > > > > What I don't understand: > > 1. At first, I thought there is a one-to-one relationship between an LU > > and a target. However, this doesn't seem to be the case. Why would you > > need more than one target in a target group? > > 2. Where does the target portal group fit in? > > > > In my scenario, I would like to share volumes v1 and v2 with hosts h1 > > and h2. I would also like to limit the network to go through ip > > addresses p1 and p2 only. Can someone please give me just the broad > > steps;'' > > > > Thank you in advance for your help. > > > > Regards, > > Peter > > -- > > This message posted from opensolaris.org > > _______________________________________________ > > storage-discuss mailing list > > storage-discuss@opensolaris.org > > http://mail.opensolaris.org/mailman/listinfo/storage-discuss > > > ------------------------------ > > Message: 4 > Date: Thu, 11 Nov 2010 08:48:43 +1000 > From: "James C. McPherson" <j...@opensolaris.org> > To: Greg Terkanian <gr...@crystalcomputer.com> > Cc: storage-discuss@opensolaris.org > Subject: Re: [storage-discuss] crash dump after comstar install > Message-ID: <4cdb214b.8040...@opensolaris.org> > Content-Type: text/plain; charset=UTF-8; format=flowed > > On 11/11/10 12:20 AM, Greg Terkanian wrote: > > David, > > Can you please explain to me how you can tell it's the snv_134 version of > > the driver? Here are the steps I performed to test COMSTAR: > > > > - Built system > > - Removed SUN provided aac driver > > - Installed the adaptec provided driver > > - Rebooted > > - Ran system for months as-is.....when I attempted iSCSI, system became > > unresponsive on regular basis > > - Installed COMSTAR (on active BE) > > - Reboot, panic > > - Rebuilt entire system (and installed adaptec provided drivers) > > - Upgraded fw/bios on adaptec card and upgraded driver on system > > - Rebooted and ran for a few days > > - Created a new BE and installed COMSTAR on it via "pkg install > > storage-server SUNWiscsit > > - Boot to new BE and kernel panic > > - Reverted to prior BE > > > > My current output of modinfo shows: > > > > 189 fffffffff8026000 128d0 94 1 aac (AAC Driver 2.3.6) > > > > Thanks, > > Greg > > > $ what /kernel/drv/amd64/aac > /kernel/drv/amd64/aac: > SunOS 5.11 snv_150 October 2010 > > $ strings /kernel/drv/amd64/aac |grep AAC.Driver > AAC Driver 2.2.11 > > > > James C. McPherson > -- > Oracle > http://www.jmcp.homeunix.com/blog > > > ------------------------------ > > _______________________________________________ > storage-discuss mailing list > storage-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/storage-discuss > > > End of storage-discuss Digest, Vol 59, Issue 5 > **********************************************
_______________________________________________ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
