From: "Bas" <weblists@gmx.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] URgent - please Help - our main system is corrupt, no one can work!
Date: Mon Jun 10 09:05:02 2002 [thread overview]
Message-ID: <005301c21088$4131bad0$3b00a8c0@aplabwp0368359> (raw)
In-Reply-To: F47B5C16711BEC4BBB0651C75F724809D5C6@qntsv14.quant.com
Hi,
You probably already tried this, but just to make sure.
# vgscan
# vgchange -a y
Try to mount the filesystems.
Good luck,
Bas.
----- Original Message -----
From: "Gesine Sch�fer-Reimers" <G.SchaeferReimers@quant-forum.de>
To: <linux-lvm@sistina.com>
Sent: Monday, June 10, 2002 3:16 PM
Subject: [linux-lvm] URgent - please Help - our main system is corrupt, no
one can work!
Dear Sirs,
this is the second mail. I tried it this noon but got no answer so far, but
our whole
production is down and I really have to fix it.
We use SUSE 7.3 with LVM. I have got /var and /tmp and /opt an /home and
many
Partitions without a filesystem for our database on a logical volume group
named quant.
The system was up and running. I added (with YAST2) one more logical volume
to the
volume group, applied an restarted. The restart ist "strange", since only
parts of the
systems come up.
For instance the /var directory claims to be mounted but is empty and cannot
be
mounted, for they are not mounted !! In /procs/ not filesystem is shown as
mountet.
The / filesystem, which is out of the VM is in a read only state, some files
are there
others are gone.
When I do vgdisplay the VM is shown as available, when I do vgdisplay -D it
is shown
as unavailable.
I cannot afford any tests, since I do not have a backup of the database data
>from today.
It looks for me as if the addition of the new logical volume wrote some
information in a
place where it does not belong. Can I recover the old state without loosing
information?
With best regards
Gesine Sch�fer-Reimers
quant GmbH
++49/40/254078-70
_______________________________________________
linux-lvm mailing list
linux-lvm@sistina.com
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
prev parent reply other threads:[~2002-06-10 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 8:15 [linux-lvm] URgent - please Help - our main system is corrupt, no one can wor k! Gesine Schäfer-Reimers
2002-06-10 8:36 ` Goetz Bock
2002-06-10 8:52 ` Benjamin Scott
2002-06-10 8:59 ` Tim
2002-06-10 11:02 ` Andreas Dilger
2002-06-10 11:12 ` Goetz Bock
2002-06-10 9:05 ` Bas [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='005301c21088$4131bad0$3b00a8c0@aplabwp0368359' \
--to=weblists@gmx.net \
--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