From: Corey Coughlin <corey.coughlin.cc3@gmail.com>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: raid1 has failing disks, but smart is clear
Date: Thu, 7 Jul 2016 21:51:40 -0700 [thread overview]
Message-ID: <577F315C.8080509@gmail.com> (raw)
In-Reply-To: <pan$90586$9ef8a2d7$381c8c69$44837006@cox.net>
Hi Duncan,
Thanks for the info! I've seen that done in the fstab, but it
didn't work for me the last time I tried it on the command line. Worth a
shot!
------ Corey
On 07/07/2016 06:24 PM, Duncan wrote:
> 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.
>
> Of course because the identifiers behind by-uuid and by-label are per-
> filesystem, those will normally only identify the one device of a multi-
> device filesystem, but the by-id links ID on device serials and partition
> number, and if you are using GPT partitioning, you have by-partuuid and
> (if you set them when setting up the partitions) by-partlabel as well.
>
next prev parent reply other threads:[~2016-07-08 4:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 22:14 raid1 has failing disks, but smart is clear Corey Coughlin
2016-07-06 22:59 ` Tomasz Kusmierz
2016-07-07 6:40 ` Corey Coughlin
2016-07-08 1:24 ` Duncan
2016-07-08 4:51 ` Corey Coughlin [this message]
2016-07-09 5:51 ` Andrei Borzenkov
2016-07-09 5:40 ` Andrei Borzenkov
2016-07-12 4:50 ` Corey Coughlin
2016-07-07 11:58 ` Austin S. Hemmelgarn
2016-07-08 4:50 ` Corey Coughlin
2016-07-08 11:14 ` Tomasz Kusmierz
2016-07-08 12:14 ` Austin S. Hemmelgarn
2016-07-09 5:13 ` Corey Coughlin
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=577F315C.8080509@gmail.com \
--to=corey.coughlin.cc3@gmail.com \
--cc=1i5t5.duncan@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).