04-09-2011
in that case it, of course, not necessary
but what flexible in the raid when there's no raid?
10 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. 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
5. 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
6. 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
7. 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
8. 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
9. 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
10. 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
DM(4) BSD Kernel Interfaces Manual DM(4)
NAME
dm -- Device-mapper disk driver
SYNOPSIS
pseudo-device dm
DESCRIPTION
The dm driver provides the capability of creating one or more virtual disks based on the target mapping.
This document assumes that you're familiar with how to generate kernels, how to properly configure disks and pseudo-devices in a kernel con-
figuration file, and how to partition disks. This driver is used by the Linux lvm2tools to create and manage lvm in NetBSD.
Currently, the linear, zero, and error targets are implemented. Each component partition should be offset at least 2 sectors from the begin-
ning of the component disk. This avoids potential conflicts between the component disk's disklabel and dm's disklabel. In i386 it is offset
by 65 sectors, where 63 sectors are the initial boot sectors and 2 sectors are used for the disklabel which is set to be read-only.
In order to compile in support for dm, you must add a line similar to the following to your kernel configuration file:
pseudo-device dm #device-mapper disk device
dm may create linear mapped devices, zero, and error block devices. Zero and error block devices are used mostly for testing. Linear
devices are used to create virtual disks with linearly mapped virtual blocks to blocks on real disk. dm Device-mapper devices are controlled
through the /dev/mapper/control device. For controlling this device ioctl(2) calls are used. For the implementation of the communication
channel, the proplib(3) library is used. The protocol channel is defined as a proplib dictionary with needed values. For more details, look
at sys/dev/dm/netbsd-dm.h. Before any device can be used, every device-mapper disk device must be initialized. For initialization one line
must be passed to the kernel driver in the form of a proplib dictionary. Every device can have more than one table active. An example for
such a line is:
0 10240 linear /dev/wd1a 384
dm The first parameter is the start sector for the table defined with this line, the second is the length in sectors which is described with
this table. The third parameter is the target name. All other parts of this line depend on the chosen target. dm For the linear target,
there are two additional parameters: The first parameter describes the disk device to which the device-mapper disk is mapped. The second
parameter is the offset on this disk from the start of the disk/partition.
SEE ALSO
config(1), proplib(3), MAKEDEV(8), dmsetup(8), fsck(8), lvm(8), mount(8), newfs(8)
HISTORY
The device-mapper disk driver first appeared in NetBSD 6.0.
AUTHORS
Adam Hamsik <haad@NetBSD.org> implemented the device-mapper driver for NetBSD.
Brett Lymn <blymn@NetBSD.org>,
Reinoud Zandijk <reinoud@NetBSD.org>, and
Bill Stouder-Studenmund <wrstuden@NetBSD.org> provided guidance and answered questions about the NetBSD implementation.
BUGS
This driver is still work-in-progress--there can be bugs.
BSD
August 30, 2008 BSD