From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f46.google.com ([209.85.215.46]:36422 "EHLO mail-lf0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932946AbcGIFvS (ORCPT ); Sat, 9 Jul 2016 01:51:18 -0400 Received: by mail-lf0-f46.google.com with SMTP id q132so39732903lfe.3 for ; Fri, 08 Jul 2016 22:51:17 -0700 (PDT) Subject: Re: raid1 has failing disks, but smart is clear To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org References: <577D82AE.3040005@gmail.com> <03E1A820-7029-4022-9D46-900C4FCA1ADC@gmail.com> <577DF95E.7080100@gmail.com> From: Andrei Borzenkov Message-ID: <578090D2.1080303@gmail.com> Date: Sat, 9 Jul 2016 08:51:14 +0300 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: 08.07.2016 04:24, Duncan пишет: > Corey Coughlin posted on Wed, 06 Jul 2016 23:40:30 -0700 as excerpted: > >> Well yeah, if I was mounting all the disks to different mount points, I >> would definitely use UUIDs to get them mounted. But I haven't seen any >> way to set up a "mkfs.btrfs" command to use UUID or anything else for >> individual drives. Am I missing something? I've been doing a lot of >> googling. > > FWIW, you can use the /dev/disk/by-*/* symlinks (as normally setup by > udev) to reference various devices. > Current udev ships rule that calls equivalent of "btrfs device ready $dev", where $dev is the canonical kernel device name. btrfs kernel driver will update internal list of device names when it gets this ioctl, which means that unless you explicitly pass full list of /dev/disk/by-*/* during mount you will see those kernel names. And even then as soon as device for some reason dis- and re-appears (as is apparently the case here) it will be renamed back by udev when "add" event is seen.