On Thu, Jun 13, 2013 at 2:55 PM, Autif Khan <autif.mlist@xxxxxxxxx> wrote: > Hi, > > We are using /dev/disk/by-label/OURLABEL to mount USB disk partitions. > > We were using Ubuntu 12.04 with 1.42 version of e2fsprogs - where we > encountered SSD corruption issues on unclean powerdown. It was > suggested that we upgrade to the latest e2fsprogs > (http://marc.info/?l=linux-ext4&m=137035378614543&w=2). > > After the upgrade to 1.42.7, we do not have /dev/disk/by-label > > I am not sure if this is the right place to ask this - but I thought > that I should start here and ask in udev mailing list later - (that > whole thing about correlation mumble causation). > > I am still researching how /dev/disk/by-label comes into existence - > please advice if there is something obvious that I am missing. > Thanks djwong#ext4 for all the help on IRC It seems like blkid -o udev /dev/sdb1 displays info about the volume - which is used by udev rules to populates /dev/disk/by-label The output when e2fsprogs version 1.42 was used: ubuntu@mac0013950af6fb:/lib/udev/rules.d$ sudo blkid -o udev -p /dev/sdb1 ID_FS_LABEL=KOKO ID_FS_LABEL_ENC=KOKO ID_FS_UUID=56D8-F5EE ID_FS_UUID_ENC=56D8-F5EE ID_FS_VERSION=FAT32 ID_FS_TYPE=vfat ID_FS_USAGE=filesystem ID_PART_ENTRY_SCHEME=dos ID_PART_ENTRY_TYPE=0xb ID_PART_ENTRY_FLAGS=0x80 ID_PART_ENTRY_NUMBER=1 ID_PART_ENTRY_OFFSET=32 ID_PART_ENTRY_SIZE=251616 ID_PART_ENTRY_DISK=8:16 The output when e2fsprogs version 1.42.7 was used: ubuntu@mac001395089897:~$ sudo blkid -o udev /dev/sda1 Invalid output format udev. Choose from value, device, list, or full BTW, sudo blkid -o full /dev/sdb1 worked just fine - had the LABEL and everything. Also - looks like 1.42.7 does not support the -p option. From the man page: -p Switch to low-level superblock probing mode (bypass cache). Is there a configuration option that will allow blkid to display udev output formats? I could not find with ./configure --help Thanks Autif -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
