From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [linux-lvm] Tools compile problem, 1.0.1-rc4 on RH6.2 w/kernel 2.4.12 References: <20011015105230.C609@tykepenguin.com> From: Terje Kvernes Date: 15 Oct 2001 13:24:03 +0200 In-Reply-To: Morten Wang's message of "15 Oct 2001 13:07:23 +0200" Message-ID: MIME-Version: 1.0 Sender: linux-lvm-admin@sistina.com Errors-To: linux-lvm-admin@sistina.com Reply-To: linux-lvm@sistina.com List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-lvm@sistina.com Morten Wang 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