![]() This is what btrfs uses to keep track of what belongs where. Or just zero out the device as you were going to anyway as it didn't try to mount the device, just told you there's a duplicate UUID.īlkid will show you all the UUID, UUID_SUB stuff. You would use wipefs on the device, which will tell you what signatures have been found, and then wipe them all with wipefs -a on the device. The tool for wiping device signatures including btrfs ones is wipefs. The problem would be at mount time (or with the filesystem present in fstab but not mounted) if you have two filesystems with the same UUID - it may try to mount the wrong fs, which could be dangerous. It's just a warning because you've plugged in a device which has the same UUID as your volume, but it will not have a UUID_SUB the fs knows about, so isn't part of it. (you can check what's in which volume using btrfs fi show -d). Nothing to worry about, replace will have removed that device from your array already. Is there a way to prevent BTRFS from automatically attempting to mount a drive as soon as it is attached?.What is the recommended way to wipe just the tiny part of the drive that contains the UUID etc that identifes it to the system as part of a btrfs volume? (It was used as a raw drive in the btrfs volume).Is this just a warning, causing btrfs to simply ignore this duplicate? Could this have damaged the integrity of my btrfs volume in any way?.This resulted in syslog showing the following error: kernel: BTRFS warning: duplicate device /dev/sdg devid 5 generation nnnnnn scanned by systemd-udevd (nnnnnn) ![]() Just now, I attached that failing drive to the same machine via a USB HDD dock, so that I can zero out the drive prior to disposing of it. I recently had a failing disk with SMART errors in my RAID 1 btrfs volume, so I removed it and swapped it out for a new drive and did a btrfs replace.
0 Comments
Leave a Reply. |