Skip to contentSkip to conversation

IDE/ATAPI in 2.5

DISCUSSION Nick Bellinger 3 participants 3 messages Jul 15, 2002 – Jul 16, 2002

lore
Share & tools
lore
#0 lore raw
Quoted 7 lines

I think someone is misunderstanding some industry buzz words here ... NAS refers to Network Attached Storage, as in via NFS, AFS, et al. What your showing in the output of the Solaris format command are raw SCSI LUNS attached via fibre channel (fabric or loop) or native scsi.

Just as a matter of clarification, the above two examples NFS and AFS are most certainly NOT Network Attached Storage aka NAS. The former is an simple Networked File System, and the latter the first practical distributed file system (ie: multiple client access to shares), but they both provide access to storage resources at the FILE SYSTEM level.

The term 'NAS' (and SAN for that matter as the terms are pretty much used interchangeably these days) refer to moving raw disk protocol Command Descriptor Blocks aka CDBs and its associated data across the network at the BLOCK level. But storage folks generically regard the terms as: NAS refers to BLOCK level storage over IP networks, and SAN to BLOCK level storage over a Fibre Channel setup.

The reason being a Storage Area Network is generally a closed, secure, and seperate entity from ones IP network, while Network Attached Storage is storage added directly into an existing IP network. Of course this opens up all of related security considerations when dealing with IP networks, but a discussion of the related issues is beyond the scope of this reply, and dangerously off-topic.

Nicholas 'trying to keep it real' Bellinger

Quoted 47 lines
Quoted 35 lines

From [email protected] Mon Jul 15 11:11:59 2002

Quoted 9 lines · Rik van Riel
Quoted 5 lines

BTW: did you ever look at Solaris / HP-UX, ... and the way they name disks?

someting like: /dev/{r}dsk/c0t0d0s0
This is SCSI bus, target, lun and slice.

I wonder what they'll change it to in order to support network attached storage.

Actually notthing:

dbtecnocasa:{root}:/>format
Searching for disks...done

c2t1d0: configured with capacity of 6.56MB
c2t1d30: configured with capacity of 34.04GB
c2t1d31: configured with capacity of 34.04GB
c2t1d81: configured with capacity of 34.04GB

AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248> /pci@1f,4000/scsi@3/sd@0,0
1. c2t1d0 <EMC-SYMMETRIX-5567 cyl 14 alt 2 hd 15 sec 64> /pci@4,2000/scsi@1/sd@1,0
2. c2t1d30 <EMC-SYMMETRIX-5567 cyl 37178 alt 2 hd 30 sec 64> /pci@4,2000/scsi@1/sd@1,1e
3. c2t1d31 <EMC-SYMMETRIX-5567 cyl 37178 alt 2 hd 30 sec 64> /pci@4,2000/scsi@1/sd@1,1f
4. c2t1d81 <EMC-SYMMETRIX-5567 cyl 37178 alt 2 hd 30 sec 64> /pci@4,2000/scsi@1/sd@1,51

Quoted 1 line

except of c0t0d0 everything else is network attached...

How is it attached? Using FACL or ISCSI?

In any case, it seems to be a natural solution to do it this way.

In order to access a network disk, you need to obtain the right to do so first. Once this has been done, the netork subsystem just looks like a new SCSI bus.

Jörg

#1 lore raw

I would disagree here. NAS _does_ in fact typically refer to storage that is network attached and acessed via some form of network filesystem i.e. NFS and friends. Typically, this is billed as just plugging more storage into the network.

See http://www.quantum.com/Products/NAS+Servers/Default.htm for an example. SearchStorage has a little blurb (which I think could use some additional clarity)
http://whatis.techtarget.com/definition/0,289893,sid9_gci214410,00.html

SAN on the other hand typically requires a different HBA than that NIC you use to access the network. Common access methods are via FiberChannel or iSCSI. As of now SAN based storage also requires more effort, skill and cost to provision. I would expect that to go down over time.

--jauder

Quoted 89 lines · Nick Bellinger
Quoted 7 lines

I think someone is misunderstanding some industry buzz words here ... NAS refers to Network Attached Storage, as in via NFS, AFS, et al. What your showing in the output of the Solaris format command are raw SCSI LUNS attached via fibre channel (fabric or loop) or native scsi.

Just as a matter of clarification, the above two examples NFS and AFS are most certainly NOT Network Attached Storage aka NAS. The former is an simple Networked File System, and the latter the first practical distributed file system (ie: multiple client access to shares), but they both provide access to storage resources at the FILE SYSTEM level.

The term 'NAS' (and SAN for that matter as the terms are pretty much used interchangeably these days) refer to moving raw disk protocol Command Descriptor Blocks aka CDBs and its associated data across the network at the BLOCK level. But storage folks generically regard the terms as: NAS refers to BLOCK level storage over IP networks, and SAN to BLOCK level storage over a Fibre Channel setup.

The reason being a Storage Area Network is generally a closed, secure, and seperate entity from ones IP network, while Network Attached Storage is storage added directly into an existing IP network. Of course this opens up all of related security considerations when dealing with IP networks, but a discussion of the related issues is beyond the scope of this reply, and dangerously off-topic.

Nicholas 'trying to keep it real' Bellinger

Quoted 40 lines
Quoted 35 lines

From [email protected] Mon Jul 15 11:11:59 2002

Quoted 9 lines · Rik van Riel
Quoted 5 lines

