LINUX.IE, website of the Irish Linux Users' Group
Tux rules!

   
Home
New Users
Articles
Download
Projects
Community
Vendors

  Print Version
 
Archives:


planetILUG

Recent News

News Archive


Join the
ILUG
on FaceBook


Join the
ILUG
on LinkedIn


Join the
ILUG SETI
Group



















 
 :: Mailing Lists

[ILUG] mdadm confusion

[ILUG] mdadm confusion

Niall O Broin niall at linux.ie
Thu Aug 11 09:07:31 IST 2005


I have just converted (read - reinstalled) an Amanda server box from 
sarge (pre stable) to Ubuntu hoary (why not just just update the box? - 
simply trying to cut down on the number of Linux variants running in 
the one place) and all is cool and froody with the exception of the 
600GB RAID5 array which is used for the actual backups. The data, 
touching large chunks of trees, is fine, but mdadm, or the md layer, 
seems a tad confused. There is ONE RAID array in the box yet  cat 
/proc/mdstat shows me this

Personalities : [raid5]
md1 : active raid5 hdf[0] hdh[2] hdg[1]
       597445440 blocks level 5, 64k chunk, algorithm 2 [4/3] [UUU_]

md0 : active raid5 hde1[0] hdh1[3] hdg1[2] hdf1[1]
       597376512 blocks level 5, 128k chunk, algorithm 2 [4/4] [UUUU]

unused devices: <none>

fdisk -l shows me the four component physical disks, each of which is 
one big partition, and then shows me this:

Disk /dev/md0: 611.7 GB, 611713548288 bytes
2 heads, 4 sectors/track, 149344128 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md0 doesn't contain a valid partition table

Disk /dev/md1: 611.7 GB, 611784130560 bytes
255 heads, 63 sectors/track, 74378 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

     Device Boot      Start         End      Blocks   Id  System
/dev/md1p1               1       24790   199125643+  fd  Linux raid 
autodetect

What I am used to seeing is /dev/md0, with no partition table i.e. the 
filesystem created on the RAID device. I have no idea what the system 
thinks md1 is (well, I know what it thinks it is, but I'd don't know 
where it got the idea) and WTF is /dev/md1p1 - there is no such device 
file.

ps -ef|grep md shows me, inter alia,

root      2603     1  7 00:14 ?        00:46:51 [md0_raid5]
root      2641     1  0 00:14 ?        00:00:00 [md1_raid5]

and I guess md1_raid5 shouldn't be there, though I'm reluctant to 
simply kill it.

I suspect I could fix this by creating an mdadm config file, but mdadm 
should work quite happily without a config file.

Ideas?




More information about the ILUG mailing list
Read this without the formatting.
                                                                                                    

 

Hosted by HEAnet


Maintained by the ILUG website team. The aim of Linux.ie is to support and help commercial and private users of Linux in Ireland. You can display ILUG news in your own webpages, read backend information to find out how. Networking services kindly provided by HEAnet, server kindly donated by Dell. Linux is a trademark of Linus Torvalds, used with permission. No penguins were harmed in the production or maintenance of this highly praised website. Looking for the Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
RSS Version
Powered by Dell