From: Terje Kvernes <terjekv@math.uio.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Tools compile problem, 1.0.1-rc4 on RH6.2 w/kernel 2.4.12
Date: 15 Oct 2001 13:24:03 +0200 [thread overview]
Message-ID: <wxxelo5tacs.fsf@baal.uio.no> (raw)
In-Reply-To: Morten Wang's message of "15 Oct 2001 13:07:23 +0200"
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
prev parent reply other threads:[~2001-10-15 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 15:07 [linux-lvm] Tools compile problem, 1.0.1-rc4 on RH6.2 w/kernel 2.4.12 Morten Wang
2001-10-15 9:52 ` Patrick Caulfield
2001-10-15 11:07 ` Morten Wang
2001-10-15 11:24 ` Terje Kvernes [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wxxelo5tacs.fsf@baal.uio.no \
--to=terjekv@math.uio.no \
--cc=linux-lvm@sistina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.