From: Karel Zak <kzak@redhat.com>
To: grantksupport@operamail.com
Cc: util-linux@vger.kernel.org
Subject: Re: blikid reports gdisk-created Bios Boot Partition, created with NO fs, has fs TYPE=ext4. Bug/why?
Date: Thu, 19 Feb 2015 11:01:16 +0100 [thread overview]
Message-ID: <20150219100116.GD11507@ws.net.home> (raw)
In-Reply-To: <1424032823.1090725.227824713.20C2D28B@webmail.messagingengine.com>
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
prev parent reply other threads:[~2015-02-19 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 20:40 blikid reports gdisk-created Bios Boot Partition, created with NO fs, has fs TYPE=ext4. Bug/why? grantksupport
2015-02-19 10:01 ` Karel Zak [this message]
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=20150219100116.GD11507@ws.net.home \
--to=kzak@redhat.com \
--cc=grantksupport@operamail.com \
--cc=util-linux@vger.kernel.org \
/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