[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#660258: md truncates devices





Package: linux-image-2.6.32-5-amd64
Version: 2.6.32-41


I have got a 32T raid0 md device (with 2.6.32-39):

failure:/home/thuthu# mdadm --detail /dev/md200
/dev/md200:
        Version : 0.90
  Creation Time : Tue Dec 14 09:59:58 2010
     Raid Level : raid0
     Array Size : 35093139072 (33467.43 GiB 35935.37 GB)
   Raid Devices : 3
  Total Devices : 3
Preferred Minor : 200
    Persistence : Superblock is persistent

    Update Time : Tue Dec 14 09:59:58 2010
          State : clean
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0

     Chunk Size : 64K

           UUID : db733d82:63962b6c:9d4deba6:47ca997f
         Events : 0.1

    Number   Major   Minor   RaidDevice State
       0       8        3        0      active sync   /dev/sda3
       1       8       19        1      active sync   /dev/sdb3
       2       8       35        2      active sync   /dev/sdc3

failure:/home/thuthu# cat /proc/partitions
major minor  #blocks  name

   8        0 11718684672 sda
   8        1   10484736 sda1
   8        2   10485760 sda2
   8        3 11697713135 sda3
   8        4        992 sda4
   8       16 11718684672 sdb
   8       17   10484736 sdb1
   8       18   10485760 sdb2
   8       19 11697713135 sdb3
   8       20        992 sdb4
   8       32 11718684672 sdc
   8       33   10484736 sdc1
   8       34   10485760 sdc2
   8       35 11697713135 sdc3
   8       36        992 sdc4
   9      200 35093139072 md200






after upgrade to 6.0.4 (2.6.32-41) 3*4T :


failure:/home/thuthu# cat /proc/partitions
major minor  #blocks  name

   8        0 11718684672 sda
   8        1   10484736 sda1
   8        2   10485760 sda2
   8        3 11697713135 sda3
   8        4        992 sda4
   8       16 11718684672 sdb
   8       17   10484736 sdb1
   8       18   10485760 sdb2
   8       19 11697713135 sdb3
   8       20        992 sdb4
   8       32 11718684672 sdc
   8       33   10484736 sdc1
   8       34   10485760 sdc2
   8       35 11697713135 sdc3
   8       36        992 sdc4
   9      200 12884901696 md200


Feb  9 02:24:41 failure kernel: [    7.412198] md: bind<sdb3>
Feb  9 02:24:41 failure kernel: [    7.412498] md: bind<sdc3>
Feb  9 02:24:41 failure kernel: [    7.412779] md: bind<sda3>
Feb  9 02:24:41 failure kernel: [    7.414642] raid0: looking at sda3
Feb  9 02:24:41 failure kernel: [    7.414703] raid0:   comparing sda3(8589934464)
Feb  9 02:24:41 failure kernel: [    7.414742]  with sda3(8589934464)
Feb  9 02:24:41 failure kernel: [    7.414837] raid0:   END
Feb  9 02:24:41 failure kernel: [    7.414887] raid0:   ==> UNIQUE
Feb  9 02:24:41 failure kernel: [    7.414938] raid0: 1 zones
Feb  9 02:24:41 failure kernel: [    7.414988] raid0: looking at sdc3
Feb  9 02:24:41 failure kernel: [    7.415040] raid0:   comparing sdc3(8589934464)
Feb  9 02:24:41 failure kernel: [    7.415079]  with sda3(8589934464)
Feb  9 02:24:41 failure kernel: [    7.415174] raid0:   EQUAL
Feb  9 02:24:41 failure kernel: [    7.415224] raid0: looking at sdb3
Feb  9 02:24:41 failure kernel: [    7.415276] raid0:   comparing sdb3(8589934464)
Feb  9 02:24:41 failure kernel: [    7.415315]  with sda3(8589934464)
Feb  9 02:24:41 failure kernel: [    7.415411] raid0:   EQUAL
Feb  9 02:24:41 failure kernel: [    7.415461] raid0: FINAL 1 zones
Feb  9 02:24:41 failure kernel: [    7.415514] raid0: done.
Feb  9 02:24:41 failure kernel: [    7.415563] raid0 : md_size is 25769803392 sectors.
Feb 9 02:24:41 failure kernel: [ 7.415618] ******* md200 configuration *********



Imre Simon



Reply to: