From: Eric Sandeen <sandeen@redhat.com>
To: Adam Huffman <bloch@verdurin.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Problem with 15TB logical volume
Date: Thu, 12 Aug 2010 09:59:09 -0400 [thread overview]
Message-ID: <4C63FE2D.8070500@redhat.com> (raw)
In-Reply-To: <4C63FA81.8060306@redhat.com>
Eric Sandeen wrote:
...
> Without the comma, mkfs thinks you are trying to mkfs a device called
> "stripe-width=384" with a block count of "<devicename>"
>
> Odd eh ;)
>
> Perhaps echoing back the blocks count which it found to be invalid
> (in this case the devicename string) would make the failure more
> obvious...
>
Oh, actually, that is just what it's doing, but it's not obvious,
since it was the device name, and it looked like it was simply reporting
which device had the error...
-Eric
next prev parent reply other threads:[~2010-08-12 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 9:16 Problem with 15TB logical volume Adam Huffman
2010-08-12 13:43 ` Eric Sandeen
2010-08-12 13:59 ` Eric Sandeen [this message]
2010-08-12 14:51 ` Adam Huffman
2010-08-12 15:14 ` Eric Sandeen
2010-08-12 17:44 ` Andreas Dilger
2010-08-12 18:24 ` Eric Sandeen
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=4C63FE2D.8070500@redhat.com \
--to=sandeen@redhat.com \
--cc=bloch@verdurin.com \
--cc=linux-ext4@vger.kernel.org \
/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).