From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] thin: 235:2 pool target (735616 blocks) too small: expected 809216
Date: Thu, 02 Jun 2016 06:49:35 -0400 [thread overview]
Message-ID: <1464864575.13773.29.camel@interlinx.bc.ca> (raw)
In-Reply-To: <c5664f25-6ee4-9a4f-f2d7-f6e45206de83@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]
On Thu, 2016-06-02 at 11:11 +0200, Zdenek Kabelac wrote:
> Hi
Hi.
> So it seems your machine has crashed (you probably know better)
> during
> thin-pool resize operation.
So, this is actually a family member's machine and he was using it at
the time so I don't know, firsthand what happened.
He says he was just adding some plugin to some (Windows) program in
Wine. Doesn't seem like that should come anywhere near resizing so I
will ask him again.
> Unfortunately fc23 has lvm2 version 2.02.132 - and version 2.02.133
> has
> improvement patch to make the resize more resistent (but still not as
> good as
> I wish to be).
Incremental improvements are improvements all the same. :-)
> So what happened - lvm2 resized _tdata LV - tried to resumed it -
> and
> it has failed along this path - however since the 'resize' is ATM a
> single
> transaction - the lvm2 rollback reverted to previous size - yet thin-
> pool
> already managed to remembered 'new' bigger size.
Ahhh.
> So please take a look at your logs (if you have some) if there
> is something suspicious to be mentioned (thought if you machined
> has freezed, hardly any log will be available).
I will take a look once I can get the system back up and running.
> To get access to your thin-pool - I'm attaching restored metadata
> content from
> your disk header with 'bigger' _tdata volume.
There was no attachment.
> To restore use:
>
> 'vgcfgrestore -f back --force brianr-laptop'
I can do that in Fedora's "rescue" environment? Probably "lvm
vgcfgrestore -f back --force brianr-laptop" instead.
> It would be really interesting to know the reason of failure - but I
> can
> understand you could hardly obtain.
I will see if there is anything in the logs and get back to you. It's
the least I can do in return for the help you have provided. Much
appreciated.
Cheers,
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-02 10:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 10:57 [linux-lvm] thin: 235:2 pool target (735616 blocks) too small: expected 809216 Brian J. Murrell
2016-05-31 11:22 ` Zdenek Kabelac
2016-06-01 22:52 ` Brian J. Murrell
2016-06-02 9:11 ` Zdenek Kabelac
2016-06-02 10:49 ` Brian J. Murrell [this message]
2016-06-02 12:15 ` Zdenek Kabelac
2016-06-02 19:27 ` Brian J. Murrell
2016-06-02 19:32 ` Zdenek Kabelac
2016-06-02 21:18 ` Brian J. Murrell
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=1464864575.13773.29.camel@interlinx.bc.ca \
--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).