linux-ext4 - Re: New warning: Unable to get device geometry for [filename]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F237227.2000208@redhat.com>
Date:	Fri, 27 Jan 2012 21:57:27 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	"Richard W.M. Jones" <rjones@...hat.com>
CC:	linux-ext4@...r.kernel.org
Subject: Re: New warning: Unable to get device geometry for [filename]

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.
> 

--
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