Re: processes hung in D (raid5/dm/ext3)

From: foo
Date: Tue Jun 15 2004 - 21:18:54 EST


On Tue, Jun 15, 2004 at 04:26:07PM -0700, Andrew Morton wrote:
> Other than that, the chances of getting this fixed are proportional to your
> skill in finding us a way of reproducing it. A good start would be to tell
> us exactly which commands were used to set up the LVM and the raid array.
> That way a raid/LVM ignoramus like me can take a look ;)
>

In case any of this is of interest...

# cat /proc/mdstat
Personalities : [raid1] [raid5]
md0 : active raid5 sde1[4] sdd1[3] sdc1[2] sdb1[1] sda1[0]
573487616 blocks level 5, 128k chunk, algorithm 2 [5/5] [UUUUU]

unused devices: <none>

# pvdisplay /dev/md0
--- Physical volume ---
PV Name /dev/md0
VG Name vg0
PV Size 546.92 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 140011
Free PE 62699
Allocated PE 77312
PV UUID a76cj4-Fvnf-xkY8-bE0j-Wcdk-jtb0-mq9NbF

# vgdisplay vg0
--- Volume group ---
VG Name vg0
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 37
VG Access read/write
VG Status resizable
MAX LV 256
Cur LV 36
Open LV 36
Max PV 256
Cur PV 1
Act PV 1
VG Size 546.92 GB
PE Size 4.00 MB
Total PE 140011
Alloc PE / Size 77312 / 302.00 GB
Free PE / Size 62699 / 244.92 GB
VG UUID EameBy-n1m#-cwNa-rKqz-YqoM-hSEH-BKVeQQ

# lvdisplay
--- Logical volume ---
LV Name /dev/vg0/home
VG Name vg0
LV UUID yQFLXG-KLog-TdWQ-Rvis-35U1-jUj1-zO0h3M
LV Write Access read/write
LV Status available
# open 1
LV Size 25.00 GB
Current LE 6400
Segments 1
Allocation next free (default)
Read ahead sectors 0
Block device 253:0

[...35 more...]

-ryan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/