LinuxQuestions.org - problems create fs on raid5 device

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - problems create fs on raid5 device (https://www.linuxquestions.org/questions/linux-general-1/problems-create-fs-on-raid5-device-4175450259/)

problems create fs on raid5 device

Hi There,
I am trying to create file system on my new raid5 device but after while it hangs on:

Writing superblocks and filesystem accounting information:

some details:
the command i've used
mkfs.ext3 -v -m .1 -b 4096 -E stride=128,stripe-width=2304 /dev/md0

mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Wed Feb 13 15:06:39 2013
Raid Level : raid5
Array Size : 9001838592 (8584.82 GiB 9217.88 GB)
Used Dev Size : 500102144 (476.93 GiB 512.10 GB)
Raid Devices : 19
Total Devices : 20
Persistence : Superblock is persistent

Update Time : Fri Feb 15 15:38:08 2013
State : clean
Active Devices : 19
Working Devices : 20
Failed Devices : 0
Spare Devices : 1

Layout : left-symmetric
Chunk Size : 512K

Name : sandy2:0 (local to host sandy2)
UUID : 9e313caa:c33e5d9c:e56f7848:b0c67189
Events : 52

Number Major Minor RaidDevice State
0 8 33 0 active sync /dev/sdc1
1 8 49 1 active sync /dev/sdd1
2 8 65 2 active sync /dev/sde1
3 8 81 3 active sync /dev/sdf1
4 8 97 4 active sync /dev/sdg1
5 8 113 5 active sync /dev/sdh1
6 8 129 6 active sync /dev/sdi1
7 8 145 7 active sync /dev/sdj1
8 8 161 8 active sync /dev/sdk1
9 8 177 9 active sync /dev/sdl1
10 8 193 10 active sync /dev/sdm1
11 8 209 11 active sync /dev/sdn1
12 8 225 12 active sync /dev/sdo1
13 8 241 13 active sync /dev/sdp1
14 65 1 14 active sync /dev/sdq1
15 65 17 15 active sync /dev/sdr1
16 65 33 16 active sync /dev/sds1
17 65 49 17 active sync /dev/sdt1
20 65 65 18 active sync /dev/sdu1

19 8 17 - spare /dev/sdb1

i have tried with mkfs.ext4, mke2fs as well but the result was the same.
any ideas what could be wrong ?
Thx!
SK

Which os, version and system do you use. All looks well what gives cat /proc/mdstat when you format the array and iostat 10.

OS: Scientific Linux release 6.3 (Carbon), 2.6.32-279.el6.x86_64; supermicro 4047R-7JRFT
i will let you know about the output from iostat 10 and cat /proc/mstat in few days since i am doing some simulations right now on this node.
SK

It looks like /dev/md0 is the raid device, not the partition. What is the output of "fdisk -l"?

Quote:

Originally Posted by suicidaleggroll (Post 4893013)

It looks like /dev/md0 is the raid device, not the partition. What is the output of "fdisk -l"?

You can put a filesystem on a raid device.

Code:

root@dimmel:~# mdadm --detail /dev/md0

/dev/md0:

        Version : 0.90

  Creation Time : Mon Aug 13 22:11:31 2012

    Raid Level : raid10

    Array Size : 524160 (511.96 MiB 536.74 MB)

  Used Dev Size : 262080 (255.98 MiB 268.37 MB)

  Raid Devices : 4

  Total Devices : 4

Preferred Minor : 0

    Persistence : Superblock is persistent



  Intent Bitmap : Internal



    Update Time : Sat Feb 16 22:19:53 2013

          State : active 

 Active Devices : 4

Working Devices : 4

 Failed Devices : 0

  Spare Devices : 0



        Layout : far=2

    Chunk Size : 32K



          UUID : 5fc08dc9:45be61b5:950f9dea:d7ce0e55

        Events : 0.31



    Number  Major  Minor  RaidDevice State

      0      8        4        0      active sync  /dev/sda4

      1      8      20        1      active sync  /dev/sdb4

      2      8      36        2      active sync  /dev/sdc4

      3      8      52        3      active sync  /dev/sdd4

root@dimmel:~# df /dev/md0

Filesystem    1K-blocks  Used Available Use% Mounted on

/dev/md0          507720 459176    22336  96% /

Quote:

Originally Posted by whizje (Post 4893236)

You can put a filesystem on a raid device.

My mistake, I spend a lot more time with hardware RAID than software.

cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sdc1[0] sdb1[19](S) sdu1[20] sdt1[17] sds1[16] sdr1[15] sdq1[14] sdp1[13] sdo1[12] sdn1[11] sdm1[10] sdl1[9] sdk1[8] sdj1[7] sdi1[6] sdh1[5] sdg1[4] sdf1[3] sde1[2] sdd1[1]
9001838592 blocks super 1.2 level 5, 512k chunk, algorithm 2 [19/19] [UUUUUUUUUUUUUUUUUUU]

unused devices: <none>

iostat 10
Linux 2.6.32-279.el6.x86_64 (sandy2) 02/17/2013 _x86_64_ (32 CPU)

avg-cpu: %user %nice %system %iowait %steal %idle
71.65 0.00 0.68 0.03 0.00 27.64

Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
sdb 0.00 0.01 0.00 2082 26
sdc 739.70 8028.47 46.04 1728113392 9910572
sdk 747.05 8028.26 45.95 1728068548 9890364
sdj 745.21 8028.22 45.91 1728060054 9881396
sdh 744.81 8028.34 45.99 1728085920 9899828
sdm 747.68 8028.29 45.93 1728076266 9885460
sdd 741.42 8028.55 46.18 1728131440 9939092
sdp 753.17 8028.31 45.92 1728079130 9883468
sdn 749.92 8028.29 45.92 1728076014 9883716
sde 739.55 8028.28 45.92 1728072616 9885196
sdg 742.78 8028.36 45.93 1728089520 9886980
sdf 741.33 8028.34 45.96 1728085534 9893260
sdi 742.99 8028.30 45.98 1728076742 9897204
sdo 751.55 8028.33 45.90 1728084804 9880156
sdl 749.22 8028.24 45.94 1728065300 9889260
sdq 752.14 8028.40 45.93 1728098164 9886404
sdr 753.51 8028.55 45.99 1728131434 9898324
sdu 754.73 8028.49 45.96 1728119028 9892620
sds 754.70 8028.55 45.99 1728132054 9899012
sdt 755.58 8028.51 45.98 1728123712 9897500
sda 0.38 13.03 23.24 2805226 5003104
md0 101.46 0.00 811.68 856 174712672

avg-cpu: %user %nice %system %iowait %steal %idle
0.00 0.00 0.01 3.13 0.00 96.86

Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
sdb 0.00 0.00 0.00 0 0
sdc 0.00 0.00 0.00 0 0
sdk 0.00 0.00 0.00 0 0
sdj 0.00 0.00 0.00 0 0
sdh 0.00 0.00 0.00 0 0
sdm 0.00 0.00 0.00 0 0
sdd 0.00 0.00 0.00 0 0
sdp 0.00 0.00 0.00 0 0
sdn 0.00 0.00 0.00 0 0
sde 0.00 0.00 0.00 0 0
sdg 0.00 0.00 0.00 0 0
sdf 0.00 0.00 0.00 0 0
sdi 0.00 0.00 0.00 0 0
sdo 0.00 0.00 0.00 0 0
sdl 0.00 0.00 0.00 0 0
sdq 0.00 0.00 0.00 0 0
sdr 0.00 0.00 0.00 0 0
sdu 0.00 0.00 0.00 0 0
sds 0.00 0.00 0.00 0 0
sdt 0.00 0.00 0.00 0 0
sda 0.30 0.00 3.20 0 32
md0 0.00 0.00 0.00 0 0

^Z
[2]+ Stopped iostat 10

Is this the iostat while performing a format of the array?

a bit after it get stack unfortunately. iostat gives some statistics in the beginning and then get to the current state which is when the sda is working only I guess?

Seems best to subscribe to the linux-raid mailinglist and ask there, there are the experts. You can subscribe by sending a mail to majordomo@vger.kernel.org with in the body "subscribe linux-raid"