10 More Discussions You Might Find Interesting
1. AIX
need to confirm:
we have a system with two VIOs each serving a partition on a local disk to a client LPAR. That client LPAR has them both in a VG which is mirrored (exact). So each disk has a copy of the client LV that the client VG supports. This is the setup that was bequeathed to us by the... (3 Replies)
Discussion started by: maraixadm
3 Replies
2. Solaris
Hi all,
Is there anyway i can control the naming of the disk device ?
I have added an iscsi disk on server1 using iscsiadm , devfsadm and it is now showing as
/dev/dsk/c2t0d0 in node1
However, i am worried that the same disk will appear as
/dev/dsk/cXtXd0 in node2
This iscsi disk(lun)... (0 Replies)
Discussion started by: javanoob
0 Replies
3. AIX
Hello,
I am unable to remove the disk, whenever i remove the disk using
rmdev -dl hdisk2
or
rmdev -Rdl hdisk2
the disk appears back when i run
cfgmgr
but unable to create any volume group on it
# mkvg -y foovg hdisk2
0516-008 /usr/sbin/mkvg: LVM system call returned an unknown
... (20 Replies)
Discussion started by: filosophizer
20 Replies
4. AIX
Hello,
VIOS 2.2.1.4 using IVM.
I'm trying to extend a virtual disk assigned to a running lpar so that I can expand the lpar's datavg and grow some filesystems for the user.
Storage admin expanded the lun and new size was reflected in VIO right away. I then needed the storage pool to... (2 Replies)
Discussion started by: j_aix
2 Replies
5. AIX
Hi Folks,
I am working on a task - Cloning the OS from fullSystem partition to 3 new LPAR's using alt_disk_install.
I just wanted to clarify my steps here.
1. alt_disk_install -CBO hdisk1 and rename it to alt1
2. alt_disk_install -CBO hdisk2 and rename it to alt2
3. alt_disk_install... (4 Replies)
Discussion started by: snchaudhari2
4 Replies
6. AIX
Hello Everyone,
i got a question in AIX. How can i track the communication between LPARs.
i mean how can we find if a program/account trying to access a directory/file inside AIX LPAR or from another LPAR ?
if some one is trying to access our LPAR. where can i track those info? or a outside... (5 Replies)
Discussion started by: System Admin 77
5 Replies
7. AIX
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies
8. HP-UX
Hello people.
I need to shared a disk between two virtuals hosts in the same Guest, and I don't see any help about this.
I'm working on HP-UX 11.31
Thanks to all.:b: (2 Replies)
Discussion started by: cegamboav
2 Replies
9. AIX
Hello guys,
It would be so nice of you if someone can provide me with these informations.
1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Discussion started by: solaix14
3 Replies
10. AIX
Hello
I am doing a HACMP set-up using AiX e-server p5 series. The very basic requirement for the set-up is Shared disk storage like Fast-T and the related hardware. But because of lack of this hardware I want to use the simulated shared disk environment which is implemented using Network Block... (0 Replies)
Discussion started by: kul_sharvari
0 Replies
MKFATIMAGE16(1) Make HDIMAGE for DOSEMU MKFATIMAGE16(1)
NAME
mkfatimage16 - generate a virtual drive image suitable for DOSEMU
SYNOPSIS
mkfatimage16 [ -b bsectfile ] [{ -t tracks | -k Kbytes }] [ -l volume-label ] [ -f outfile ] [ -p ] [ file... ]
DESCRIPTION
mkfatimage16 creates a hdimage file for DOSEMU that is pre-loaded with the files specified on the command line. The output is either writ-
ten to stdout (hence do not forget to append " > hdimagefile", else you will see garbage on the screen) or to the file specified by the -f
option. For the latter you may also use option -p in order to force padding up to the given size. This padding will result in so-called
holes on an ext2-FS, hence the actual disk usage will not be greater. The file created by mkfatimage16 then can be used as a virtual
drive, when defined in /etc/dosemu.conf. As long as -k is not given, the number of heads is always 4 and you have 17 sectors per head else
it is adjusted accordingly. To vary the size, you may either use the -t option or specify the total amount of Kbytes via -k option.
All files given behind the options will be copied onto the hdimage. In addition a DOSEMU suitable master boot record (MBR) is established
and via option -b you may specify a boot sector that gets inserted as first sector of the partition. To later access the hdimage outside of
DOSEMU you should use mtools (/etc/mtools.conf parameters partition=1 and offset=128).
OPTIONS
-b file
Insert the first 512 bytes of file into the bootsector of the partition.
-t num Make the virtual disk have num tracks. This is the one way to define the size of the disk.
-k Kbytes
Make the virtual disk be Kbytes in size. Using -t and -k are mutual exclusive.
-l label
insert label as volume label for the disk.
-f outfile
The hdimage is written to outfile instead of stdout
-p Pad the hdimage with zero up to the total size given by -t or -k (only in conjunction with -f).
AUTHOR
Pasi Eronen (pe@iki.fi) and Peter Wainwright.
BUGS
This program doesn't support name mangling and does very little checking for non-DOS filenames. Disk full condition isn't detected (and
probably causes erratic behaviour). Duplicate files aren't detected.
AVAILABILITY
Comes with DOSEMU
SEE ALSO
dosemu(1), xdosemu(1), mtools(1)
Version ALPHA 0.98 September, 1998 MKFATIMAGE16(1)