I created a zpool and two ZFS volumes in OpenSolaris. I would like both ZFS volumes to be exportable. However, I don't know how to set that up.
These are the steps I did:
1) Create the zpool using raidz1 across five disks.
I have six disks and created a zpool across 5 of them. c4t0d0... (3 Replies)
I created a zpool and zfs filesystem in OpenSolaris. I made two NFS mount points:
> zpool history
History for 'raidpool':
2009-01-15.17:12:48 zpool create -f raidpool raidz1 c4t1d0 c4t2d0 c4t3d0 c4t4d0 c4t5d0
2009-01-15.17:15:54 zfs create -o mountpoint=/vol01 -o sharenfs=on -o... (0 Replies)
Hi Folks,
Looking for info here more than any actual HowTo, does anyone know if there is an actual way of converting a Veritas or UFS filesystem to ZFS leaving the resident data intact.
All that I have been able to find, including the commercial products seem to require the FS backed up from... (1 Reply)
Dear all,
We are facing prolem when we are going to mount AIX filesystem, the system returned the following error
0506-307The AFopen call failed
: A file or directory in the path name does not exist.
But when we ls filesystems in the /etc/ directory it show
-rw-r--r-- 0 root ... (2 Replies)
Hi,
Recently we have new server T5 Oracle. We set up it for our database. For out database files we set one zfs filesystem. When i use iostat -xc the output as below. As you see the value for vdc4 is quite high.
extended device statistics cpu
device ... (32 Replies)
Hello,
Need to ask the question regarding extending the zfs storage file system.
currently after using the command, df -kh
u01-data-pool/data 600G 552 48G 93% /data
/data are only 48 gb remaining and it has occupied 93% for total storage.
zpool u01-data-pool has more then 200 gb... (14 Replies)
I have a esxi 6.7 server running a Solaris 10 x86 vm (actually a bunch of them). The VM uses zfs for the pools (of course). I expand the underlying ESX logical disk, for example from 50GB to 100gb, then I set autoexpand=on <pool> that belongs to the esx logical disk.
what am i missing to... (2 Replies)
Discussion started by: mrmurdock
2 Replies
LEARN ABOUT NETBSD
mlxctl
MLXCTL(8) BSD System Manager's Manual MLXCTL(8)NAME
mlxctl -- Mylex DAC960 family management utility
SYNOPSIS
mlxctl [-f dev] [-v] [-a] status [drive] [...]
mlxctl [-f dev] [-a] detach [drive] [...]
mlxctl [-f dev] [-a] check [drive] [...]
mlxctl [-f dev] rebuild channel:target
mlxctl [-f dev] cstatus
mlxctl [-f dev] rescan
mlxctl [-f dev] config
DESCRIPTION
The mlxctl utility performs status monitoring and management functions for Mylex DAC960 RAID controllers and attached devices.
The following options are available:
-a Apply the action to all drives attached to the controller.
-f dev Specify the control device to use. The default is /dev/mlx0.
-v Increased verbosity.
The following commands are available:
cstatus Display the controller's current status.
status Display the status of the specified drives. This command returns 0 if all drives tested are online, 1 if one or more drives are
critical and 2 if one or more are offline.
rescan Re-scan the logical drive table, and attach or detach devices from the system as necessary.
detach Detach the specified drives. Drives must be unmounted and unopened for this command to succeed.
check Initiate a consistency check and repair pass on a drive that provides redundancy (e.g., RAID1 or RAID5). This command returns imme-
diately. The status command can be used to monitor the progress of the check.
rebuild Rebuild onto the specified physical drive. Note that there can be only one running rebuild operation per controller at any given
time. This command returns immediately. The cstatus command can be used to monitor the progress of the rebuild.
config Write the current system drive configuration to stdout.
EXAMPLES
Display the status of drive ld3 attached to the controller mlx1:
mlxctl -f /dev/mlx1 -v status ld3
SEE ALSO ld(4), mlx(4)HISTORY
The mlxctl command first appeared in NetBSD 1.5.3, and was based on the mlxcontrol utility found in FreeBSD.
BUGS
Modifying drive configuration is not yet supported.
Some commands do not work with older firmware revisions.
Error log extraction is not yet supported.
BSD April 10, 2000 BSD