search for: mkraid

Consider this section: http://www.tldp.org/HOWTO/Software-RAID-HOWTO-4.html#ss4.14 I have not done this before and I'm leary about Step 11 which is resizing the filesystem after doing a mkraid command. This howto lacks any ext3 documentation. Some questions I have are: 1. Should I convert back to ext2 on all my filesystems before I do a mkraid? 2. If I leave the system at ext3, will the mkraid conflict with the journal? Is resize2fs even neccessary now-a-days? 3. If so, in the future,...

...aidtab the machine boots ok and lists all the raid-1 devices I set up in the install (including the /boot partition) but there is no raidtab file. I tried using dmraid to take a look at the software RAID setup but it reports "No Software Raid" So my question is "what happened to mkraid commands and stuff like /etc/raidtab", /proc/mdstat reports fine... P.

...and B of the array. So we have a list of devices under /proc/partitions mapping what we are expecting to see , for example the devices /dev/sdd1 (A) and /dev/sdx1 (B ) would form a raid 0 device under linux to make a file system slightly under 1TB. This file system was created using the older mkraid utils at the time but has been in production for over a year. This node and the array unfortunately had a power outage and the resulting problem faced by us is the following. The raid start up fails with as it cannot find a device /dev/sdai1 . This device is not part of the /etc/raidtab but is...

...couldn't convice the box that it should boot from the motherboard, but that's another story. But I hope, that this isn't causing the problem. As I am a Linux beginner, I can't really tell you what version of raid software the box is using. If I run raid0run -V it tells me "mkraid version 0.90.0" and if I run raidstart -V it says "raidstart v0.3d compiled for md raidtools-1.00.3". Hmmm.... However, whenever I run Samba together with the raid, the clients (Win XP SVP2) do hang after a few minutes. In the middle of a copy process they tell me "Disk is fu...

...dc 00 06 CL1G 04:1b OPEN-9 00040898 /dev/sdh c6 00 07 CL2G 04:1c OPEN-9 00040898 /dev/sdp dc 00 07 CL1G 04:1c OPEN-9 00040898 from here: would I fdisk the devices, then create the raidtab file, then mkraid, then add them to create the ocfs filesystem, then mount then, then add them to the fstab and it's done? Is this even supported? The main reason for all of this is that I see a couple of conflicting comments on this: don't use raid or lvm on RAC? or yes you can? Any insights? Thanks.

When a new system CentOS-4.4 is built the swap partition is always reversed... Note md3 below, the raidtab is OK, I have tried various raid commands to correct. swapoff -a raidstop /dev/md3 mkraid /dev/md3 --really-force swapon -a And then I get a proper ourput for /proc/mdstat, but when I reboot /proc/mdstat again reads as below, with md3 [0] [1] reversed. [root]# cat /proc/mdstat Personalities : [raid1] md3 : active raid1 hda3[0] hdc3[1] 1000320 blocks [2/2] [UU] md1 : active rai...

I've read through the archives and it looks like people are using ext3 with software RAID with at least some success. I just want to confirm that it works properly. If I convert my md RAID 0 to ext3, should I expect A) A fast journalled filesystem, or B) Wailing and gnashing of teeth My RAID currently does not use persistant superblocks, because I created it many moons ago under the old

Hello all, I've got CentOS 5.2 installed on an old Pentium III server. The server is used by a club at my school, and they are rapidly running out of room on the internal IDE drives that are configured in software RAID 1. I have a Silicon Image SATA controller in the server, and I was planning on adding two more SATA hard drives to the computer. Is there a GUI like Disk Druid for

With Centos3, fedora1/2 I have been able to put /boot on a RAID1 partition and have it boot normally. Unlike earlier versions that used lilo as the default boot loader, these did not make the 2nd drive bootable but at least I was fairly confident that if the first drive failed I could use the install CD in rescue mode to fix up the 2nd one and go on. However, Centos4 won't boot at all with

...-size 8 device /dev/sda1 failed-disk 0 device /dev/sdb1 raid-disk 1 ... repeated for each partition. Marking the partitions on sda - our source drive - as failed BEFORE creating the raid array is very important as it prevents them from being overwritten by mkraid. Create the RAID disks now. # for i in ''seq 0 3''; do mkraid /dev/md$i; done Format and mount the root and boot partitions and initialise swap: # mkfs.ext3 /dev/md0 # mkfs.ext3 /dev/md1 # mkswap /dev/md2 # mkdir /target # mount /dev/md1 /target # mkdir /target/boot # mount /dev...