From: Thomas Mueller <thomas@chaschperli.ch>
To: ceph-devel@vger.kernel.org
Subject: Re: use UUID mount btrfs failed
Date: Wed, 12 Oct 2011 10:28:18 +0200 [thread overview]
Message-ID: <j73j32$6fs$1@dough.gmane.org> (raw)
In-Reply-To: <CABAwU-bS7gZscTkDUDTzBetSZ_v1GgQtcr0rH3VTa8Xj3ETTpA@mail.gmail.com>
On 12.10.2011 10:22, huang jun wrote:
> 2011/10/12 Damien Churchill<damoxc@gmail.com>:
>> On 12 October 2011 02:22, huang jun<hjwsm1989@gmail.com> wrote:
>>> I use the UUID option to mount the btrfs disk,but i can not success.
>>> first, the disk is /dev/sdd1
>>> then, i pull out the disk
>>> and after mintues, pushed it again,at this time, it changes to /dev/sde1
>>> at this time, if we use /etc/init.d/ceph restart, it will failed, for
>>> the current mount option is likely "/dev/sd** "
>>> but the UUID didn't change.
>>> why i can not mount it successfuly?
>>> BTW, does ceph provides methods to resolve the condition like that?
>>>
>>> the starce file attached.
>>>
>>> thanks!
>>>
>>
>> Hi,
>>
>> I switched to use the symlinks created by udev in /dev/disk/by-id/
>> which contains the hard-disks serial number which will be completely
>> static, even if a new btrfs filesystem is created. This ensures that
>> the same partition on the same disk is always used.
>>
>> Regards,
>> Damien
>>
> can you mount successfully by using the /dev/disk/by-id/ instead of /dev/sd**?
> and how to get the hard-disk serial number? I have tried "udevadm info
> -a -p $(udevadm info -q path -n $btrfs_devs)", but failed to get it.
> or you should test the condition like that, pull out the disk first
> and then push it in after few minutes.
>
> thanks!
for example with smartctl from the smartmontools you can get the s/n.
smartctl -i /dev/sd*
- Thomas
next prev parent reply other threads:[~2011-10-12 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 1:22 use UUID mount btrfs failed huang jun
2011-10-12 8:02 ` Damien Churchill
2011-10-12 8:22 ` huang jun
2011-10-12 8:28 ` Thomas Mueller [this message]
2011-10-12 8:40 ` huang jun
2011-10-12 16:03 ` Sage Weil
2011-10-13 0:03 ` huang jun
2011-10-12 8:38 ` Damien Churchill
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='j73j32$6fs$1@dough.gmane.org' \
--to=thomas@chaschperli.ch \
--cc=ceph-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.