From: "Christoph Berger" <chberger@pool.informatik.rwth-aachen.de>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Remount a LVM Vol after a system crash
Date: Tue, 16 Oct 2001 18:19:38 +0200 [thread overview]
Message-ID: <000201c1565e$5affe980$6c88e289@tweety> (raw)
[-- Attachment #1: Type: text/plain, Size: 2760 bytes --]
Hello,
A few days ago my system crashes and ive used LVM v 0.8 with one volume
group(server), two physical volumes(hda6, hdb6) and one logical
volume(dev/server/ftp)
Now ive installed Suse 7.2 with LVM v 0.9 Beta7, but i cant mount the
logical volume.
The error message is:
# mount /dev/server/ftp /mnt
mount: wrong fs type, bad option, bad superblock on /dev/server/ftp,
or too many mounted file systems
I get the following outputs from my system:
# vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found active volume group "server"
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume
group
# pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- ACTIVE PV "/dev/hda6" of VG "server" [37.78 GB / 0 free]
pvscan -- ACTIVE PV "/dev/hdb5" of VG "server" [41.92 GB / 0 free]
pvscan -- total: 2 [79.71 GB] / in use: 2 [79.71 GB] / in no VG: 0 [0]
# pvdisplay /dev/hda6
--- Physical volume ---
PV Name /dev/hda6
VG Name server
PV Size 37.78 GB / NOT usable 3.75 MB [LVM: 267 KB]
PV# 1
PV Status available
Allocatable yes (but full)
Cur LV 1
PE Size (KByte) 4096
Total PE 9671
Free PE 0
Allocated PE 9671
PV UUID /dev/h-da6
# pvdisplay /dev/hdb5
--- Physical volume ---
PV Name /dev/hdb5
VG Name server
PV Size 41.93 GB / NOT usable 3.45 MB [LVM: 271 KB]
PV# 2
PV Status available
Allocatable yes (but full)
Cur LV 1
PE Size (KByte) 4096
Total PE 10732
Free PE 0
Allocated PE 10732
PV UUID /dev/h-db5
# vgchange -ay
vgchange -- volume group "server" already active
# lvchange -ay /dev/server/ftp
lvchange -- logical volume "/dev/server/ftp" is already active
lvchange -- availability of logical volume "/dev/server/ftp" doesn't
have to be changed
lvchange -- logical volume "/dev/server/ftp" didn't have to be changed
Ive tried to follow the instructions of the mailing list article, ive
found at http://www.geocrawler.com/archives/3/3500/2001/4/0/5655568/
But it doesnt work, After vgchange ay I get an error message, too,
like
vgcfgrestore -- ERROR: different structure size stored in
"/etc/lvmconf/export.conf"
than expected in file vg_cfgrestore.c [line
> 120]
> vgcfgrestore -- ERROR "vg_cfgrestore(): read" restoring volume group
"export"
I hope you can help me,
Thanks
Christoph
[-- Attachment #2: Type: text/html, Size: 18652 bytes --]
next reply other threads:[~2001-10-16 16:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 16:19 Christoph Berger [this message]
2001-10-16 21:40 ` [linux-lvm] Remount a LVM Vol after a system crash Heinz J . Mauelshagen
2001-10-17 9:27 ` [linux-lvm] read_intr errors Erick Calder
2001-10-17 14:29 ` Patrick Caulfield
2001-10-17 20:08 ` Erick Calder
2001-10-18 7:42 ` Patrick Caulfield
2001-10-23 23:19 ` Erick Calder
2001-10-24 4:25 ` Patrick Caulfield
2001-10-26 2:13 ` Erick Calder
2001-10-26 3:29 ` Patrick Caulfield
2001-10-26 16:16 ` Erick Calder
2001-10-30 2:55 ` Patrick Caulfield
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='000201c1565e$5affe980$6c88e289@tweety' \
--to=chberger@pool.informatik.rwth-aachen.de \
--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).