[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120130143433.GW27709@amd.home.annexia.org>
Date: Mon, 30 Jan 2012 14:34:33 +0000
From: "Richard W.M. Jones" <rjones@...hat.com>
To: Eric Sandeen <sandeen@...hat.com>
Cc: linux-ext4@...r.kernel.org
Subject: Re: New warning: Unable to get device geometry for [filename]
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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists