What does the noparity mean in vol status vol0?

To save space the vol0 volume has been created without parity. We suggest you don’t perform any disk fails of the root volume...

It isn't possible to create new volumes without parity as this requires special versions of the simulator that aren't suitable for anything other than Network Appliance internal use. If you are really restricted on disk space then add more disks to the vol0 volume and use that for your tests using the setup.sh script.

It is possible to convert the vol0 volume into a normal RAID 4 style volume through the following advanced procedure:

Check to see how many disks you will need. If your root volume isn't called vol0 then substitute the name of your root volume as appropriate:

sim> vol status -r vol0
Volume vol0 (online, raid0) (block checksums)
  Plex /vol0/plex0 (online, normal, active)
    RAID group /vol0/plex0/rg0 (normal)

      RAID Disk Device  HA    SHELF BAY CHAN  Used (MB/blks)    Phys (MB/blks)
      --------- ------  --------------- ----  --------------    --------------
      data      v0.0    v0    0     0   FC:A  120/246784        126/259200
sim>

In this example we have a single disk and it's size is 126MB. For a RAID 4 volume we'll need 2 disks of at least 126MB in size.

Halt the simulator and create new disks to migrate the vol0 data onto.

sim> halt

CIFS local server is shutting down...

CIFS local server has shut down...
Fri Nov 28 11:22:00 GMT [kern.shutdown:notice]: System shut down because : "halt".
linux:/sim # ./setup.sh

Script version 14 (13/Nov/2003)
Loading defaults. Run with -i option to ignore defaults
Please ensure the simulator is not running.
Regenerate MAC address? [no]:
Use DHCP on first boot? [yes]:
Ask for floppy boot? [no]:
Would you like the memory page hack applied? [yes]:
Which network interface should the simulator use? [default]:
How much memory would you like the simulator to use? [512]:
Create a new log for each session? [no]:
Overwrite the single log each time? [yes]:
Your simulator has 1 disks. How many more would you like to add? [0]: 2

The following disk types are available in MB:
        Real (Usable)
  a -   43   ( 14)
  b -   62   ( 30)
  c -   78   ( 45)
  d -  129   ( 90)
  e -  535   (450)
  f - 1024   (900)
What disk size would you like to use? [a]: d
Disk adapter to put disks on? [0]:
Adding 2 additional disk(s).
Creating ,disks/v0.1:NETAPP__:VD-100MB-FZ-520_:61163201:259200
Creating ,disks/v0.2:NETAPP__:VD-100MB-FZ-520_:61163302:259200
Shelf file Shelf:DiskShelf14 updated
Complete. From the simulator directory run runsim.sh to start the simulator.
linux:/sim # ./runsim.sh
[the simulator restarts]

Create a new volume.

sim> vol create newvol0 2
Creation of a volume with 2 disks has been initiated.  The disks need
to be zeroed before addition to the volume. The process has been initiated
and you will be notified via the system log as disks are added.
sim> Fri Nov 28 11:30:12 GMT [raid.disk.zero.done:notice]: Disk /v0.2 Shelf 0 Bay 2 [NETAPP   VD-100MB-FZ-520  0042] S/N [61163302] : disk zeroing complete
Fri Nov 28 11:30:15 GMT [raid.disk.zero.done:notice]: Disk /v0.1 Shelf 0 Bay 1 [NETAPP   VD-100MB-FZ-520  0042] S/N [61163201] : disk zeroing complete
Fri Nov 28 11:30:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /newvol0/plex0/rg0/v0.2 Shelf 0 Bay 2 [NETAPP   VD-100MB-FZ-520  0042] S/N [61163302] to volume newvol0 has completed successfully
Fri Nov 28 11:30:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /newvol0/plex0/rg0/v0.1 Shelf 0 Bay 1 [NETAPP   VD-100MB-FZ-520  0042] S/N [61163201] to volume newvol0 has completed successfully
Fri Nov 28 11:30:17 GMT [raid.rg.spares.low:warning]: /newvol0/plex0/rg0
Fri Nov 28 11:30:17 GMT [config_async_0:notice]: Volume newvol0 has been added to the system.

Use vol copy to create a copy of your existing vol0 configuration and data.

sim> vol restrict newvol0
Fri Nov 28 11:45:01 GMT [config_async_0:notice]: CIFS - disabled for volume newvol0
Volume newvol0 is now restricted.
sim> vol copy start vol0 newvol0
This can be a long-running operation. Use Control - C (^C) to interrupt.
Copy Volume: vol0 on machine 127.0.0.1 to Volume: newvol0
VOLCOPY DUMP: creating "/vol/vol0/../snapshot_for_volcopy.0" snapshot.
VOLCOPY: Starting on volume 1.
11:45:04 GMT : vol copy restore 0 : begun, 61 MB to be copied.
11:45:10 GMT : vol copy restore 0 : 5 % done. Estimate 3 minutes remaining.
[snip]
11:47:53 GMT : vol copy restore 0 : 95 % done. Estimate 1 minutes remaining.
VOLCOPY DUMP: Deleting "/vol/vol0/../snapshot_for_volcopy.0" snapshot.
11:48:05 GMT : vol copy restore 0 : 100% done, 61 MB copied.
sim>

Make this new volume the root volume and reboot the simulator.

sim> vol online newvol0
Volume 'newvol0' is now online.
sim> vol options newvol0 root
Fri Nov 28 12:08:45 GMT [fmmbx_instanceWorke:info]: Disk v0.0 removed from primary mailbox set
Fri Nov 28 12:08:45 GMT [fmmbx_instanceWorke:info]: Disk v0.2 is a primary mailbox disk
Fri Nov 28 12:08:45 GMT [fmmbx_instanceWorke:info]: Disk v0.1 is a primary mailbox disk
volume newvol0 will become root volume at the next boot.
sim> reboot
[snip lots of rebooting information]

Take the existing root volume off line and delete it.

sim> vol offline vol0
Fri Nov 28 12:39:38 GMT [config_async_0:notice]: CIFS - disabled for volume vol0
Share HOME disabled while volume vol0 is offline.
Volume 'vol0' is now offline.
sim> vol destroy vol0
Are you sure you want to destroy this volume? yes
Fri Nov 28 12:39:44 GMT [raid.config.vol.destroyed:info]: Volume 'vol0' destroyed.
Share HOME removed when volume vol0 destroyed.
Volume 'vol0' destroyed.
sim> vol rename newvol0 vol0
newvol0 renamed to vol0

The old disk(s) are now marked as spares. If you want to delete them to recover space follow these instructions. If you had any shares/exports on your old vol0 volume then you may need to re-create them.