linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Insufficient free space: 1 extents needed, but only 0 available with 32.83g available
Date: Tue, 02 Apr 2013 09:17:02 -0400	[thread overview]
Message-ID: <kjeloc$hvh$1@ger.gmane.org> (raw)
In-Reply-To: <515AC642.7000609@redhat.com>

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

On 13-04-02 07:51 AM, Marian Csontos wrote:
> 
> You said there is a LV containing the bad block. You can not have a
> block belonging to two LVs

Ah ha!  The missing link.  Interestingly enough, as I was going through
this process I had a nagging feeling that I somehow needed to release
the block from the existing LV.

> Use something like `pvmove --alloc anywhere /dev/sda2:2812` first.

Yeah.  That did the trick.

> I fully respect your choice, I myself have enough of throw away data
> like VMs...

Thanks.

> Just for convenience, if you can spare more than 2 blocks be more
> generous and disable larger extent of blocks - those disk errors like to
> spread... (or allocate to LV which loosing will be least )

Yeah.  I don't mind handling them piecemeal.  Like I said, nothing on
this machine is irreplaceable.

> Sometimes backups are not backups. To check if the backups work, have
> you ever tried to recover *all* data from those backups?

But of course!  You can't really call it a backup unless you have done a
successful restore.  I had to restore a machine from this same backup
only a few weeks ago.

> By size of the disk looks like notebook.

Nope.  Just old enough that that size disk was "common" when it was built.

> Are you using disk encryption?

Nope.

> (Loosing LUKS header could be rather painful!

Indeed.  But not encrypting.  In any case, losing the LUKS header might
be just enough excuse to restore to bare-metal.

> And also depending on FS you may loose more than just few files.

Yeah.  Pass on XFS and Reiserfs.  Both have lost me too much data to use
again.  Fortunately ext{3,4} don't have such catastrophic failures just
losing a block or two.

Cheers,
b.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

      reply	other threads:[~2013-04-02 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01 12:23 [linux-lvm] Insufficient free space: 1 extents needed, but only 0 available with 32.83g available Brian J. Murrell
2013-04-02 11:51 ` Marian Csontos
2013-04-02 13:17   ` Brian J. Murrell [this message]

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='kjeloc$hvh$1@ger.gmane.org' \
    --to=brian@interlinx.bc.ca \
    --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;
as well as URLs for NNTP newsgroup(s).