From: ToddAndMargo <ToddAndMargo@zoho.com>
To: linux-xfs@vger.kernel.org
Subject: Re: What is the proper way to remove an xfs partition?
Date: Thu, 31 Aug 2017 11:32:00 -0700 [thread overview]
Message-ID: <a1e12c3c-5238-e319-e2ea-982606e808b3@zoho.com> (raw)
In-Reply-To: <e74da24b-b604-b9af-e6b7-6943543fa56a@sandeen.net>
On 08/31/2017 11:16 AM, Eric Sandeen wrote:
> xOn 8/31/17 1:04 PM, ToddAndMargo wrote:
>> Hi All,
>>
>> Fedora 26
>> BIOS boot = legacy (EUFI give me hives)
>>
>> I have a SATA backup drive formatted gpt, one partition, xfs. I went into gparted, erased the partition, recreated the partition as ext4 and formatted it as ext4.
>>
>> Then I mounted it as ext4, copied some files to it, unmounted it. When I went to remount it, mount told me there was something wrong with ext4.
>
> What "something" was that?
mount: /lin-bak: wrong fs type, bad option, bad superblock on /dev/sdd1,
missing codepage or helper program, or other error.
>
>> So I mounted it as xfs AND IT WORKED! I repeated with the same result. The drive thinks it is ext4 until the second mount.
>
> This should not be the case. It's possible to leave old magic numbers & signatures lying around in general, but mkfs.ext4, in my testing, zeros out the XFS superblock at offset 0; xfs should fail to mount after that. It sounds like there may be more going on, here.
I have notices issues in the past with gparted. It use to not
format an ntfs partition that Windows recognized. Now
it can't label and ntfs partition that Windows also recognized.
But these were usually relegated to Windows problems.
I would love it if gparted would FINALLY support luks.
>> Out of shear frustration, I did a dd /dev/zero overwrite of the stinker and left it running overnight. That did the trick, but it takes
>> forever and I have four more drives to go.
>>
>> What is the official way to remove an xfs partition?
>
> It's not usually needed, but if you don't want the kernel and/or utilities to recognize an xfs block device as xfs anymore, simply zero the first 512 bytes of that block device.
I can do that!
I was concerned about the gpt stuff at the end of the drive.
Ignored if I clobber the first 512 bytes?
> Or more conveniently, there's also the wipefs utility:
>
> NAME
> wipefs - wipe a signature from a device
Didn't know about that one. Thank you!
-T
> -Eric
>
next prev parent reply other threads:[~2017-08-31 18:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 18:04 What is the proper way to remove an xfs partition? ToddAndMargo
2017-08-31 18:16 ` Eric Sandeen
2017-08-31 18:32 ` ToddAndMargo [this message]
2017-08-31 21:09 ` Eric Sandeen
2017-09-01 7:02 ` Carlos Maiolino
2017-09-02 0:34 ` ToddAndMargo
2017-09-03 12:34 ` Carlos E. R.
2017-09-04 0:03 ` ToddAndMargo
2017-09-04 0:14 ` Carlos E. R.
2017-09-04 5:06 ` ToddAndMargo
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=a1e12c3c-5238-e319-e2ea-982606e808b3@zoho.com \
--to=toddandmargo@zoho.com \
--cc=linux-xfs@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