From: Eric Sandeen <sandeen@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: New warning: Unable to get device geometry for [filename]
Date: Fri, 27 Jan 2012 21:57:27 -0600 [thread overview]
Message-ID: <4F237227.2000208@redhat.com> (raw)
In-Reply-To: <20120127225346.GA7449@amd.home.annexia.org>
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.
Does mkfs.xfs do any differently?
thanks,
-Eric
> Rich.
>
next prev parent reply other threads:[~2012-01-28 3:57 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 [this message]
2012-01-30 14:34 ` Richard W.M. Jones
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=4F237227.2000208@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=rjones@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).