Morten Wang <warnckew@online.no> writes: > I _did_ check the two usual symlinks in /usr/include, 'linux' & > 'asm', which point to directories in the kernel-source tree. they > were ok. what I forgot to check was whether /usr/include/malloc.h > actually was readable, and then I found out. it wasn't possible to > read the file and it had incorrect values in a directory listing. > did check around a bit for various clues, but couldn't find any, so > I assume it's just a filesystem error after a few unwanted > shutdowns. a reinstall of the glibc-devel RPM fixed the problem, and > the tools compiled successfully. uhm, this is a bad thing. what filesystem does /usr/include reside on? if a file is corrupt and the fsck didn't fix it under boot, I'd be worried about physical disk damage. > 'make install' then ran successfully, and I could run vgcan and > vgchange without any problems. am looking forward to checking out > LVM, thanks! you'll enjoy it. trust me. :) (now, if I could just get snapshots to work like I want them to. sigh) -- Terje
