Solstice DiskSuite 4.2.1 User's Guide

Creating File Systems on Metadevices

This section describes how to create a new file system on a metadevice.

Preliminary Information for Creating File Systems on Metadevices

How to Create a File System on a Metadevice (File System Manager)

This task assumes you have installed Solstice Storage Manager on the host you are working with, and that you have launched the Storage Manager application. For more information, see Appendix A, Using Storage Manager.

  1. Make sure you have met the prerequisites ("Prerequisites for Creating DiskSuite Objects") and have read the preliminary information ("Preliminary Information for Creating File Systems on Metadevices").

  2. Start File System Manager.

    If you have appropriately configured DiskSuite Tool, select File System Manager from the DiskSuite Tool "Tools" menu.

    If you have not configured DiskSuite Tool as such, you must first launch Storage Manager from the Solstice Launcher.


    Note -

    To configure DiskSuite to work with Storage Manager, refer to "How to Enable DiskSuite to Launch Storage Manager (Command Line)".


  3. Within the File System Manager main window, select Create from the Object menu, then select File System to display the Property Book for a new file system.

  4. Click Device in the Property Viewer portion of the window.

  5. Select and drag a metadevice from DiskSuite Tool's Metadevice Editor window to the Device Name text field.

  6. Click Apply.

    File System Manager begins building the new file system on the metadevice.

How to Create a File System on a Metadevice (Command Line)

After checking the prerequisites ("Prerequisites for Creating DiskSuite Objects"), and the preliminary information ("Preliminary Information for Creating File Systems on Metadevices"), use the newfs(1M) command to create a new file system on a metadevice. Refer to the newfs(1M) man page for more information.

Example -- Creating a File System on a Concatenation


# newfs /dev/md/rdsk/d3
newfs: construct a new file system /dev/md/rdsk/d3: (y/n)? y
/dev/md/rdsk/d3:        917280 sectors in 1638 cylinders of 7 tracks, 80 sectors
        447.9MB in 103 cyl groups (16 c/g, 4.38MB/g, 2112 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
 32, 9072, 18112, 27152, 36192, 45232, 54272, 63312, 71712, 80752, 89792,
 98832, 107872, 116912, 125952, 134992, 143392, 152432, 161472, 170512, 179552,
 188592, 197632, 206672, 215072, 224112, 233152, 242192, 251232, 260272,
 269312, 278352, 286752, 295792, 304832, 313872, 322912, 331952, 340992,
 350032, 358432, 367472, 376512, 385552, 394592, 403632, 412672, 421712,
 430112, 439152, 448192, 457232, 466272, 475312, 484352, 493392, 501792,
 510832, 519872, 528912, 537952, 546992, 556032, 565072, 573472, 582512,
 591552, 600592, 609632, 618672, 627712, 636752, 645152, 654192, 663232,
 672272, 681312, 690352, 699392, 708432, 716832, 725872, 734912, 743952,
 752992, 762032, 771072, 780112, 788512, 797552, 806592, 815632, 824672,
 833712, 842752, 851792, 860192, 869232, 878272, 887312, 896352, 905392,
 914432,
# fsck /dev/md/rdsk/d3
** /dev/md/rdsk/d3
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
2 files, 9 used, 942654 free (14 frags, 117830 blocks,  0.0% fragmentation)

This example creates a file system on a concatenation named d3. The fsck(1M) command verifies the new file system.

Example -- Creating a File System on a Concatenation Within a Diskset


# newfs /dev/md/relo-red/rdsk/d33
newfs: construct a new file system /dev/md/relo-red/rdsk/d33: (y/n)? y
/dev/md/relo-red/rdsk/d33:        917280 sectors in 1638 cylinders of 7 tracks,
80 sectors
        447.9MB in 103 cyl groups (16 c/g, 4.38MB/g, 2112 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
 32, 9072, 18112, 27152, 36192, 45232, 54272, 63312, 71712, 80752, 89792,
 98832, 107872, 116912, 125952, 134992, 143392, 152432, 161472, 170512, 179552,
 188592, 197632, 206672, 215072, 224112, 233152, 242192, 251232, 260272,
 269312, 278352, 286752, 295792, 304832, 313872, 322912, 331952, 340992,
 350032, 358432, 367472, 376512, 385552, 394592, 403632, 412672, 421712,
 430112, 439152, 448192, 457232, 466272, 475312, 484352, 493392, 501792,
 510832, 519872, 528912, 537952, 546992, 556032, 565072, 573472, 582512,
 591552, 600592, 609632, 618672, 627712, 636752, 645152, 654192, 663232,
 672272, 681312, 690352, 699392, 708432, 716832, 725872, 734912, 743952,
 752992, 762032, 771072, 780112, 788512, 797552, 806592, 815632, 824672,
 833712, 842752, 851792, 860192, 869232, 878272, 887312, 896352, 905392,
 914432,

This example creates a file system on a concatenation name d33 in diskset relo-red.


Note -

A file system that resides on a metadevice in a diskset cannot be automatically mounted at boot via the /etc/vfstab file. The necessary diskset RPC daemons (rpc.metad and rpc.metamhd) do not start early enough in the boot process to permit this. Additionally, the ownership of a diskset is lost during a reboot.


Where to Go From Here

If You Want to Make the File System Available ... 

Then ... 

Now 

Mount the file system with the mount(1M) command, specifying the metadevice name as the mount device, such as /dev/md/dsk/d30.

Automatically when the system boots 

Create or modify the file system's entry in /etc/vfstab file, using the metadevice block and raw device names.

As a shared (exported) resource

Create a file system entry in the /etc/dfs/dfstab file.