From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] [SOLVED]: lvm2 and partition shringkin: superblock/filesystem size mismatch
Date: Wed, 1 Dec 2010 15:12:59 +0100 [thread overview]
Message-ID: <20101201141259.GA17090@barkeeper1-xen.linbit> (raw)
In-Reply-To: <id5ji7$b6h$1@dough.gmane.org>
On Wed, Dec 01, 2010 at 02:45:42PM +0100, Johannes Graumann wrote:
> And yes, by that I set the truncation of the FS (thanks, Lars for pointing
> that out) in stone ...
Soo... did the fsck you ran immediately after the mke2fs -S complain,
or did you get away with no more than a fright?
Lars
next prev parent reply other threads:[~2010-12-01 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 7:28 [linux-lvm] lvm2 and partition shringkin: superblock/filesystem size mismatch Johannes Graumann
2010-12-01 10:04 ` Lars Ellenberg
2010-12-01 10:10 ` [linux-lvm] [SOLVED]: " Johannes Graumann
2010-12-01 13:45 ` Johannes Graumann
2010-12-01 14:12 ` Lars Ellenberg [this message]
2010-12-01 14:23 ` Johannes Graumann
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=20101201141259.GA17090@barkeeper1-xen.linbit \
--to=lars.ellenberg@linbit.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;
as well as URLs for NNTP newsgroup(s).