BTW: did you ever look at Solaris / HP-UX, ... and the way they name disks?

someting like: /dev/{r}dsk/c0t0d0s0
This is SCSI bus, target, lun and slice.

I wonder what they'll change it to in order to support network attached storage.

Actually notthing:

dbtecnocasa:{root}:/>format
Searching for disks...done

c2t1d0: configured with capacity of 6.56MB
c2t1d30: configured with capacity of 34.04GB
c2t1d31: configured with capacity of 34.04GB
c2t1d81: configured with capacity of 34.04GB

AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248> /pci@1f,4000/scsi@3/sd@0,0
1. c2t1d0 <EMC-SYMMETRIX-5567 cyl 14 alt 2 hd 15 sec 64> /pci@4,2000/scsi@1/sd@1,0
2. c2t1d30 <EMC-SYMMETRIX-5567 cyl 37178 alt 2 hd 30 sec 64> /pci@4,2000/scsi@1/sd@1,1e
3. c2t1d31 <EMC-SYMMETRIX-5567 cyl 37178 alt 2 hd 30 sec 64> /pci@4,2000/scsi@1/sd@1,1f
4. c2t1d81 <EMC-SYMMETRIX-5567 cyl 37178 alt 2 hd 30 sec 64> /pci@4,2000/scsi@1/sd@1,51

Quoted 1 line

except of c0t0d0 everything else is network attached...

How is it attached? Using FACL or ISCSI?

Quoted 7 lines

In any case, it seems to be a natural solution to do it this way.

In order to access a network disk, you need to obtain the right to do so first. Once this has been done, the netork subsystem just looks like a new SCSI bus.

J�rg

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#2 lore raw
In reply to Nick Bellinger

As apposed to creating a huge list of URL's to illustrate my point, since EMC LUNS were provided below, i'll point you to EMC's "NAS" solution:

http://www.emc.com/products/networking/celerra.jsp?openfolder=storage_networ
king

They are called "EMC Celerra File Servers" and to keep you from reading the whole site I'll sum it up here. It's a card that you slide into the symmetrix to provide Network Attached Storage, AKA NFS front end to storage that may or may not be also available on a SAN which implies a connection to a fabric.

Regards,

--Buddy

-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Nick Bellinger
Sent: Monday, July 15, 2002 11:28 AM
To: Buddy Lumpkin
Cc: [email protected]
Subject: RE: IDE/ATAPI in 2.5

Quoted 5 lines

I think someone is misunderstanding some industry buzz words here ... NAS refers to Network Attached Storage, as in via NFS, AFS, et al. What your showing in the output of the Solaris format command are raw SCSI LUNS attached via fibre channel (fabric or loop) or native scsi.

Just as a matter of clarification, the above two examples NFS and AFS are most certainly NOT Network Attached Storage aka NAS. The former is an simple Networked File System, and the latter the first practical distributed file system (ie: multiple client access to shares), but they both provide access to storage resources at the FILE SYSTEM level.

The term 'NAS' (and SAN for that matter as the terms are pretty much used interchangeably these days) refer to moving raw disk protocol Command Descriptor Blocks aka CDBs and its associated data across the network at the BLOCK level. But storage folks generically regard the terms as: NAS refers to BLOCK level storage over IP networks, and SAN to BLOCK level storage over a Fibre Channel setup.

The reason being a Storage Area Network is generally a closed, secure, and seperate entity from ones IP network, while Network Attached Storage is storage added directly into an existing IP network. Of course this opens up all of related security considerations when dealing with IP networks, but a discussion of the related issues is beyond the scope of this reply, and dangerously off-topic.

Nicholas 'trying to keep it real' Bellinger

Quoted 40 lines
Quoted 35 lines

From [email protected] Mon Jul 15 11:11:59 2002

Quoted 9 lines · Rik van Riel
Quoted 5 lines

BTW: did you ever look at Solaris / HP-UX, ... and the way they name disks?

someting like: /dev/{r}dsk/c0t0d0s0
This is SCSI bus, target, lun and slice.

I wonder what they'll change it to in order to support network attached storage.

Actually notthing:

dbtecnocasa:{root}:/>format
Searching for disks...done

c2t1d0: configured with capacity of 6.56MB
c2t1d30: configured with capacity of 34.04GB
c2t1d31: configured with capacity of 34.04GB
c2t1d81: configured with capacity of 34.04GB

AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248> /pci@1f,4000/scsi@3/sd@0,0
1. c2t1d0 <EMC-SYMMETRIX-5567 cyl 14 alt 2 hd 15 sec 64> /pci@4,2000/scsi@1/sd@1,0
2. c2t1d30 <EMC-SYMMETRIX-5567 cyl 37178 alt 2 hd 30 sec 64> /pci@4,2000/scsi@1/sd@1,1e
3. c2t1d31 <EMC-SYMMETRIX-5567 cyl 37178 alt 2 hd 30 sec 64> /pci@4,2000/scsi@1/sd@1,1f
4. c2t1d81 <EMC-SYMMETRIX-5567 cyl 37178 alt 2 hd 30 sec 64> /pci@4,2000/scsi@1/sd@1,51

Quoted 1 line

except of c0t0d0 everything else is network attached...

How is it attached? Using FACL or ISCSI?

Quoted 7 lines

In any case, it seems to be a natural solution to do it this way.

In order to access a network disk, you need to obtain the right to do so first. Once this has been done, the netork subsystem just looks like a new SCSI bus.

Jörg

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/