On Sun, 16 Jan 2005, Henrique de Moraes Holschuh wrote: > This is apparently related to #281831, so I am directing it there.
Well, it turns out it is not. vgscan is just being obnoxious as ever, but it has no bearing on the lvm crash with 2.6.10-4. I am cc'ing 281831 just to not leave a misleading note in there. What happens is that vgchange -a y segfaults under 2.6.10-4, just after mlockall(MLC_CURRENT|MLC_FUTURE) returns with a 0 state. At that point, under 2.6.10-3, vgchange would brk(0). Under 2.6.10-4, it just segfaults. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
