| In addition to the basic UFS, there are two variants, logging
UFS (LUFS) and the metatrans UFS. All three versions
share the same basic code that blocks allocation, directory management,
and data organization. In particular, all current versions of
UFS have a nominal maximum file system size of 1 terabyte (the
limit will be raised to 16 terabytes in the Solaris 10 OS). Obviously,
a single file stored in any of them must fit inside a file system,
so the maximum size file is slightly smaller, about 1009 gigabytes
out of a 1024 gigabyte file system. There is no reasonable limit
to the number of file systems that can be built on a single system;
systems have been run with over 2880 UFS file systems.
Whereas UFS and VxFS are hosted on a single disk resource, QFS
can be hosted on multiple disk resources. In this context, a disk
resource is anything that presents the appearance of a single
virtual disk. This could be a LUN exported out of a disk array,
a slice of a directly attached disk drive, or some synthesis of
one or more of these created by a volume manager such as VxVM or
Solaris Volume Manager software. The main point is that there are
limits to virtual disk resources. In particular, a 1 terabyte maximum
size exists when the file system is hosted on a single disk resource,
and it is necessarily limited to the size of that resource.
QFS essentially includes a volume manager in its inner core. A
QFS file system is hosted on top of disk groups. (Do not confuse
these with the completely unrelated VxVM concept of the same name.)
A QFS disk group is a collection of disk resources that QFS binds
together internally.
There are two types of disk group: round-robin and striped. The
striped disk group is effectively the same thing as a RAID-0 of
the underlying disk resources. Blocks are logically disbursed across
each of the constituent disk resources according to a RAID-0 organization.
One might use this configuration to maximize the available I/O
bandwidth from a given underlying storage configuration.
SAMFS is something of a confusing term. Strictly speaking, it
refers to a local file system that is strongly related to QFS/local.
More specifically, it is functionally the same as QFS/local, except
that it does not offer the ability to place user data and metadata
on separate devices. In my opinion, there is so little difference
between QFS/local and SAMFS that they can be treated together as
QFS/local.
/dev/dsk/c0t0d0s3 swap
/dev/dsk/c0t0d0s0 / ufs
/dev/dsk/c0t0d0s5 /usr ufs
/dev/dsk/c0t0d0s1 /var ufs
/dev/dsk/c0t0d0s4 /opt ufs
/dev/dsk/c0t0d0s6 /db ufs
swap /tmp tmpfs
/dev/dsk/c0t2d0s7 /image ufs
Disk 1 Volume name = < > ascii name = <ST320011A
cyl 38790 alt 2 hd 16 sec 63> pcyl = 38792 ncyl = 38790 acyl
= 2 nhead = 16 nsect = 63 Part Tag Flag Cylinders Size Blocks 0
root wm 2 - 306 150.12MB (305/0/0) 307440 1 var wm 307 - 2338 1000.12MB
(2032/0/0) 2048256 2 backup wm 0 - 38789 18.64GB (38790/0/0) 39100320
3 swap wm 2339 - 6500 2.00GB (4162/0/0) 4195296 4 usr wm 6501 -
9548 1.47GB (3048/0/0) 3072384 5 usr wm 9549 - 12596 1.47GB (3048/0/0)
3072384 6 usr wm 12597 - 38789 12.59GB (26193/0/0) 26402544 7 unassigned
wm 0 - 1 0.98MB (2/0/0) 2016
Disk 2 Volume name = < > ascii
name = <ST3120022A cyl 57459 alt 2 hd 16 sec 255> pcyl =
57461 ncyl = 57459 acyl = 2 nhead = 16 nsect = 255 Part Tag Flag
Cylinders Size Blocks 0 unassigned wm 0 0 (0/0/0) 0 1 unassigned
wm 0 0 (0/0/0) 0 2 backup wu 0 - 57458 111.79GB (57459/0/0) 234432720
3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned
wm 0 0 (0/0/0) 0 6 unassigned wm 0 0 (0/0/0) 0 7 unassigned wm
0 - 57458 111.79GB (57459/0/0) 234432720
|
