From: "Tobias Hahn" <TobHahn@web.de>
To: linux-LVM-Bug@sistina.com, linux-LVM@sistina.com
Subject: [linux-lvm] LVM problems
Date: Tue, 19 Jun 2001 14:12:03 +0200 [thread overview]
Message-ID: <200106191212.f5JCC3j06725@mailgate4.cinetic.de> (raw)
Hi!
I have serious trouble trying to get LVM to work again since I upgraded my lvm-tools to 0.9beta6. I cannot access my vg (and needless to say, almost all of my system is on that vg :-( ). The problem is that the kernel complains about an unsupported ioctl. I looked up this problem in lvm-related mailinglists and figured out that this is a version mismatch between kernel lvm and user lvm. At that point I was using kernel 2.4.3. According to the mailing list, the problem should be fixed in kernel 2.4.4. However, kernel 2.4.5 (downloaded from ftp.kernel.org) still contains 0.9beta2. So I downloaded the lvm-source from ftp.sistina.com (both beta6 and beta7) and tried to patch kernel 2.4.5 following the instructions in PATCHES/README. The patched kernel, however, does not link any longer.
All I'm asking for is a way to get my data back - either by telling me how lvm can be convinced to run or by just getting that stuff off lvm and removing lvm from my system. It would be very nice if someone could at least acknowledge receipt of this problem report, my last mail seems to have vanished out in the void.
Thanx everyone for reading this mail!
Regards, Tobias Hahn
ld -m elf_i386 -T /tmp/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \
--start-group \
arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \
drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/char/agp/agp.o drivers/isdn/isdn.a drivers/ide/idedriver.o drivers/scsi/scsidrv.o drivers/cdrom/driver.o drivers/pci/driver.o drivers/video/video.o drivers/md/mddev.o \
net/network.o \
/tmp/linux/arch/i386/lib/lib.a /tmp/linux/lib/lib.a /tmp/linux/arch/i386/lib/lib.a \
--end-group \
-o vmlinux
drivers/md/mddev.o: In function `__update_hardblocksize':
drivers/md/mddev.o(.text+0x7e01): undefined reference to `get_hardblocksize'
drivers/md/mddev.o(.text+0x7e3d): undefined reference to `get_hardblocksize'
make: *** [vmlinux] Error 1
______________________________________________________________________________
Ferienklick.de - Jede Menge Urlaub auf einen Blick!
Hier geht's zu Ihrem Traumstrand: http://ferienklick.de/?PP=2-0-100-105-1
next reply other threads:[~2001-06-19 12:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 12:12 Tobias Hahn [this message]
2001-06-19 12:14 ` [linux-lvm] LVM problems Ilya Martynov
2001-06-19 17:27 ` Andreas Dilger
2001-06-19 19:24 ` AJ Lewis
-- strict thread matches above, loose matches on Subject: below --
2001-06-19 19:28 Gonyou, Austin
2001-06-19 21:19 ` AJ Lewis
2001-06-20 1:11 ` Ed Tomlinson
2001-06-20 13:50 ` Heinz J. Mauelshagen
2001-06-21 0:58 ` Paul Jakma
2001-06-21 9:05 ` Heinz J. Mauelshagen
2001-06-20 1:15 ` Paul Jakma
2001-06-21 8:58 ` Heinz J. Mauelshagen
2001-06-19 22:42 Gonyou, Austin
2004-02-08 17:50 [linux-lvm]LVM Problems David Rohrer
2005-12-07 1:47 [linux-lvm] LVM problems Kelly Harding
2005-12-07 2:06 ` Kelly Harding
2005-12-07 8:06 ` Anil Kumar Sharma
2005-12-07 22:13 ` Alasdair G Kergon
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=200106191212.f5JCC3j06725@mailgate4.cinetic.de \
--to=tobhahn@web.de \
--cc=linux-LVM-Bug@sistina.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).