Linux LVM users
 help / color / mirror / Atom feed
From: David Mohr <squisher@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] help
Date: Thu, 5 May 2005 10:05:21 -0500	[thread overview]
Message-ID: <472d4b2505050508052371491e@mail.gmail.com> (raw)
In-Reply-To: <20050505125502.M61440@pk25.com>

Hi,

On 5/5/05, Diaz Rodriguez, Eduardo <ediaz@pk25.com> wrote:
> # From LVM how to
> 
> xfs
> There is no way to shrink XFS file systems.
> 
> If your are touch lvm2 you must know that about 250Gx1000 and 233x1024.
> 
> try use xfs_repair -n for see the reparis..

I don't think that's an issue here because the history that was posted
did not include an xfs_grow after he grew the LV. As such this should
IMO be a pure LVM issue, because XFS was not grown.

> I use (but it is only a personal opinion, this is very dangerous)
> (use again the first commands).
> vgextend my_volume_group /dev/hdc1
> lvextend -L250G /dev/HOME_VG/HOME_LV
> lvscan

Hmm, I agree that it sounds a bit "dangerous" but it might be worth a shot.

> In this point use xfs_repair -n
> If you see good, use xfs_repair (pray)....
> if you don't have luck try xfs_repair -d (after of this reboot) (read man
> xfs_repair)
> try to mount. (pray again).....

See above, should not be necessary.

~David

  reply	other threads:[~2005-05-05 15:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05 12:26 [linux-lvm] help Colm G. Connolly
2005-05-05 12:33 ` Martin Eisenhardt
2005-05-05 13:16 ` Diaz Rodriguez, Eduardo
2005-05-05 15:05   ` David Mohr [this message]
2005-05-07 14:18     ` Colm G. Connolly
  -- strict thread matches above, loose matches on Subject: below --
2001-07-26 15:42 Pierre Lamb
2001-07-22  4:36 [linux-lvm] Help Ben Konosky
2001-07-22  4:40 ` Steven Lembark
2001-07-22  5:00   ` Ben Konosky
2001-07-23  7:52 ` Heinz J. Mauelshagen
2001-07-24  2:02   ` Ben Konosky

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=472d4b2505050508052371491e@mail.gmail.com \
    --to=squisher@gmail.com \
    --cc=david@mcbf.net \
    --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