From: Hugo Mills <hugo@carfax.org.uk>
To: "Kengo.M" <kengo@kyoto-arc.or.jp>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: delete whole file system
Date: Tue, 6 Sep 2022 10:12:03 +0100 [thread overview]
Message-ID: <20220906091203.GY1103@savella.carfax.org.uk> (raw)
In-Reply-To: <p0600104adf3cb2552d24@kyoto-arc.or.jp>
On Tue, Sep 06, 2022 at 05:59:21PM +0900, Kengo.M wrote:
> Hi folks
>
> I made raid5 file system by btrfs like below
>
> sudo mkfs.btrfs -L raid5.btrfs -d raid5 -m raid1 -f /dev/sda /dev/sdb
> /dev/sdc /dev/sdd /dev/sde
>
> And mount /mnt/raid5.btrfs
>
> sudo btrfs filesystem show
>
> Label: 'raid5.btrf' uuid: 23a34a45-8f5e-40f5-8cda-xxxxxxxxxxxx
> Total devices 5 FS bytes used 128.00KiB
> devid 1 size 2.73TiB used 1.13GiB path /dev/sda
> devid 2 size 2.73TiB used 1.13GiB path /dev/sdb
> devid 3 size 2.73TiB used 1.13GiB path /dev/sdc
> devid 4 size 2.73TiB used 1.13GiB path /dev/sdd
> devid 5 size 2.73TiB used 1.13GiB path /dev/sde
>
>
> So,I want to delete this file system.
>
> btrfs device delete /dev/sda /mnt/raid5.btrfs
>
> But delete /dev/sda only.
>
> Please Someone tell me how to delete whole this file system.
>
> BRD
>
> Kengo.m
"btrfs dev delete" remove a device from the SF leaving the rest of
it intact. To destroy the filesystem completely, wipe the start of the
device on each device. You can do that with any tool that will write
data (dd if=/dev/zero is a popular one here), but there's a generic
tool called wipefs that will do it for any filesystem with minimal
writes to the device and a good level of recoverability if you get it
wrong.
Hugo.
--
Hugo Mills | Klytus, I'm bored. What plaything can you offer me
hugo@... carfax.org.uk | today?
http://carfax.org.uk/ |
PGP: E2AB1DE4 | Ming the Merciless, Flash Gordon
next prev parent reply other threads:[~2022-09-06 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fb056073-5bd6-6143-9699-4a5af1bd496d@zoho.com>
[not found] ` <655f97cc-64e6-9f57-5394-58f9c3b83a6f@gmx.com>
[not found] ` <40b209eb-9048-da0c-e776-5e143ab38571@zoho.com>
[not found] ` <72a78cc 0-4524-47e7-803c-7d094b8713ee@gmx.com>
[not found] ` <72a78cc0-4524-47e7-803c-7d094b8713ee@gmx.com>
[not found] ` <00984321-3006-764d-c29e-1304f89652ae@zoho.com>
[not found] ` <18300547-1811-e9da-252e-f9476dca078c@gmx.com>
[not found] ` <4691b710-3d71-bd 26-d00a-66cc398f57c5@zoho.com>
[not found] ` <4691b710-3d71-bd26-d00a-66cc398f57c5@zoho.com>
2022-08-16 5:38 ` some help for improvement in btrfs Qu Wenruo
2022-09-06 8:02 ` hmsjwzb
2022-09-06 8:37 ` Qu Wenruo
2022-09-07 8:24 ` hmsjwzb
2022-09-07 8:46 ` Qu Wenruo
2022-09-08 9:21 ` hmsjwzb
2022-09-08 9:28 ` Qu Wenruo
2022-09-06 8:59 ` delete whole file system Kengo.M
2022-09-06 9:12 ` Hugo Mills [this message]
2022-09-06 10:28 ` Kengo.M
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=20220906091203.GY1103@savella.carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=kengo@kyoto-arc.or.jp \
--cc=linux-btrfs@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