From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Brian Murrell <brian@interlinx.bc.ca>
Subject: Re: [linux-lvm] thin: 235:2 pool target (735616 blocks) too small: expected 809216
Date: Thu, 2 Jun 2016 11:11:21 +0200 [thread overview]
Message-ID: <c5664f25-6ee4-9a4f-f2d7-f6e45206de83@gmail.com> (raw)
In-Reply-To: <1464821577.13773.9.camel@interlinx.bc.ca>
Dne 2.6.2016 v 00:52 Brian J. Murrell napsal(a):
> On Tue, 2016-05-31 at 13:22 +0200, Zdenek Kabelac wrote:
>> Hi
>
> Sorry for the delay. It can be a bugger to get an environment on a
> laptop that won't boot USB devices to a state where you can access the
> PV and store something from it.
>
>> Well - could you post somewhere for download 1st. MB of your
>> PV device?
>>
>> dd if=/dev/sdX of=/tmp/upload_me bs=1M count=1
>
> You should be able to get that from:
>
> http://www.interlinx.bc.ca/~brian/lvm-pv.img
>
>> Have you already tried to restore in some way ?
>
> I have not tried anything yet for fear of making things worse ("angels
> tread" and all that), so this is a blank slate from the point of it
> first failing.
Hi
So it seems your machine has crashed (you probably know better) during
thin-pool resize operation.
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).
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.
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).
To get access to your thin-pool - I'm attaching restored metadata content from
your disk header with 'bigger' _tdata volume.
To restore use:
'vgcfgrestore -f back --force brianr-laptop'
It would be really interesting to know the reason of failure - but I can
understand you could hardly obtain.
Regards
Zdenek
next prev parent reply other threads:[~2016-06-02 9:11 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 [this message]
2016-06-02 10:49 ` Brian J. Murrell
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=c5664f25-6ee4-9a4f-f2d7-f6e45206de83@gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=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).