Assignment of device names to external USB drives
Mikhail Goriachev
mikhailg at webanoide.org
Wed May 23 00:10:13 UTC 2007
illoai at gmail.com wrote:
> On 19/05/07, Kevin Downey <redchin at gmail.com> wrote:
>> On 5/19/07, Denis Fortin <fortin at acm.org> wrote:
>>> Greetings,
>>>
>>> I am trying to set up a backup server, using a combination of internal
>>> and external (USB) disk drives.
>>>
>>> How can I manage the mapping of USB disk drives to device names? i.e.
>>> USB drives get assigned device names like da0, da1, da2... when they are
>>> detected. But if one of the drives fails or is not powered up, all
>>> other ones will get bumped down one in the list next time I reboot.
>>>
>>> The problem is that if I automatically "mount /dev/da0a
>>> /archive/volume1", "mount /dev/da1a /archive/volume2", etc. I run the
>>> risk of having the wrong disk being mounted on a mount point !?!
>>>
>>> Is there an obvious solution that I'm missing, or a canonical workaround
>>> to this problem?
>>>
>> when you newfs a drive use the -L flag to give it a label like
>> 'VOLUME1' then if you load the geom_label module that drive becomes
>> availble under /dev/ufs/VOLUME1
>
> Or, if instead of fdisk, you
> # glabel label disk0 da0
> # bsdlabel -w label/fancy0
> # newfs -U label/fancy0a
> # mount /dev/label/fancy0a /bla
>
In addition, you can modify an already created filesystem (as described
in glabel(8)):
# tunefs -L data /dev/da4s1a
Read the glabel(8) and loader.conf(5) man pages.
Regards,
Mikhail.
--
Mikhail Goriachev
Webanoide
Telephone: +61 (0)3 62252501
Mobile Phone: +61 (0)4 38255158
E-Mail: mikhailg at webanoide.org
Web: www.webanoide.org
More information about the freebsd-questions
mailing list