All of lore.kernel.org
 help / color / mirror / Atom feed
From: "marduk" <marduk@python.net>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Help, /usr will not mount!
Date: Thu Nov  6 06:36:01 2003	[thread overview]
Message-ID: <20031106123527.B08897F524@server2.messagingengine.com> (raw)

I just lost /usr.  Please someone tell me it can be restored.

The thing is, I am attempting to move my drives to another system.  My
two SCSI drives
are smaller and older and the new system has no SCSI adapter yet, so I
thought it best
to remove the two scsi drives from the volume group before moving the 2
IDEs to the new
box.  Here's what I did:

pvmove /dev/sda1

Well, pvmove gave me an error message (I can not remember the exact
message) and returned
me to the command prompt, so I assumed nothing was done.  Afterward, I
ran another,
non-destructive command (i think vgscan or something like that) and the
process just froze.
Since I was at the console in single-user mode and could not get back to
the shell, I
rebooted.  Well, on reboot the system could not mount my /usr or
/var/video (not important)
because the superblock could not be found.  Both partitions were logical
volumes.

It really sucks not having /usr as you can imagine. I've managed to get a
basic /usr working
that I copied from a CD onto my / partition (that's not a LVM volume).

Running  pvmove again, just gives me the same error as before.  Running
pvmove --abort freezes
again.  When I run ps after the pvmove --abort, I see the process status
for pvmove is D<L
but it doesn't appear to be doing anything (it's been "running" for over
6 hours now).

Please tell me I can get /usr (and /var/video) back and how.

--m
-- 
  
  marduk@letterboxes.org

                 reply	other threads:[~2003-11-06  6:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20031106123527.B08897F524@server2.messagingengine.com \
    --to=marduk@python.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.