From: "Måns Rullgård" <mru@inprovide.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Re: lvextend error on XFS
Date: Mon, 22 Nov 2004 22:02:23 +0100 [thread overview]
Message-ID: <yw1xwtwdwqao.fsf@ford.inprovide.com> (raw)
In-Reply-To: 41A250A0.5060702@ercwc.org
"Frank J. Buchholz" <frankb@ercwc.org> writes:
> Hello,
>
> I recently attempted to extend my logical volume. First I added an
> additional physical volume to an existing volume group. This worked
> fine.
>
> vgextend Volume00 /dev/sba
> lvextend -L+100G /dev/Volume00/LogVol00
>
> However when it came time to run the lvextend command I received a
> number of device-mapper errors. While I was trying to determine what
> the errors were I noticed that the filesystem that sits on the logical
> volume being extended was no longer available. I attempted to umount
> the filesystem however the command froze. I then rebooted the system
> without mounting the filesystem in question and manually mounted the
> filesystem. XFS reported back that it could not locate the superblock.
I have done lvextend followed by xfs_growfs many times without any
problems. Have you checked for hardware errors?
--
M�ns Rullg�rd
mru@inprovide.com
next prev parent reply other threads:[~2004-11-22 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 20:48 [linux-lvm] lvextend error on XFS Frank J. Buchholz
2004-11-22 21:02 ` Måns Rullgård [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-22 22:08 [linux-lvm] " Frank J. Buchholz
2004-11-22 22:23 ` Måns Rullgård
2004-11-19 9:47 [linux-lvm] HA Fileserver configuration recommendation sought Gary Mansell
2004-11-19 18:21 ` Dan Stromberg
2004-11-19 19:24 ` David S.
2004-11-20 0:13 ` Dan Stromberg
2004-11-20 0:22 ` Garrick Staples
2004-11-20 1:36 ` Dan Stromberg
2004-11-20 2:08 ` Garrick Staples
2004-11-20 2:18 ` Dan Stromberg
2004-11-22 15:36 ` Kevin Anderson
2004-11-23 0:42 ` Dan Stromberg
2004-11-23 2:10 ` [linux-lvm] Re: lvextend error on XFS Frank J. Buchholz
2004-11-23 8:38 ` David Greaves
2004-11-23 12:37 ` Frank J. Buchholz
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=yw1xwtwdwqao.fsf@ford.inprovide.com \
--to=mru@inprovide.com \
--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