From: "Måns Rullgård" <mru@kth.se>
To: linux-lvm@sistina.com
Subject: [linux-lvm]Re: corrupt /dev/lvm - bizzare properties
Date: Mon Feb 9 04:26:00 2004 [thread overview]
Message-ID: <yw1xvfmgob7w.fsf@kth.se> (raw)
In-Reply-To: 4026FEC4.2050005@adelaide.edu.au
Chris Doherty <chris.doherty@adelaide.edu.au> writes:
>> The filesystem containing /dev has been damaged somehow. You should
>> fsck it. Most likely fsck will remove /dev/lvm so you'll have to
>> recreate it with proper values. Don't just rm it. Something bad has
>> obviously happened and changing things without a proper fsck can make
>> things worse.
>
> thanks. i'll try this tonight and report back. :) my limited
> understanding of LVM leads me to believe that the volume group and
> logical volume within it are actually still safe and sound in /dev/vg1
Chances are it's still there.
> is /dev/lvm just a character device which is used to transmit data
> from the volume group (vg1) to the device driver?
Yes.
> you mention that fsck will probably remove /dev/lvm and that i
> should recreate it. is there any risk to vg1/lv1 if i do that? (as
> i still haven't successfully backed up anything in it's current
> state)
You should be fine. If you are paranoid and vg1 is on different disks
than the root fs you could unplug them while doing the fsck.
--
M�ns Rullg�rd
mru@kth.se
next prev parent reply other threads:[~2004-02-09 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 1:00 [linux-lvm]corrupt /dev/lvm - bizzare properties Chris Doherty
2004-02-08 6:29 ` [linux-lvm]Re: corrupt " Måns Rullgård
2004-02-08 7:01 ` Chris Doherty
2004-02-08 17:50 ` Rainer krienke
2004-02-08 8:46 ` Chris Doherty
2004-02-08 8:51 ` Måns Rullgård
2004-02-08 22:29 ` Chris Doherty
2004-02-09 4:26 ` Måns Rullgård [this message]
2004-02-11 3:16 ` [linux-lvm] " Chris Doherty
2004-02-11 14:33 ` [linux-lvm] LVM Statistics John
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=yw1xvfmgob7w.fsf@kth.se \
--to=mru@kth.se \
--cc=linux-lvm@redhat.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