One of my zone is stuck in down state, not able to boot it or halt it .. not even detach .. is there any way to recover without rebooting the whole system ( global zone ) ? (3 Replies)
Hi All,
I'm preparing to migrate some servers from vscsi to pass-thru NPIV. I am planning to have the SAN team move the exact LUNs from vio1/vio2 to those two VWWN through NPIV.
My question is on the partition itself.. right now, let's say I have hdisk0/1/2/3/4 that are part of datavg. They... (2 Replies)
Hi,
I want to change from vscsi to npiv. Is it possible to use both on the same adapter, so we can change the systems one by one, or must we place a second FC adapter in the VIO servers?
Thanks,
Ronald (2 Replies)
Hello,
I have a VIOS System and would like to do mapping some hdisks, hdisk160 until hdisk165 to a vSCSi Adapter. I try to do this in the oem_setup_env like the following:
for i in $(lspv | grep hdisk* | awk {'print $1'};
do
mkdev -V $i -p vhost20
done
There where a mapping with... (4 Replies)
If you're familiar with vscsi mappings thru a VIO Server, you are probably aware, on an AIX 6.1 Client LPAR, that:
print cvai | kdbcan provide useful information to you.... like VIO Server name & vhost #. But, "cvai" does not appear to be part of the Kernel Debugger in AIX 5.3.
My question is... (3 Replies)
Hello,
When I assigned CDROM from IVM (VIOS) to LPAR and then running cfgmgr i get the following message on the client lpar
#cfgmgr
cfgmgr: 0514-621 WARNING: The following device packages are required for device support but are not currently installed.
devices.vscsi.disk
searching... (0 Replies)
Hi everybody,
I have Power5 server with 4 internal hdisks each of 70Gb.
VIOS server was installed via Virtual I/O Server Image Repository on the HMC.
HMC release - 7.7.0
VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies
LEARN ABOUT FREEBSD
zfsloader
ZFSLOADER(8) BSD System Manager's Manual ZFSLOADER(8)NAME
zfsloader -- kernel bootstrapping final stage
DESCRIPTION
zfsloader is an extended variant of loader(8) with added support for booting from ZFS. This document describes only differences from
loader(8).
ZFS FEATURES
zfsloader supports the following format for specifying ZFS filesystems which can be used wherever loader(8) refers to a device specification:
zfs:pool/filesystem:
where pool/filesystem is a ZFS filesystem name as described in zfs(8).
If /etc/fstab does not have an entry for the root filesystem and vfs.root.mountfrom is not set, but currdev refers to a ZFS filesystem, then
zfsloader will instruct kernel to use that filesystem as the root filesystem.
ZFS COMMAND EXTENSIONS
lsdev [-v]
Lists ZFS pools in addition to disks and partitions. Adding -v shows more ZFS pool details in a format that resembles zpool status
output.
lszfs filesystem
A ZFS extended command that can be used to explore the ZFS filesystem hierarchy in a pool. Lists the immediate children of the
filesystem. The filesystem hierarchy is rooted at a filesystem with the same name as the pool.
FILES
/boot/zfsloader zfsloader itself.
EXAMPLES
Set the default device used for loading a kernel from a ZFS filesystem:
set currdev=zfs:tank/ROOT/knowngood:
SEE ALSO gptzfsboot(8), loader(8), zfs(8), zfsboot(8), zfsloader(8), zpool(8)HISTORY
The zfsloader first appeared in FreeBSD 7.3.
AUTHORS
This manual page was written by Andriy Gapon <avg@FreeBSD.org>.
BSD September 15, 2014 BSD