From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sat, 14 Mar 2009 18:01:44 +0000 Subject: Re: vol_id doesn't recognize unjournaled ext4 Message-Id: List-Id: References: <20090314173946.GA16215@ibh.de> In-Reply-To: <20090314173946.GA16215@ibh.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Sat, Mar 14, 2009 at 18:39, Andre Beck wrote: > fooling around with a Debian Sid/Experimental installation on a USB > flash drive, I had some boot issues as /dev/disk/by-{uuid,label} showed > no trace of my boot partition. I've tracked this to vol_id not > recognizing an ext4 block device if the ext4 doesn't have a journal > (a feature that was added to ext4 as an afterthought for the flash > drive use case). The code in ext.c makes pretty clear why that happens, > it will only go into the ext3 branch if there is a journal in the > first place, and will only recognize ext4 as incompatible features > on top of ext3 in that branch. > > BTW, util-linux mount(8) apparently has the same issue, as it doesn't > autodetect an unjournaled ext4 and insists on "-t ext4" to mount it. No, libvolume_id does not support it. Libvolume_id and blkid got merged and major parts got rewritten by Karel and we have a new libblkid in util-linux-ng now. We are on the way to switch udev over to it during the next month. Libvolume_id and vol_id will no longer be used and deleted from the udev tree. If you like it detected now, you could provide a patch for it, but it's unlikely, that it will hit a distro release before we replaced it with libblkid, which supports it already. Thanks, Kay