blikid reports gdisk-created Bios Boot Partition, created with NO fs, has fs TYPE=ext4. Bug/why?

blikid reports gdisk-created Bios Boot Partition, created with NO fs, has fs TYPE=ext4. Bug/why?

[grantksupport]

I'd originally posted this to linux-ext4, got redirected here ...

I create a GPT Bios Boot Partition on a clean disk

	sgdisk -z /dev/sdc
	sgdisk -o /dev/sdc
	sgdisk -n 1:2048:+1M    -t 1:ef02  -c 1:"BIOS Boot"           /dev/sdc

IIUC, at this point, the partition should exist with NO filesystem.

But, if I check with blkid

	blkid /dev/sdc1
		/dev/sdc1: LABEL="RAID_BOOT" UUID="8a828baa-f315-4456-88d2-ff14849eb705" TYPE="ext4" PARTLABEL="BIOS Boot" PARTUUID="2b3b10b1-a458-481e-872c-bada7d244b13" 

Note that it IDs the filesystem type as

	TYPE="ext4"

Why?

Bios Boot Partition should have NO filesystem.

Is blkid correct?  Is there, or isn't there a fs on that partition?

if there isn't, what's causint the 'false' report?

If there IS, how do I make sure there isn't?

grant

Re: blikid reports gdisk-created Bios Boot Partition, created with NO fs, has fs TYPE=ext4. Bug/why?

[Karel Zak]

On Sun, Feb 15, 2015 at 12:40:23PM -0800, grantksupport@operamail.com wrote:
> Note that it IDs the filesystem type as
> 
> 	TYPE="ext4"
> 
> Why?
> 
> Bios Boot Partition should have NO filesystem.
> 
> Is blkid correct?  Is there, or isn't there a fs on that partition?

Maybe the disk has been originally used for ext4 and now there is
obsolete signature... Note that fdisks usually only write partition
table to the disk, but does not erase any old stuff.

> If there IS, how do I make sure there isn't?

 wipefs /dev/sdc1

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com