10 More Discussions You Might Find Interesting
1. Ubuntu
I suddenly don't see my folders into /mnt/md0.
What can be reason?
mdadm --detail /dev/md*
/dev/md0:
Version : 1.2
Creation Time : Fri Jan 18 09:54:27 2019
Raid Level : raid1
Array Size : 1953383488 (1862.89 GiB 2000.26 GB)
Used Dev Size : 1953383488 (1862.89 GiB... (8 Replies)
Discussion started by: tomislav91
8 Replies
2. UNIX for Advanced & Expert Users
Currently I am using this laborious command
lvdisplay | awk '/LV Path/ {p=$3} /LV Name/ {n=$3} /VG Name/ {v=$3} /Block device/ {d=$3; sub(".*:", "/dev/dm-", d); printf "%s\t%s\t%s\n", p, "/dev/mapper/"v"-"n, d}'
Would like to know if there is any shorter method to get this mapping of... (2 Replies)
Discussion started by: royalibrahim
2 Replies
3. Solaris
Dear All ,
Pl find the below command ,
# raidctl -l
Controller: 1
Volume:c1t0d0
Disk: 0.0.0
Disk: 0.1.0
Disk: 0.3.0
#
raidctl -l c1t0d0
Volume Size Stripe Status Cache RAID
Sub Size ... (10 Replies)
Discussion started by: jegaraman
10 Replies
4. Red Hat
Good morning
Recently we needed to change the password from a redhat 6.5 system that no one knew the root password.
Starting the system with the init=/bin/bash method took us to the following scenario:
system_vg active with only root_lv and tmpfs mounted.
our entries at fstab are like... (1 Reply)
Discussion started by: Ikaro0
1 Replies
5. AIX
Hello,
I have a scsi pci x raid controller card on which I had created a disk array of 3 disks
when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk )
suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies
6. Solaris
I've just installed Sol 10 Update 9 on a Sun 4140 server and have a RAID 1 configuration (2 136 Gb drives) for the OS and have created a RAID 5 array (6 136 GB) drives. When i log into the system I am unable to see the RAID 5 disks at all. I've tried using the devfsadm command but no luck and... (9 Replies)
Discussion started by: goose25
9 Replies
7. Red Hat
Hi,
I had a doubt regarding device mapper notations and their corresponding LVM volumes.
I have configured a volume group with two logical volumes in it as root and swap.
The entries in the /etc/fstab file show the dm notations namely,
/dev/mapper/VolGroup00-LogVol01... (2 Replies)
Discussion started by: kanna_geekworkz
2 Replies
8. Red Hat
I have an HP blade with Qlogic HBA's connected to an EVA8000. I have downloaded the latest multipath.conf from HP's website. The drive presented to the server appears to be configured and working except the output of "multipath -l" shows for all paths. What is causing this output?
mpath0... (2 Replies)
Discussion started by: manzier
2 Replies
9. Solaris
Hi.
I need to move a 5 disk RAID5 array from a SE3310 box to a different SE3310 array. After installing the disks in the "new" StorEdge device, I "would like" ;) to be able have access to the data which is on the RAID.
Essentially, the quesion is, how can this be done? :confused:
I checked... (5 Replies)
Discussion started by: alexs77
5 Replies
10. Red Hat
We have a Red Hat linux server running on IBM x445 hardware. There are external disks in an IBM EXP300 disk enclosure. The system is running RAID 5. One of the four IBM disks (73.4 GB 10k FRU 06P5760) has become faulty. The system is still up and running OK because of the RAID. In that same EXP300... (3 Replies)
Discussion started by: pdudley
3 Replies
LVS(8) System Manager's Manual LVS(8)
NAME
lvs - report information about logical volumes
SYNOPSIS
lvs [--aligned] [-a|--all] [-d|--debug] [-h|-?|--help] [--ignorelockingfailure] [--ignoreskippedcluster] [--nameprefixes] [--noheadings]
[--nosuffix] [-o|--options [+]Field[,Field]] [-O|--sort [+|-]Key1[,[+|-]Key2[,...]]] [-P|--partial] [--rows] [--separator Separator]
[--segments] [--unbuffered] [--units hHbBsSkKmMgGtTpPeE] [--unquoted] [-v|--verbose] [--version] [VolumeGroupName [VolumeGroupName...]]
DESCRIPTION
lvs produces formatted output about logical volumes.
OPTIONS
See lvm(8) for common options.
--aligned
Use with --separator to align the output columns.
--all Include information in the output about internal Logical Volumes that are components of normally-accessible Logical Volumes, such as
mirrors, but which are not independently accessible (e.g. not mountable). The names of such Logical Volumes are enclosed within
square brackets in the output. For example, after creating a mirror using lvcreate -m1 --mirrorlog disk , this option will reveal
three internal Logical Volumes, with suffixes mimage_0, mimage_1, and mlog.
--nameprefixes
Add an "LVM2_" prefix plus the field name to the output. Useful with --noheadings to produce a list of field=value pairs that can
be used to set environment variables (for example, in udev(7) rules).
--noheadings
Suppress the headings line that is normally the first line of output. Useful if grepping the output.
--nosuffix
Suppress the suffix on output sizes. Use with --units (except h and H) if processing the output.
-o, --options
Comma-separated ordered list of columns. Precede the list with '+' to append to the default selection of columns instead of replac-
ing it.
Use -o lv_all to select all logical volume columns, and -o seg_all to select all logical volume segment columns.
Use -o help to view the full list of columns available.
Column names include: chunk_size, convert_lv, copy_percent, data_lv, devices, discards, lv_attr, lv_host, lv_kernel_major, lv_ker-
nel_minor, lv_kernel_read_ahead, lv_major, lv_minor, lv_name, lv_path, lv_profile, lv_read_ahead, lv_size, lv_tags, lv_time,
lv_uuid, metadata_lv, mirror_log, modules, move_pv, origin, origin_size, pool_lv, raid_max_recovery_rate, raid_min_recovery_rate,
raid_mismatch_count, raid_sync_action, raid_write_behind, region_size, segtype, seg_count, seg_pe_ranges, seg_size, seg_size_pe,
seg_start, seg_start_pe, seg_tags, snap_percent, stripes, stripe_size, sync_percent, thin_count, transaction_id, writebehind, zero.
With --segments, any "seg_" prefixes are optional; otherwise any "lv_" prefixes are optional. Columns mentioned in vgs(8) can also
be chosen.
The lv_attr bits are:
1 Volume type: (C)ache, (m)irrored, (M)irrored without initial sync, (o)rigin, (O)rigin with merging snapshot, (r)aid, (R)aid with-
out initial sync, (s)napshot, merging (S)napshot, (p)vmove, (v)irtual, mirror or raid (i)mage, mirror or raid (I)mage out-of-
sync, mirror (l)og device, under (c)onversion, thin (V)olume, (t)hin pool, (T)hin pool data, raid or pool m(e)tadata or pool
metadata spare.
2 Permissions: (w)riteable, (r)ead-only, (R)ead-only activation of non-read-only volume
3 Allocation policy: (a)nywhere, (c)ontiguous, (i)nherited, c(l)ing, (n)ormal This is capitalised if the volume is currently
locked against allocation changes, for example during pvmove(8).
4 fixed (m)inor
5 State: (a)ctive, (s)uspended, (I)nvalid snapshot, invalid (S)uspended snapshot, snapshot (m)erge failed, suspended snapshot
(M)erge failed, mapped (d)evice present without tables, mapped device present with (i)nactive table
6 device (o)pen
7 Target type: (m)irror, (r)aid, (s)napshot, (t)hin, (u)nknown, (v)irtual. This groups logical volumes related to the same kernel
target together. So, for example, mirror images, mirror logs as well as mirrors themselves appear as (m) if they use the origi-
nal device-mapper mirror kernel driver; whereas the raid equivalents using the md raid kernel driver all appear as (r). Snap-
shots using the original device-mapper driver appear as (s); whereas snapshots of thin volumes using the new thin provisioning
driver appear as (t).
8 Newly-allocated data blocks are overwritten with blocks of (z)eroes before use.
9 Volume Health: (p)artial, (r)efresh needed, (m)ismatches exist, (w)ritemostly. (p)artial signifies that one or more of the Phys-
ical Volumes this Logical Volume uses is missing from the system. (r)efresh signifies that one or more of the Physical Volumes
this RAID Logical Volume uses had suffered a write error. The write error could be due to a temporary failure of that Physical
Volume or an indication that it is failing. The device should be refreshed or replaced. (m)ismatches signifies that the RAID
logical volume has portions of the array that are not coherent. Inconsistencies are detected by initiating a "check" on a RAID
logical volume. (The scrubbing operations, "check" and "repair", can be performed on a RAID logical volume via the 'lvchange'
command.) (w)ritemostly signifies the devices in a RAID 1 logical volume that have been marked write-mostly.
10 s(k)ip activation: this volume is flagged to be skipped during activation.
-O, --sort
Comma-separated ordered list of columns to sort by. Replaces the default selection. Precede any column with '-' for a reverse sort
on that column.
--rows Output columns as rows.
--segments
Use default columns that emphasize segment information.
--separator Separator
String to use to separate each column. Useful if grepping the output.
--unbuffered
Produce output immediately without sorting or aligning the columns properly.
--units hHbBsSkKmMgGtTpPeE
All sizes are output in these units: (h)uman-readable, (b)ytes, (s)ectors, (k)ilobytes, (m)egabytes, (g)igabytes, (t)erabytes,
(p)etabytes, (e)xabytes. Capitalise to use multiples of 1000 (S.I.) instead of 1024. Can also specify custom units e.g. --units 3M
--unquoted
When used with --nameprefixes, output values in the field=value pairs are not quoted.
SEE ALSO
lvm(8), lvdisplay(8), pvs(8), vgs(8)
Sistina Software UK LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26) LVS(8)