[mythtv-users] IOBOUND errors after kernel upgrade from 2.6.31 to 2.6.32
John Drescher
drescherjm at gmail.com
Wed Apr 28 15:01:46 UTC 2010
>>> Thanks John! I might just try that. I was going to say that you'd be
>>> pretty hard pressed to find any Gentoo user that configures the entire
>>> kernel from the defaults in order to upgrade. If that's how you had
>>> to do it even I might quit Gentoo :D...and I'm a huge fanboy. It's
>>> not like the kernel make process is very likely to let an invalid
>>> config get through or something.
>>>
>>> There's definitely something different in 2.6.32. All those IOBOUND
>>> errors do in fact go away when I reboot to 2.6.31.
>>>
>>
>> I do not have 2.6.32 running on any of my mythtv boxes or any other
>> machine that I can think of at the moment. However I do run 2.6.33 on
>> several gentoo raid servers at work with ext4. I am not seeing any
>> IOBOUND errors there.
>>
>> John
>
> Interesting. The fact is that my backend setup really isn't ideal in
> that I have two disks LVMed together, but the non-LVM OS EXT3
> partition with the MySQL database is in fact on one of those disks as
> well. That's the way it's always been and I'm not sure I could even
> get away with adding a third disk to it (it's a Dell Dimension 4600).
> Again, I've gotten away with that up until now, and I don't get
> IOBOUNDS with 2.6.31, but it might not take much of a change to upset
> the apple cart given that less-than-ideal setup.
>
> I've always used the gentoo-sources kernels. I suppose if I try it I
> should use unmask the highest version in portage right now
> (sys-kernel/gentoo-sources-2.6.33-r1)? I've actually never used a
> kernel that wasn't marked stable before.
>
I am using gentoo sources as well. I have not had much issue with
kernels that were not marked stable.
datastore3 ~ # uname -a
Linux datastore3 2.6.33-gentoo #1 SMP Tue Mar 9 18:19:35 EST 2010
x86_64 Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz GenuineIntel
GNU/Linux
datastore3 ~ # lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
data_analysis vg1 -wi-ao 500.00g
imagedata vg1 -wi-ao 1.70t
metro vg1 -wi-ao 50.00g
portage vg1 -wi-ao 5.00g
temp_data vg1 -wi-a- 50.00g
var_tmp vg1 -wi-ao 50.00g
virtualization vg1 -wi-ao 50.00g
datastore3 ~ # pvs
PV VG Fmt Attr PSize PFree
/dev/md2 vg1 lvm2 a- 3.13t 764.89g
datastore3 ~ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sda1[0] sdg1[7] sdh1[6] sdf1[5] sde1[4] sdd1[3]
sdc1[2] sdb1[1]
272960 blocks [8/8] [UUUUUUUU]
md2 : active raid5 sdf4[5] sdg4[7] sdh4[6] sdb4[1] sdc4[2] sda4[0]
sde4[4] sdd4[3]
3361616832 blocks level 5, 64k chunk, algorithm 2 [8/8] [UUUUUUUU]
md1 : active raid5 sdf3[5] sdg3[7] sdh3[6] sdb3[1] sdc3[2] sda3[0]
sde3[4] sdd3[3]
51447424 blocks level 5, 64k chunk, algorithm 2 [8/8] [UUUUUUUU]
unused devices: <none>
datastore3 ~ #
datastore3 ~ # mount | grep vg1
/dev/mapper/vg1-metro on /mnt/vg0/metro type ext4
(rw,commit=15,barrier=0,data=writeback)
/dev/mapper/vg1-portage on /usr/portage type ext4
(rw,commit=60,barrier=0,data=writeback)
/dev/mapper/vg1-var_tmp on /var/tmp type ext4
(rw,commit=60,barrier=0,data=writeback)
/dev/mapper/vg1-virtualization on /vz type ext4
(rw,commit=60,barrier=0,data=writeback)
/dev/mapper/vg1-imagedata on /mnt/vg1/imagedata type ext4
(rw,noatime,nodiratime,commit=60,barrier=0,data=writeback)
/dev/mapper/vg1-data_analysis on /mnt/vg1/data_analysis type ext4
(rw,noatime,nodiratime,commit=60,barrier=0,data=writeback)
datastore3 ~ # dmesg | grep IOBOUND
datastore3 ~ #
John
More information about the mythtv-users
mailing list