search for: lsblk

...ide a traditional Unix > would return, ie. a list of mounted filesystems backed by real > devices, plus swap. > > That's not an exact definition. A better way to understand it might > be to look at how it is is used (ie. ‘git grep list[-_]filesystems’). Isn't more like 'lsblk' rather than 'df'? Because 'df' is useless with unmounted file systems where is 'lsblk' discovers all available block devices. -- Mykola Ivanets

...;s important to distinguish between verbatim/pasteable and what the old-writer merely thinks/remembers. I want to be able to boot ANY installation/partition as I vaguely remember I could do with the old USBstik. > To mount /, the initramfs needs to know the partition's name reported > by lsblk, that you'd give as a kernel parameter in the command line, as > said by message.txt. In the limiting case, there's only the 4 partitons of M$pook & stkA & stikB, which gives only 3 sdX1 to test BLINDLY. > But that also needs a kernel driver to handle the USB adapter. There...

The following patch attempts to implement sparsification of LUKS-encrypted partitions. It uses lsblk to pair the underlying LUKS block device with its mapped name. Also, --allow-discards was added by default to luks_open(). There are several potential issues that I can think of: 1) If and entire device is encrypted (not just one of more partitions), the lsblk trick might not work. 2) The --allo...

Yes this is the SAME question, that I can't get an answer from a month ago! I have the files, from a USBstik [now stolen] which I previously could edit at boot time, to boot any of my IDE or SATA partitions. Now, with a laptop, I want to boot the same IDE or SATA via a USB-adaptor to IDE/SATA. And also I want to boot a Toshiba 500GB USB disk. The obvious question is: why [if] the old system

..."the discard operation is not supported" fstrim error when the LVs are set to "nopassdown" Seems that when I use ext4 the fstrim reports that it worked but the LVs Data% does not decrease after the fstrim. xfs just throws the error. I've also been looking at the output of lsblk -D # lsblk -D NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO xvdb 0 0B 0B 0 ??data-pool00_tmeta 0 0B 0B 0 ? ??data-pool00-tpool 0 0B 0B 0 ? ??data-pool00 0 0B...

...ect is off [155484.391556] sd 0:0:1:0: [sdb] Mode Sense: 61 00 00 00 [155484.391593] sd 0:0:1:0: [sdb] Cache data unavailable [155484.391595] sd 0:0:1:0: [sdb] Assuming drive cache: write through [155484.396148] sdb: unknown partition table [155484.396356] sd 0:0:1:0: [sdb] Attached SCSI disk and lsblk shows... # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 32G 0 disk .... sdb 8:16 0 16G 0 disk ... so I can immediately... # mkfs.xfs /dev/sdb meta-data=/dev/sdb isize=256 agcount=4, agsiz...

I would like to have a smart cli tool, that shows a comprehensive list about the local storage structure: An output like: /srv /dev/mapper/luks-f85b7a2c-...: UUID="ca924fad-..." TYPE="ext4" /dev/mapper/vg_internal_e-lv_internal_srv: UUID="f85b7a2c-..." TYPE="crypto_LUKS" vg_internal_e /dev/md3: UUID="1Fi2Ex-..."

