129 lines
7.7 KiB
HTML
129 lines
7.7 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2005" />
|
||
|
|
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Introducing network server storage spaces" />
|
||
|
|
<meta name="abstract" content="This topic discusses network server storage spaces and how to name them." />
|
||
|
|
<meta name="description" content="This topic discusses network server storage spaces and how to name them." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzau9mandrives.htm" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzau9intronsss" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Introducing network server storage spaces</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzau9intronsss"><a name="rzau9intronsss"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Introducing network server storage spaces</h1>
|
||
|
|
<div><p>This topic discusses network server storage spaces and how to name
|
||
|
|
them.</p>
|
||
|
|
<p>Operating systems such as Windows<sup>®</sup>, Unix and Linux<sup>®</sup> work with
|
||
|
|
what they see as physical disk drives; there is little or no virtualization
|
||
|
|
of storage at an operating system level. Because <span class="keyword">i5/OS™</span> virtualizes
|
||
|
|
all disk storage, you can carve out chunks of disk space from the storage
|
||
|
|
pool to form virtual disk drives, which we can then allocate to Linux and Windows.
|
||
|
|
We call these virtual disk drives, storage spaces. Integrated Linux and Windows servers,
|
||
|
|
as well as AIX
|
||
|
|
5L™ and Linux running
|
||
|
|
in iSeries™ partitions,
|
||
|
|
see these storage spaces as physical disk drives.</p>
|
||
|
|
<div class="important"><span class="importanttitle">Important:</span> Because drives, as seen by integrated Linux and Windows servers,
|
||
|
|
are physically scattered over all disk drives in the ASP, you can size a Windows
|
||
|
|
or Linux drive up to the available storage in the specified ASP.</div>
|
||
|
|
<p>The <span class="keyword">i5/OS</span> object that
|
||
|
|
is used to create a Windows or Linux virtual drive is called a Network
|
||
|
|
Server Storage Space (NWSSTG), or storage space for short. These storage spaces
|
||
|
|
are stored in the root of the <span class="keyword">i5/OS</span> Integrated
|
||
|
|
File System (IFS) in a directory called /QFPNWSSTG. You can use the Work with
|
||
|
|
Links (WRKLNK) command from an <span class="keyword">i5/OS</span> command
|
||
|
|
line to view the contents of the /QFPNWSSTG directory. This same storage space
|
||
|
|
architecture is used not only by integrated Linux servers, but also by integrated Windows servers,
|
||
|
|
and Linux and AIX
|
||
|
|
5L running in iSeries logical partitions. Storage spaces can be
|
||
|
|
interchanged between each of these different operating systems. </p>
|
||
|
|
<p>The amount of disk storage that you create for your servers is taken directly
|
||
|
|
from the iSeries available
|
||
|
|
storage, and each Windows or Linux virtual drive is physically scattered
|
||
|
|
across all the real disk drives in the iSeries disk pool.</p>
|
||
|
|
<p>Storage spaces are different from other <span class="keyword">i5/OS</span> file
|
||
|
|
objects because the size that you specify for a storage space is completely
|
||
|
|
allocated at the time it is created. This is because integrated Linux and Windows servers
|
||
|
|
need to be able to connect to and format a drive of a fixed size. </p>
|
||
|
|
<p>The Linux server
|
||
|
|
install command (INSLNXSVR) creates only two drives. These drives are used
|
||
|
|
to store the Linux operating
|
||
|
|
system (called the system drive) and some IBM-supplied drivers (called the
|
||
|
|
installation drive).</p>
|
||
|
|
<p>It is a good idea to make a backup of the system drive before and after
|
||
|
|
you make changes to the operating system. If something should happen, you
|
||
|
|
can recover by restoring a backup of the system drive, rather than rebuilding
|
||
|
|
the server from scratch. In order to recovery quickly from a system failure,
|
||
|
|
you should not store user files on the system or installation drives. Files
|
||
|
|
and data that change frequently should be stored on a different drive. </p>
|
||
|
|
<p>Before you start creating new drives for your server, take some time to
|
||
|
|
calculate what the server needs now and in the future. After the server has
|
||
|
|
been installed you can create additional drives for your Linux server
|
||
|
|
at any time. These drives can be linked to the server while it is shut down
|
||
|
|
(static linking) or started (dynamic linking). This means that you do not
|
||
|
|
need to allocate large portions of your iSeries storage when the server is created;
|
||
|
|
you can create additional drives of any size you wish (up to the limit) when
|
||
|
|
they are needed. </p>
|
||
|
|
<p>Here is a summary of the operations that you can perform on Linux drives:</p>
|
||
|
|
<ul><li>Create a new Linux drive.</li>
|
||
|
|
<li>Delete a Linux drive.</li>
|
||
|
|
<li>Link a Linux drive.</li>
|
||
|
|
<li>Unlink a Linux drive.</li>
|
||
|
|
<li>Clone a Linux drive.</li>
|
||
|
|
<li>Expand a Linux drive.</li>
|
||
|
|
</ul>
|
||
|
|
<p>Linux disk
|
||
|
|
drive operations can be performed in two ways:</p>
|
||
|
|
<ul><li>Using iSeries Navigator.</li>
|
||
|
|
<li>Using CL commands.</li>
|
||
|
|
</ul>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Naming storage spaces</h4><p>It is important to decide
|
||
|
|
on a naming convention for your storage spaces; otherwise you might
|
||
|
|
have trouble correlating storage space names that you see from the <span class="keyword">i5/OS</span> side with drives that you
|
||
|
|
see from the Linux side.
|
||
|
|
This can be especially difficult if you have both statically linked and dynamically
|
||
|
|
linked drives. </p>
|
||
|
|
<p>When the Linux server is created, two drives are
|
||
|
|
created by default: The system and installation drives. They pick up the name
|
||
|
|
of the NWSD with a 1 appended for the system drive, and a 2 appended for the
|
||
|
|
installation drive. For example, for an NWSD named REDHAT1, a system drive
|
||
|
|
named REDHAT11 and an installation drive named REDHAT12 are created. It is
|
||
|
|
not possible to rename these drives directly. You must copy them and then
|
||
|
|
supply a new name to the copy. However, it is rarely necessary to rename these
|
||
|
|
two drives, as it is obvious which NWSD they are associated with. </p>
|
||
|
|
<p>We
|
||
|
|
do, however, recommend that you systematically name any additional drives
|
||
|
|
that you create for a server. We suggest that you use the next available Linux device
|
||
|
|
name for each new drive. By default, Linux allocates the SCSI device names
|
||
|
|
/dev/sda and /dev/sdb to the system and installation drives, respectively.
|
||
|
|
Therefore, we recommand that you name the first additional storage space you
|
||
|
|
create for a server nwsd-namesdc, nwsd-namesdd, and so on. Using this naming
|
||
|
|
convention for an NWSD named REDHAT1, additional storage spaces would be named
|
||
|
|
REDHAT1SDC, REDHAT1SDD, and so on. Note that the maximum length of a storage
|
||
|
|
space name is 10 characters.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzau9mandrives.htm" title="This topic describes information and advice on how to manage iSeries disk storage allocated to integrated Linux servers.">Managing Linux drives</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|