Re: Where do I find the definitive man page for mdadm?
On Sat 13 Nov 2021 at 18:37:34 (-0500), Greg Wooledge wrote:
> On Sat, Nov 13, 2021 at 04:06:43PM -0700, Charles Curley wrote:
> >
> > Gene, the answer is, anythng the TYPE of which is a valid file system.
> > Try, e.g.:
> >
> > blkid | grep -E -i \(ext\|ntfs\|fat\)
>
> lsblk is a lot easier and prettier for this purpose.
>
> unicorn:~$ sudo lsblk -o +UUID
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID
> sda 8:0 0 931.5G 0 disk
> ├─sda1 8:1 0 260M 0 part /boot/efi 4C30-7972
> ├─sda2 8:2 0 16M 0 part
> ├─sda3 8:3 0 92.2G 0 part 7294B93794B8FEA3
> ├─sda4 8:4 0 980M 0 part 609E71C79E71966E
> ├─sda5 8:5 0 11.5G 0 part 6858F6A458F66FE4
> ├─sda6 8:6 0 11.2G 0 part [SWAP] 08c87bdb-17f4-40ab-9b2f-5cb2f29149fb
> ├─sda7 8:7 0 23.3G 0 part / c4691ccb-2090-491e-8e82-d7cc822db04a
> ├─sda8 8:8 0 23.3G 0 part /home 19fb397b-a113-4536-a03d-d60e176cbfdf
> └─sda9 8:9 0 651.9G 0 part /stuff 95058c4a-44e2-4a90-87b5-2a5fe40d3cdb
> sr0 11:0 1 418.7M 0 rom
You shouldn't require root for either blkid or lsblk,
though the former needs a path, and does include a
warning that the information may be read from cache.
One question about lsblk, though: why does it always
use the xterm width to format the output, regardless of
whether you redirect the output and the value of COLUMNS.
Is there a workaround beyond resizing the window?
Cheers,
David.
Reply to: