I'm still concerned that your business application might be running on the VIOS. It kind of can, but it's really not designed for it. Do you not have virtual guests for you business application? Are you sure you have the right /usr that needs to be extended? On a VIOS, ordinarily there would never be a need to extend it.
If you business application really is running on the VIOS, then an upgrade to the VIOS might destroy it. The VIOS only care about making sure the VIOS is working properly and sharing devices to the guests where the real business applications should run.
Hi,
I am getting an error message when i try to increase the size of a filesystems
under AIX 4.3.3:
chfs: 0506-932 Can not extend a JFS file system with nbpi = 4096
and frag = 4096 past 134217728 (512 byte blocks).
-> Characteristics Journaled File System
... (4 Replies)
Hi,
Has anyone ever encountered the following scenario:
I am working on a SUN server with solaris 10 installed and veritas managing the filesystem. One of the file systems has become full:
df -kh /ossrc/dbdumps
Filesystem size used avail capacity Mounted on... (6 Replies)
Hi,
The solaris filesystem /u01 shows available space as 100GB, and used space as 6 GB.
The Problem is when iam trying to install some software or copy some files in this file system /u01 Iam unable to copy or install in this file system due to lack of space.
ofcourse the software... (31 Replies)
Hi All,
I have Solaris-10 configured with two non-global zones. All file-systems are mounted on global zone and data file-systems are mounted on non-global zone as lofs.
I have added 4 luns of 100 GB each and still not able to extend a file-system. This is production server, so I can not... (5 Replies)
Hi All
I want to extend this file system to 120Gb:
df -h /xyz
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d80 98G 35G 62G 37% /xyzand the NetApp admin is going to give me an LUN with 22Gb.
This file system is mounted on:
metastat d80... (1 Reply)
Would some help me on this below
I am trying to extend file system on AIX and however unable to extend the file system.
0516-306 extendvg: Unable to find physical volume 20 in the Device
Configuration Database.
0516-321 extendvg: Physical volume u01-lv is not configured.
0516-792... (15 Replies)
Dear Expret,
Help me about my issue,
I trying add new disk to volume Group but error:
step add new disk to volume group.
1. ~Change a Volume Group
Add a Physical Volume to a Volume Group
Remove a Physical Volume from a Volume Group
Reorganize a Volume Group... (6 Replies)
Hi
I have the following cenario:
I have requested a LUN from the NetApp to create a file system, and the netapp admin provide me with one as you can see below, but after following all the steps, I could not create a file system on the device:
# format
Searching for disks...done
... (11 Replies)
Hi all.
I have a Logical volume that I can't extend, with this error message:
server171:root:/root# lvextend -L +1024M -v /dev/aplic_vg/siteminderwa_lv
Finding volume group aplic_vg
Archiving volume group "aplic_vg" metadata (seqno 75).
Extending logical volume siteminderwa_lv to... (0 Replies)
Discussion started by: Gabriander
0 Replies
LEARN ABOUT MOJAVE
platform::shell
platform::shell(n) Tcl Bundled Packages platform::shell(n)
__________________________________________________________________________________________________________________________________________________NAME
platform::shell - System identification support code and utilities
SYNOPSIS
package require platform::shell ?1.1.4?
platform::shell::generic shell
platform::shell::identify shell
platform::shell::platform shell
_________________________________________________________________DESCRIPTION
The platform::shell package provides several utility commands useful for the identification of the architecture of a specific Tcl shell.
This package allows the identification of the architecture of a specific Tcl shell different from the shell running the package. The only
requirement is that the other shell (identified by its path), is actually executable on the current machine.
While for most platform this means that the architecture of the interrogated shell is identical to the architecture of the running shell
this is not generally true. A counter example are all platforms which have 32 and 64 bit variants and where a 64bit system is able to run
32bit code. For these running and interrogated shell may have different 32/64 bit settings and thus different identifiers.
For applications like a code repository it is important to identify the architecture of the shell which will actually run the installed
packages, versus the architecture of the shell running the repository software.
COMMANDS
platform::shell::identify shell
This command does the same identification as platform::identify, for the specified Tcl shell, in contrast to the running shell.
platform::shell::generic shell
This command does the same identification as platform::generic, for the specified Tcl shell, in contrast to the running shell.
platform::shell::platform shell
This command returns the contents of tcl_platform(platform) for the specified Tcl shell.
KEYWORDS
operating system, cpu architecture, platform, architecture
platform::shell 1.1.4 platform::shell(n)