11

A week ago, I created a BTRFS pool using two flash drives (32GB each) with this command: /sbin/mkfs.btrfs -d single /dev/sda /dev/sdb. Then I realized that I should have used the partitions /dev/sda1 and /dev/sdb1, instead of the disks /dev/sda and /dev/sdb, so I recreated the volumes using /dev/sd[ab]1.

My problem is that now I have two volumes:

$ sudo btrfs fi show
Label: none  uuid: ba0b48ce-c729-4793-bd99-90764888851f
        Total devices 2 FS bytes used 28.00KB
        devid    2 size 29.28GB used 1.01GB path /dev/sdb1
        devid    1 size 28.98GB used 1.03GB path /dev/sda1

Label: none  uuid: 17020004-8832-42fe-8243-c145879a3d6a
        Total devices 2 FS bytes used 288.00KB
        devid    1 size 29.28GB used 1.03GB path /dev/sdb
        devid    2 size 28.98GB used 1.01GB path /dev/sda

I've tried different options in order to delete the second volume (uuid ending in c145879a3d6a), ie: using btrfs delete device. Then mkfs.btrfs, unmounted the devices and also fdisk in order to recreate the whole raid from scratch, but no matter what I do, btrfs fi show still shows both volumes. How can I completely remove these volumes from my system and start everything from scratch? No matter what I do the volumes can't be removed, ie:

$ sudo btrfs device delete /dev/sda /media/flashdrive/
ERROR: error removing the device '/dev/sda' - Inappropriate ioctl for device

I'm running here kernel 3.12.21 + btrfs v0.19

HopelessN00b
  • 53,385
  • 32
  • 133
  • 208
limaunion
  • 111
  • 1
  • 1
  • 3

4 Answers4

8

I've run into similar issues myself using BTRFS.

First things first -- butter doesn't need to be in a partition, so unless there was some kind of unmentioned reason that you wanted it in /dev/sdb1, you did exactly what I did and ran into exactly the same problem.

After digging around and trying to find a clean solution to fixing it, wipefs is your best option -- supposedly newer versions can remove all traces. However, at the time I ran into this, I ended up just using dd to write zeros to my entire device, something like the following:

dd if=/dev/zero of=/dev/sdX bs=4M

It's the 9000 pound gorilla of solutions, but it will put your thumbdrives back to a fresh state.

SSD Warning: This might be harmful to the performance of an SSD (depending on the manufacturer) and should really only be done on thumbdrives. See this question which offers up some other alternatives (blkdiscard) that might be faster/safer/better for SSDs. This question also has some good answers that might do the equiv of this but without zeroing (secure erase feature).

Community
  • 1
  • Thanks Nextraztus! that seems to have solved the problem! I'll recreate them now from scratch. Hope this is fixed in future btrfs versions. – limaunion Jun 19 '14 at 17:01
4
sudo wipefs --all -t btrfs /dev/sda /dev/sdb

worked for me. I had to add --all to have sudo btrfs fi show turn up empty.

-a, --all

Erase all available signatures. The set of erased signatures can be restricted with the -t option.

Array/Btrfs was created with sudo mkfs.btrfs --label btrfs_6TB_RAID1 --metadata raid1 --data raid1 /dev/sda /dev/sdb --force

See wipefs documentation

user319436
  • 41
  • 2
3

I'd prefere wipefs -t btrfs /dev/sda1 /dev/sdb1 as suggested in official btrfs wiki. It's a bit hidden in the description of mkfs-option:

-f --force Forcibly overwrite the block devices when an existing filesystem is detected. By default, mkfs.btrfs will utilize libblkid to check for any known filesystem on the devices. Alternatively you can use the wipefs utility to clear the devices.

user421075
  • 31
  • 1
  • I'm not sure why this is recommended rather than just using the flag you've quoted...I just tried it and `mkfs.btrfs -f` worked fine to delete the old filesystem and generate a new one, though it's certainly a bit unintuitive that you must create the desired partition table *first*, *then* erase it...but it was Still, certainly much quicker than zero-ing the whole device. – ghostly_s Feb 22 '22 at 20:44
0

As an alternative you could use cryptsetup to wipe the btrfs informations:

cryptsetup -c aes-cbc-essiv:sha256 -y -s 256 luksFormat /dev/sdXY

Worked for me.

jaltek
  • 283
  • 3
  • 9