Difference between revisions of "Talk:Persistent block device naming"

From ArchWiki
Jump to navigation Jump to search
m (→‎Using persistent naming > Boot managers: remove closed discussion)
 
(30 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== by-path and by-id unsuitable? ==
+
== systemd-boot entry with label ==
  
the article says by-path is unsuitable because it "contain[s] strings to indicate which subsystem they belong to (i.e. "-ide-", for 'by-path', and "ata-" for 'by-id')"
+
Should we add a systemd-boot entry using LABEL to the bottom section? --[[User:Betseg|Betseg]] ([[User talk:Betseg|talk]]) 15:17, 29 July 2015 (UTC)
  
How does that make it unsuitable? For by-path, that string is the same each boot, because the bus doesn't move (even if the buses get initialized in a different order) -- e.g. suppose you've got two SATA disks, on SATA connector #1 and #2 on your motherboard. #1 may become /dev/sda on one boot, and /dev/sdb the next time. Its by-path name won't change, though -- /dev/disk/by-path/sata-1 will point to /dev/sda in the first case and /dev/sdb in the second case, so it's persistent.
+
:Could do, but it might also be worthwhile to consider slim down that section and crosslink more instead. Or, as a first step, you could convert the LABEL example at the end to a systemd-boot one and crosslink it to [[Systemd-boot#Standard root installations]] for the additional info there. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 20:35, 29 July 2015 (UTC)
  
Furthermore, by-path is actually safer than by-label and by-uuid, because those rely on the disk data to identify the disk. Suppose you and a friend both named your boot drive "root". Your friend's power supply blows, so you plug his drive into your eSATA port to retrieve some data for him -- but oops, your system found his "root" label before yours, and suddenly you're trying to boot to the wrong disk. (I've actually tested this, and it can/does happen. It's most likely to happen when something is wrong, e.g. one of your drives is dying -- which is also when you least *want* it to happen.)
+
::Plus, there is already [[Kernel parameters#Configuration]]. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 06:20, 30 July 2015 (UTC)
 
 
[[User:Thetrivialstuff|Thetrivialstuff]] 01:04, 13 August 2011 (EDT)
 
 
 
: I am also confused by that statement in the article with respect to "by-id". E.g. elsewhere I see:
 
: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Online_Storage_Reconfiguration_Guide/persistent_naming.html
 
:: The World Wide Identifier (WWID) can be used in reliably identifying devices. It is a persistent, system-independent ID that the SCSI Standard requires from all SCSI devices. '''The WWID identifier is guaranteed to be unique for every storage device, and independent of the path that is used to access the device.'''
 
:: This identifier can be obtained by issuing a SCSI Inquiry to retrieve the Device Identification Vital Product Data (page 0x83) or Unit Serial Number (page 0x80). The mappings from these WWIDs to the current /dev/sd names can be seen in the symlinks maintained in the /dev/disk/by-id/ directory.
 
:: For example, a device with a page 0x83 identifier would have:
 
 
 
:: scsi-3600508b400105e210000900000490000 -> ../../sda
 
 
 
:: Or, a device with a page 0x80 identifier would have:
 
 
 
:: scsi-SSEAGATE_ST373453LW_3HW1RHM6 -> ../../sda
 
 
 
:: Red Hat Enterprise Linux 5 automatically maintains the proper mapping from the WWID-based device name to a current /dev/sd name on that system. '''Applications can use the /dev/disk/by-id/ name to reference the data on the disk, even if the path to the device changes, and even when accessing the device from different systems. '''
 
: Am I missing something?
 
: [[User:Goulo|Goulo]] 04:42, 11 January 2012 (EST)
 
:: I don't know if this could be relevant, at least in the context of using by-id with GRUB on BIOS computers: https://savannah.gnu.org/bugs/index.php?35354#comment3 --[[User:Kit|Kit]] ([[User talk:Kit|talk]]) 17:49, 25 October 2012 (UTC)
 
 
 
It seems to me that /dev/disk/by-id is a perfectly suitable for persistent block device naming, since it is guaranteed to uniquely identify a device and is agnostic to varying assignment of device node names and, in most cases, to which system bus the device is attached. I can see further problems with this article. '''Neither disk nor partition labels can be guaranteed to be unique across a system.''' Indeed, some file systems, notably btrfs and ZFS, will (quite legitimately) assign the same labels to disks and partitions under their control. In such a setup, /dev/disk/by-label and /dev/disk/by-partlabel '''cannot''' be used.
 
[[User:DPiergies|DPiergies]] ([[User talk:DPiergies|talk]]) 23:25, 13 May 2015 (UTC)
 

Latest revision as of 15:57, 17 March 2018

systemd-boot entry with label

Should we add a systemd-boot entry using LABEL to the bottom section? --Betseg (talk) 15:17, 29 July 2015 (UTC)

Could do, but it might also be worthwhile to consider slim down that section and crosslink more instead. Or, as a first step, you could convert the LABEL example at the end to a systemd-boot one and crosslink it to Systemd-boot#Standard root installations for the additional info there. --Indigo (talk) 20:35, 29 July 2015 (UTC)
Plus, there is already Kernel parameters#Configuration. -- Lahwaacz (talk) 06:20, 30 July 2015 (UTC)