From: "Richard W.M. Jones" <rjones@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: New warning: Unable to get device geometry for [filename]
Date: Mon, 30 Jan 2012 14:34:33 +0000 [thread overview]
Message-ID: <20120130143433.GW27709@amd.home.annexia.org> (raw)
In-Reply-To: <4F237227.2000208@redhat.com>
On Fri, Jan 27, 2012 at 09:57:27PM -0600, Eric Sandeen wrote:
> On 1/27/12 4:53 PM, Richard W.M. Jones wrote:
> >
> > I've just noticed that with the latest e2fsprogs, kernel 3.3.0 and
> > blkid (util-linux 2.20.1), I see this spurious warning when using
> > mke2fs on a file:
> >
> > $ truncate -s 4G test1.img
> > $ mke2fs -t ext2 -q -F test1.img
> > warning: Unable to get device geometry for test1.img
> >
> > Oddly this *doesn't* happen except on the very bleeding edge latest
> > versions of everything. I've not (yet) worked out exactly what
> > component has to be upgraded to see it ...
>
> Taking a quick look, I don't _think_ anything above blkid changed
> in e2fsprogs lately, but keep us posted.
Some more observations:
- The warning is 32 bit *only*. Sorry I didn't notice this rather
obvious point before. I have two identically configured Rawhide
guests, except that one is i686 and the other is x86-64, and only
the i686 guest gives this warning.
- If the disk is 1G, no warning. After some binary searching I found
the threshold for the warning is 'truncate -s 2048M' (greater than
or equal gives the warning; smaller, no warning).
> Does mkfs.xfs do any differently?
No warning, at least, not with the default settings and a 4G disk on
32 bit.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
prev parent reply other threads:[~2012-01-30 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 22:53 New warning: Unable to get device geometry for [filename] Richard W.M. Jones
2012-01-28 3:57 ` Eric Sandeen
2012-01-30 14:34 ` Richard W.M. Jones [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=20120130143433.GW27709@amd.home.annexia.org \
--to=rjones@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@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).