search for: md12

Hi All, I am trying to create an MD device. I am using the command: /sbin/mdadm --create --a /dev/md12 --level=1 --run --raid-devices=2 /dev/sda12 /dev/sdb12 to create the device, and to dynamically create the device file if needed. What I want is the device file to be created as /dev/md12, but with the -a flag it creates it as /dev/md<first unwsed minor number>. I have tried various options...

...md0 91M 22M 65M 25% /boot /dev/md6 277M 8.1M 254M 4% /tmp /dev/md7 1.8G 1.3G 595M 69% /usr /dev/md8 938M 761M 177M 82% /var /dev/md9 9.2G 2.6G 6.1G 30% /home /dev/md10 11G 2.1G 8.7G 19% /scratch /dev/md12 56G 43G 13G 77% /global The /usr and /var filesystems keep switching to ro mode following the detection of errors. This has been happening on a daily basis since switching to ext3 (usually the /var switches, /usr has done it once). I suppose my first question should be: do ext3...

...292672 blocks [2/2] [UU] md7 : active raid1 hdk6[1] hde6[0] 1952896 blocks [2/2] [UU] md8 : active raid1 hdk7[1] hde7[0] 976640 blocks [2/2] [UU] md9 : active raid1 hdk8[1] hde8[0] 9765376 blocks [2/2] [UU] md10 : active raid0 hdk9[1] hde9[0] 12108800 blocks 4k chunks md12 : active raid5 hdk3[3] hde3[2] hdc2[1] hda2[0] 59978304 blocks level 5, 32k chunk, algorithm 2 [4/4] [UUUU] md11 : active raid1 hdk4[1] hde4[0] 170240 blocks [2/2] [UU] Now, the filesystems are set-up as shown: jlm@nijinsky:~$ df -h Filesystem Size Used Avail Use% Mounted...

...have it mounted while system-startup. Do I have to specify the external journal device in fstab or does the partition find its journal device by itself? If the first, ho should I specify it? I created the journal with mke2fs /dev/md22 -O journal_dev and the ext3 filesystem with mke2fs -j /dev/md12 -J device=/dev/md22. Thanks again, Norman Schmidt. -- -- Norman Schmidt Universitaet Erlangen-Nuernberg _ cand.chem. Sysadmin Wohnheimnetzwerk RatNET _ // mailto:schmidt@naa.net \X/

...md0 91M 22M 65M 25% /boot /dev/md6 277M 8.1M 254M 4% /tmp /dev/md7 1.8G 1.3G 595M 69% /usr /dev/md8 938M 761M 177M 82% /var /dev/md9 9.2G 2.6G 6.1G 30% /home /dev/md10 11G 2.1G 8.7G 19% /scratch /dev/md12 56G 43G 13G 77% /global The /usr and /var filesystems keep switching to ro mode following the detection of errors. This has been happening on a daily basis since switching to ext3 (usually the /var switches, /usr has done it once). I suppose my first question should be: do ext3...

I have been trying to delete an md. I have recently updated to version 1.12 of mdadm. I used to be able to do mdadm ,dev. --stop. It does not seem to be stopping, but I do not get any error and the $?/return code is 0. The --verbose option for mdadm does nothing for --stop. How do I determine why this is not successful? Thanks...Art

Hello, Sorry to sound like a bad record, but I'm trying to figure out why I'm getting "Bad gzip magic numbers" errors when ISOlinux is trying to inflate the kernel. Right now I'm clueless as to what's wrong. I've tried various kernels compiled on a few different platforms. Has anyone ever seen this before? ANyone know where a better forum to ask this question