Sponsored Content
Full Discussion: Unable to remove VIOS disk
Operating Systems AIX Unable to remove VIOS disk Post 302923791 by ibmtech on Tuesday 4th of November 2014 12:57:15 PM
Old 11-04-2014
Ok,
Have you tried varyoffvg patchtest?

If that doesn't varyoff, then you have to look into each vhost and their backing device and compare it with lsvg -l `lsvg` output.

If you see some devices from patchtest VG remove them.
This User Gave Thanks to ibmtech For This Post:
 

9 More Discussions You Might Find Interesting

1. Linux

Unable to remove file using rm: Disk space is full

Hi all, My disk space is 100% full. df -k <dir> -> 100% One of my debug files consume huge amount of space and i want to remove the same to start off fresh debugs. However i'm unable to remove the file giving out the following error message: rm -f debug.out22621 rm: cannot remove... (8 Replies)
Discussion started by: Pankajakshan
8 Replies

2. AIX

Problem mapping LUN disk from VIOS to the LPAR

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

3. Solaris

Unable to take backup of /var on another disk !!

Hi Gurus, I have to back the /var to other disk, however I am unable to do so. What I did is Created a partition on another disk, placed file system on the slice and mounted on /mnt . Issued following command #ufsdump 0cfu /mnt /var And I am getting... (2 Replies)
Discussion started by: kumarmani
2 Replies

4. Ubuntu

Unable to mount disk

I am running Ubuntu Server, I recently added a new hard drive to the machine When I run fdisk -l I see both drives. The recently added drive is present but it's listed as extended. when I try to mount the drive it says you must specify the file system type. I can't mount this drive, I was... (2 Replies)
Discussion started by: NelsonC
2 Replies

5. AIX

VIOS IP address - separate vlan for vios servers ?

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

6. AIX

Shared Disk in VIOS between two LPARs ?

is there any way to create shared virtual disk between two LPARs like how you can do it using Storage through Fiber on two servers ? Trying to stimulate HACMP between two LPARs (1 Reply)
Discussion started by: filosophizer
1 Replies

7. Solaris

Solved: Disk Unable to Boot

Update: The / file system (/dev/rdsk/c1t0d0s0) is being checked fsck unable to stat WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0). Root password for system maintenance (control-d to bypass): I am unable to hit control-d to by pass. I... (50 Replies)
Discussion started by: br1an
50 Replies

8. AIX

VIOS: Extend virtual disk assigned to running lpar?

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

9. UNIX for Advanced & Expert Users

Unable to install client AIX LPAR to vscsi hdisk provided from VIOS

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
LOSETUP(8)						       System Administration							LOSETUP(8)

NAME
losetup - set up and control loop devices SYNOPSIS
Get info: losetup [loopdev] losetup -l [-a] losetup -j file [-o offset] Detach a loop device: losetup -d loopdev... Detach all associated loop devices: losetup -D Set up a loop device: losetup [-o offset] [--sizelimit size] [--sector-size size] [-Pr] [--show] -f|loopdev file Resize a loop device: losetup -c loopdev DESCRIPTION
losetup is used to associate loop devices with regular files or block devices, to detach loop devices, and to query the status of a loop device. If only the loopdev argument is given, the status of the corresponding loop device is shown. If no option is given, all loop devices are shown. Note that the old output format (i.e., losetup -a) with comma-delimited strings is deprecated in favour of the --list output format. It's possible to create more independent loop devices for the same backing file. This setup may be dangerous, can cause data loss, corrup- tion and overwrites. Use --nooverlap with --find during setup to avoid this problem. OPTIONS
The size and offset arguments may be followed by the multiplicative suffixes KiB (=1024), MiB (=1024*1024), and so on for GiB, TiB, PiB, EiB, ZiB and YiB (the "iB" is optional, e.g., "K" has the same meaning as "KiB") or the suffixes KB (=1000), MB (=1000*1000), and so on for GB, TB, PB, EB, ZB and YB. -a, --all Show the status of all loop devices. Note that not all information is accessible for non-root users. See also --list. The old output format (as printed without --list) is deprecated. -d, --detach loopdev... Detach the file or device associated with the specified loop device(s). Note that since Linux v3.7 kernel uses "lazy device destruc- tion". The detach operation does not return EBUSY error anymore if device is actively used by system, but it is marked by autoclear flag and destroyed later. -D, --detach-all Detach all associated loop devices. -f, --find [file] Find the first unused loop device. If a file argument is present, use the found device as loop device. Otherwise, just print its name. --show Display the name of the assigned loop device if the -f option and a file argument are present. -L, --nooverlap Check for conflicts between loop devices to avoid situation when the same backing file is shared between more loop devices. If the file is already used by another device then re-use the device rather than a new one. The option makes sense only with --find. -j, --associated file [-o offset] Show the status of all loop devices associated with the given file. -o, --offset offset The data start is moved offset bytes into the specified file or device. --sizelimit size The data end is set to no more than size bytes after the data start. -b, --sector-size size Set the logical sector size of the loop device in bytes (since Linux 4.14). The option may be used when create a new loop device as well as stand-alone command to modify sector size of the already existing loop device. -c, --set-capacity loopdev Force the loop driver to reread the size of the file associated with the specified loop device. -P, --partscan Force the kernel to scan the partition table on a newly created loop device. -r, --read-only Set up a read-only loop device. --direct-io[=on|off] Enable or disable direct I/O for the backing file. The optional argument can be either on or off. If the argument is omitted, it defaults to on. -v, --verbose Verbose mode. -l, --list If a loop device or the -a option is specified, print the default columns for either the specified loop device or all loop devices; the default is to print info about all devices. See also --output, --noheadings, --raw, and --json. -O, --output column[,column]... Specify the columns that are to be printed for the --list output. Use --help to get a list of all supported columns. -n, --noheadings Don't print headings for --list output format. --raw Use the raw --list output format. -J, --json Use JSON format for --list output. -V, --version Display version information and exit. -h, --help Display help text and exit. ENCRYPTION
Cryptoloop is no longer supported in favor of dm-crypt. For more details see cryptsetup(8). RETURN VALUE
losetup returns 0 on success, nonzero on failure. When losetup displays the status of a loop device, it returns 1 if the device is not configured and 2 if an error occurred which prevented determining the status of the device. FILES
/dev/loop[0..N] loop block devices /dev/loop-control loop control device EXAMPLE
The following commands can be used as an example of using the loop device. # dd if=/dev/zero of=~/file.img bs=1024k count=10 # losetup --find --show ~/file.img /dev/loop0 # mkfs -t ext2 /dev/loop0 # mount /dev/loop0 /mnt ... # umount /dev/loop0 # losetup --detach /dev/loop0 ENVIRONMENT
LOOPDEV_DEBUG=all enables debug output. AUTHORS
Karel Zak <kzak@redhat.com>, based on the original version from Theodore Ts'o <tytso@athena.mit.edu> AVAILABILITY
The losetup command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/. util-linux November 2015 LOSETUP(8)
All times are GMT -4. The time now is 01:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy