zxmaus: thanks, but these commands are not what I meant. At least according to my findings.
Some of my systems have lots of LUN-s, used for various purposes:
* used as PV-s in some VG-s (mostly rootvg)
* used as GPFS NSD backing devices
* used as Oracle ASM data disks
and some more.
Your commands can show relevant info only for LUNS used as PV disks, but they are misleading on other cases.
Now I can try to run
and see if it can put the device into DEFINED state. When the device is open, I get an error and the device state is kept unchanged. But I would like to find a way to obtain the same info without modifying the system. By the way, how does rmdev find this info?
Hi i need help pls ...
Server type sun fire 3800 I need to install solaris 9 .
When i boot the system i recieve the following :
System Controller 'sunfire3800':
Type 0 for Platform Shell
Type 1 for domain A console
Type 2 for domain B console
Type 3 for... (5 Replies)
I have a real emergency. I have a Sun Fire V240 UltraSparc server and am connected via the Serial Mgmnt Port with a Laptop. I have been building an Oracle database on it for the past couple months, not getting very far along with it , when suddenly, the system had a fatal crash. I've lost the... (2 Replies)
I've a Sun V440 machine, and it's running solaris 10 .. for some reason i need to install a fresh copy of solaris 10. for that i've prepared solaris 10 dvd but surprisingly i found there is no any dvd rom on this machine, so i've took a dvd rom from a V240 machine and inserted on V440.
after... (3 Replies)
Hi guys,
I had a solaris box, with veritas controled disk.
1 disc is showing soft errors, how can I repair the soft errors?
Please help.
Cheers; (4 Replies)
Hi All,
Could anyone please help to resolve the below problem.
I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error.
I spent 2 days for the above and go through with several suggestion found by googling. But no luck.
... (0 Replies)
Hi all,
I am not sure whether anyone of you using XIV to copy vg from one host to another. After I managed to copy all the respective vg over to destination vg, and map all vg to destination and when come to varyonvg, I got the following error
0516-510 varyonvg: Physical volume not found for... (2 Replies)
I installed a new hard drive completely blank.
sun blade 150
openboot 4.10.6
message:
Boot device: disk:a File and args:
Bad magic number in disk label
Can't open label package
Evaluating:
Can't open boot device (15 Replies)
Hello Forum,
I'm really in a fix now,
I'm getting this error message now, seems like the boot block is damaged?
When I do probe-all the system freezes...
Can any one guide me as what to do next?
System is Solaris 8 running Open Boot PROM 4
System also does not have a cd/dvd rom drive...
... (17 Replies)
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
LEARN ABOUT CENTOS
losetup
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]
Delete loop:
losetup -d loopdev...
Delete all used loop devices:
losetup -D
Print name of first unused loop device:
losetup -f
Setup loop device:
losetup [-o offset] [--sizelimit size]
[-p pfd] [-rP] {-f[--show]|loopdev} file
Resize 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.
Note that the old output format (e.g. losetup -a) with comma delimited strings is deprecated in favour of the --list output format (e.g.
losetup -a -l).
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 status of all loop devices. Note that not all information are accessible for non-root users. See also --list. The old output
format (as printed without --list) is deprecated.
-c, --set-capacity loopdev
force loop driver to reread size of the file associated with the specified loop device
-d, --detach loopdev...
detach the file or device associated with the specified loop device(s)
-D, --detach-all
detach all associated loop devices
-f, --find
find the first unused loop device. If a file argument is present, use this device. Otherwise, print its name
-h, --help
print help
-j, --associated file
show status of all loop devices associated with given file
-l, --list
if a loop device or the -a option is specified, print default columns for either the specified loop device or all loop devices,
default is to print info about all devices.
-o, --offset offset
the data start is moved offset bytes into the specified file or device
-O, --output columns
specify which columns are to be printed for the --list output
--sizelimit size
the data end is set to no more than size bytes after the data start
-P, --partscan
force kernel to scan partition table on newly created loop device
-r, --read-only
setup read-only loop device
--show print device name if the -f option and a file argument are present.
-v, --verbose
verbose mode
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 con-
figured and 2 if an error occurred which prevented from determining the status of the device.
FILES
/dev/loop[0..N]
loop block devices
/dev/loop-cotrol
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=1MiB 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
AUTHORS
Karel Zak <kzak@redhat.com>, based on 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 ftp://ftp.kernel.org/pub/linux/utils/util-linux/.
util-linux July 2003 LOSETUP(8)