From: Goetz Bock <bock@blacknet.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] URgent - please Help - our main system is corrupt, no one can wor k!
Date: Mon Jun 10 08:36:01 2002 [thread overview]
Message-ID: <20020610143814.B28341@zealot.blacknet.de> (raw)
In-Reply-To: <F47B5C16711BEC4BBB0651C75F724809D5C6@qntsv14.quant.com>; from G.SchaeferReimers@quant-forum.de on Mon, Jun 10, 2002 at 03:16:53PM +0200
On Mon, Jun 10 '02 at 15:16, Gesine Sch�fer-Reimers wrote:
> 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.
did not reache the list (AFAICT)
> 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.
Most likely it come up in a "something is broken, bplease try to fix it
manualy" state
> For instance the /var directory claims to be mounted but is empty and
> cannot be mounted, for they are not mounted !! In /procs/ not
The mount command takes it's information from /etc/mtap and not from
/proc, so most likely the console message was something like "unable to
run fsck on /dev/bla" please enter root password and try to fix it,
system will reboot after you left the shell.
> [ ... ]
> 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?
possible there are backups in /etc/lvmtab.d, but maybe not.
It would realy help, what the system told you when it booted.
A "simple" fix might be to reboot and pray :-/, but this might fu**up
everything.
Unfortunately I've not enough informations to help you further :-(, and
I don't know how stable yast2 is so I can only guess what you might be
able to do to fix anything, but my guesses might be way off.
Cu,
Goetz.
--
Goetz Bock bock@blacknet.de
IT Consulting Munich Germany
next prev parent reply other threads:[~2002-06-10 8:36 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 [this message]
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 ` [linux-lvm] URgent - please Help - our main system is corrupt, no one can work! Bas
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=20020610143814.B28341@zealot.blacknet.de \
--to=bock@blacknet.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