Linux LVM users
 help / color / mirror / Atom feed
From: "Frank J. Buchholz" <frankb@ercwc.org>
To: linux-lvm@redhat.com
Subject: [linux-lvm] XFS device-mapper problem
Date: Tue, 23 Nov 2004 23:49:00 -0500	[thread overview]
Message-ID: <41A412BC.3050409@ercwc.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]

Hello,

Recently I attemped to 'lvextend' a logical volume.  My fatal error was 
that I had a typo in my prior 'vgextend' command in which I added 
/dev/sda to a volume that already held /dev/sda1. One the device for the 
disk (sda) and the other being the device for the only partition on the 
disk (sda1). Oh no!

I recieved the following error during the 'lvextend' command...
lvm> lvextend -L+1G /dev/Volume00/LogVol00
  Extending logical volume LogVol00 to 2.93 TB
  device-mapper ioctl cmd 9 failed: Invalid argument
  Couldn't load device 'Volume00-LogVol00'.
  Problem reactivating LogVol00

I have since 'lvreduce'd the logical volume back to its original size 
and 'vgreduce'd the volume by removing /dev/sda from the volume.  Both 
of these commands ran well without any noticable errors.

However my problem is that I believe I have corrupted the block device 
located at /dev/mapper.  The block device in that directory is 
Volume00-LogVol00.  The filesystem is XFS.  When I run xfs_check on the 
filesystem I recieve the following error:
xfs_check /dev/Volume00/LogVol00
xfs_check: /dev/Volume00/LogVol00 is invalid (cannot read first 512 bytes)

When I run:
# hexdump -C Volume00-LogVol00
#
It simply returns nothing except a prompt.

The directory listing looks like:
# pwd
/dev/mapper
#ls -l
crw-------  1 root root  10, 63 Nov 22 12:05 control
brw-------  1 root root 253,  1 Jun 17  2003 Volume00-LogVol00
brw-------  1 root root 253,  0 Nov 22 10:03 Volume01-LogVol00

Volume01 is a working block device while Volume00 seems to have stopped 
working. 

I can 'hexdump' /dev/sda1, the physical volume device in Volume00, and 
it shows me the content of the filesystem (phew, still there).

How do I fix LVM and device-mapper to make this work again?

Thanks,
Frank

-- 
Frank J. Buchholz




[-- Attachment #2: frankb.vcf --]
[-- Type: text/x-vcard, Size: 328 bytes --]

begin:vcard
fn:Frank J. Buchholz
n:Buchholz;Frank J.
org:Education & Research Services
adr;dom:Suite 170;;151 Patton Ave;Asheville;NC;28801
email;internet:frankb@ercwc.org
title:Director, High Performance Computing
tel;work:828.350.2421
tel;fax:828.350.2008
tel;cell:828.606.2105
url:http://www.erswc.org
version:2.1
end:vcard


                 reply	other threads:[~2004-11-24  4:49 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=41A412BC.3050409@ercwc.org \
    --to=frankb@ercwc.org \
    --cc=linux-lvm@redhat.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