...ese are also containers, as above. *) - else if vfs_type = "crypto_LUKS" then - None + (* If a LUKS-encrypted partition had been opened, include the corresponding + * device mapper filesystem path. *) + else if vfs_type = "crypto_LUKS" then ( + let out = command "lsblk" ["-n"; "-l"; "-o"; "NAME"; device] in + (* Example output: #lsblk -n -l -o NAME /dev/sda5 + * sda5 + * lukssda5 + *) + match String.trimr @@ snd @@ String.split "\n" out with + | "" -> None +...

On Tue, Jan 21, 2020 at 03:07:11PM +0100, Jan Synacek wrote: > The following patch attempts to implement sparsification of > LUKS-encrypted partitions. It uses lsblk to pair the underlying LUKS > block device with its mapped name. Also, --allow-discards was added > by default to luks_open(). > > There are several potential issues that I can think of: > > 1) If and entire device is encrypted (not just one of more partitions), > the lsblk t...

On Thu, May 28, 2020 19:38, Robert Nichols wrote: > What output do you get from: > > file -s /dev/mapper/vg_voinet01-lv_log > lsblk -f /dev/mapper/vg_voinet01-lv_log > file -s /dev/mapper/vg_voinet01-lv_log /dev/mapper/vg_voinet01-lv_log: symbolic link TO '../DM-5' dm-f lsblk -f /dev/mapper/vg_voinet01-lv_log NAME FSTYPE LABEL UUID MOUNTPOINT vg_voinet01-lv_log (dm-5) The cloned source is a C...

Short of backing up entire disks using dd, I'd like to collect all required information to make sure I can restore partitions, disk information, UUIDs and anything else required in the event of losing a disk. So far I am collecting information from: - fdisk -l - blkid - lsblk - grub2-efi.cfg - grub - fstab Hoping that this would supply me with /all/ information to restore a system - with the exception of installed operating system, apps and data. I would appreciate any and all thoughts on the above!

...0:0:1:0: [sdb] Mode Sense: 61 00 00 00 > [155484.391593] sd 0:0:1:0: [sdb] Cache data unavailable > [155484.391595] sd 0:0:1:0: [sdb] Assuming drive cache: write through > [155484.396148] sdb: unknown partition table > [155484.396356] sd 0:0:1:0: [sdb] Attached SCSI disk > > and lsblk shows... > > # lsblk > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:0 0 32G 0 disk > .... > sdb 8:16 0 16G 0 disk > ... > > so I can immediately... > > # mkfs.xfs /dev/sdb > meta-...

Hi, I just replaced Slackware64 14.1 running on my office's HP Proliant Microserver with a fresh installation of CentOS 7. The server has 4 x 250 GB disks. Every disk is configured like this : * 200 MB /dev/sdX1 for /boot * 4 GB /dev/sdX2 for swap * 248 GB /dev/sdX3 for / There are supposed to be no spare devices. /boot and swap are all supposed to be assembled in RAID level 1 across

Boris Epstein wrote: >> >> My turn for a dumb question: from not paying a lot of attention to this >> thread, the answer isn't clear to me: has the *host* recognized the >> disk? If not, the guest's not going to see it. > > IMO your question is not dumb at all. Unfortunately, I don't have an > answer to it. > > All I know is, you reboot the VM and

...entire disks using dd, I'd like to collect all required information to make sure I can restore partitions, disk information, UUIDs and anything else required in the event of losing a disk. >> >> So far I am collecting information from: >> - fdisk -l >> - blkid >> - lsblk >> - grub2-efi.cfg >> - grub >> - fstab >> >> Hoping that this would supply me with /all/ information to restore a system - with the exception of installed operating system, apps and data. >> >> I would appreciate any and all thoughts on the above! >>...

...ese are also containers, as above. *) - else if vfs_type = "crypto_LUKS" then - None + (* If a LUKS-encrypted partition had been opened, include the corresponding + * device mapper filesystem path. *) + else if vfs_type = "crypto_LUKS" then ( + let out = command "lsblk" ["-n"; "-l"; "-o"; "NAME"; device] in + (* Example output: #lsblk -n -l -o NAME /dev/sda5 + * sda5 + * lukssda5 + *) + match String.trimr @@ snd @@ String.split "\n" out with + | "" -> None +...

...ove. *) > - else if vfs_type = "crypto_LUKS" then > - None > + (* If a LUKS-encrypted partition had been opened, include the corresponding > + * device mapper filesystem path. *) > + else if vfs_type = "crypto_LUKS" then ( > + let out = command "lsblk" ["-n"; "-l"; "-o"; "NAME"; device] in > + (* Example output: #lsblk -n -l -o NAME /dev/sda5 > + * sda5 > + * lukssda5 > + *) > + match String.trimr @@ snd @@ String.split "\n" out with > + |...

Gordon Messmer wrote: > On 7/23/19 11:12 AM, mark wrote: > >> Now, cryptsetup gives me the same UUID as I have in /etc/mdadm.conf. >> The >> entry in /etc/crypttab looks identical to the RAIDs for root and swap, >> but nope. > > > Can you post those files somewhere?? I'm confused by the idea that > cryptsetup is involved in or using the same UUID as an

Hi > On Thu, May 28, 2020 19:38, Robert Nichols wrote: > >> What output do you get from: >> >> file -s /dev/mapper/vg_voinet01-lv_log >> lsblk -f /dev/mapper/vg_voinet01-lv_log >> > > file -s /dev/mapper/vg_voinet01-lv_log > /dev/mapper/vg_voinet01-lv_log: symbolic link TO '../DM-5' > dm-f > > lsblk -f /dev/mapper/vg_voinet01-lv_log > NAME FSTYPE LABEL UUID MOUNTPOINT > vg_voinet0...

Hi All I'm trying to setup my LVM thin pool to support discards so that the pool can reclaim space even if the underlying device doesn't support trim. It is my understanding that all thin pools should support trim even if the underlying device doesn't. (please correct me if I'm wrong here) I have one centos server that does support trim and everything is working correctly but any