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
raidreconf(8) System Manager's Manual raidreconf(8)
NAME
raidreconf - reconfigure RAID arrays
SYNOPSIS
raidreconf -h {--help}
- or -
raidreconf -V {--version}
- or -
raidreconf -o oldraidtab -n newraidtab -m /dev/md?
- or -
raidreconf -i /dev/sd?? -n newraidtab -m /dev/md?
- or -
raidreconf -n newraidtab -m /dev/md? -e /dev/sd??
WARNING
You should back up all data BEFORE any attempt is made to reconfigure a RAID device. YOU HAVE BEEN WARNED.
The author will give you no guarantee whatsoever, that this program works in any specific way at all. It may well destroy all data on any
device connected directly, indirectly, or not at all, to any system this software is used on. Please use this stuff with care, if you
decide to use it at all.
Ok, that said, let's see how to actually use it :-)
DESCRIPTION
raidreconf will read two raidtab files, an old one, and a new one. It will then re-build your old array to match the configuration for the
new array, while retaining all data possible.
It can also be used to import a single block-device into a RAID array (using more block devices), or export a RAID array to a single block-
device.
raidreconf can, of course, only retain your original data if you grow the configuration. If you shrink the configuration from say, P bytes
to Q bytes, raidreconf will retain the first Q bytes of your original data, but everything from Q bytes to the end of the old array (to P
bytes) will be lost.
Currently raidreconf can grow and shrink RAID-0 and RAID-5 arrays, and import non-RAID devices into a new RAID-0 or RAID-5.
The whole purpose of raidreconf is to be able to add disks to an existing array, or convert it to a new type (eg. RAID-0 to RAID-5) without
losing data. raidreconf will move the existing data around on your array, to match the layout of the new array.
OPTIONS
-h {--help}
Raidreconf will print a short help message, and exit.
-V {--verbose}
Raidreconf will print it's version information, and exit.
-o {--old} oldraidtab
Specifies the path name of the old (current) raidtab. NOTE: raidreconf performs some tests to ensure that this configuration file
matches the raid superblocks stored on the disk, but there may be scenarios where the two are in conflict, but aren't detected as
such. Be very careful to specify this file properly.
-n {--new} newraidtab
Specifies the path name of the new raidtab. After raidreconf finishes, copy the newraidtab to the oldraidtab location, as
raidreconf doesn't perform this (potentially dangerous) operation.
-m {--mddev} /dev/md?
Specifies the name of the raid array to modify.
-i {--import} /dev/sd??
Specifies the name of the device to import from.
-e {--export} /dev/sd??
Specifies the name of the device to export to.
BUGS
Perhaps many. Well, the basic RAID-0 growth, shrink and import algorithms seem to work, but there are lots and lots of consistency checks
and graceful error handling missing.
The RAID-5 algorithms are simplistic, with little optimization other than that provided by the buffer layer. Conversions between non-RAID,
RAID-0, and RAID-5 all *seem* to work, but there may be some bugs left yet.
If an error occurs during reconfiguration, a power failure for example, restore from backup (you DID make a backup, right?), and try again.
Although RAID-4 is not supported, and almost no one uses it, it would be almost trivial to add.
REPORTING BUGS
Since this is highly experimental software, there are a number of known bugs already. The author would of course like to know about bugs,
but at this stage in development you shouldn't waste too much of your time trying to hunt them down. They're probably known, and maybe
already fixed in the author's tree.
Report bugs to <bugs@oss.connex.com>. ?????
AUTHOR
raidreconf was written in 1999 by Jakob Oestergaard <jakob@ostenfeld.dk>
The RAID-5 routines were written by Daniel S. Cox in 2001 <dcox@connex.com>
SEE ALSO
mkraid(8), raidtab(5), raidstart(8), raidhotadd(8), raidhotremove(8), raidstop(8)
raidreconf(8)