fdisk -l and lsblk - how to compare these two commands?


Recommended Posts

Hello and good morning dear community,


So from time to time I'm on the console more or less.

And if you don't always use it - if you're not at home every day - then questions keep coming up - which an experienced Linux user probably never comes up with.

In any case, the question arises for me - how to compare lsblk and fdisk -l - how and what possible errors can arise when using them.

Background: When comparing lsblk and fdisk -l, I sometimes wondered which was better and more suitable

hmmm - I think that lsblk is actually better suited for a quick, clear display
With lsblk I get the data of the contents on the drive with their structure, including mount points and logical volumes.

Seen this way, I find lsblk a bit easier – more readable and clearer

In my opinion, lsblk shows a tree-like structure showing the disk, partitions, partition types, volume groups and logical volumes. (while fdisk -l (disk) only shows the partition and partition type present on the disk.... hmmm - if it is an MBR style disk.)

How do you see that!?

I'm looking forward to hearing from you

cheers

 

update:

 

btw: i have found - with some research  a thread that might help here:

https://stackoverflow.com/questions/67124677/why-fdisk-and-lsblk-show-different-partition-size

what do you think!?

 

Well, it's the same with comparing top to htop. Or GIMP to Krita.

They give out the same info/usage.

Saying something is "best" doesn't mean it's best for the next person.

And showing different partition sizes, right in that link:

"lsblk shows size in IEC units (GiB, MiB, etc). A gibibyte (GiB) is larger than a gigabyte (GB)
fdisk shows size in SI (GB, MB, etc)."

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Free Software Foundation Europe pushes EU to force Google to allow AI uninstalls on Android by Paul Hill Credit: Pexels Users should be able to fully uninstall AI-based features from Android devices and be able to access interoperability functions, free from Google’s verification requirements, the European Commission has heard as part of an Android interoperability consultation under the Digital Markets Act. These measures were proposed by the Free Software Foundation Europe (FSFE) last week when it submitted its documentation. The FSFE noted that Google had started silently installing AI models without telling users. It noted that the EU’s DMA requires companies like Google to allow users to uninstall pre-loaded software from their devices, but in the case of the AI models Google is installing, they reinstall if you delete them, contravening the DMA. To get Google back under control, the FSFE has told the European Commission that there needs to be improvements within the Android Open Source Project (AOSP). First, it said that users should be able to fully remove pre-loaded AI components from their devices, with companies being prohibited from silently reinstalling or reactivating them. Second, access to Android interoperability features should not be contingent on registration, authorization, or contractual relationships with Google. This pertains to Google’s attempt to force developers to register with Google, even to publish apps to alternative app stores like F-Droid. Discussing its submission, Lucas Lasota, FSFE Legal Programme Manager, said: Google is planning to roll out its Android Developer Certification in September 2026. This will force every Android app developer to register with Google before their software can be installed on certified Android devices, but it should affect those who have removed Google Apps from their device. The program is controversial because it entails the signing of contracts and payment of account fees to Google, as well as the handing over of the identities of developers. It said: The FSFE said that if the Commission’s draft measures remain unchanged, then Google will be allowed to make developers verify their identity. The FSFE believes that asking developers to register is contrary to the text and spirit of the law. In summary, the FSFE has told the Commission that no developer should need a Google account, a Play Store presence, or any agreement with Google to access Android’s interoperability features.
    • You could disable this "functionality/feature/whatever" with 2 registry keys, ages ago.
    • My Photos app is version 2026.11050.1001.0 and it remembers the window size and position. My Snipping Tool is version 11.2602.49.0 and it can capture the taskbar.
  • Recent Achievements

    • Conversation Starter
      sumytbe earned a badge
      Conversation Starter
    • One Year In
      B4dM1k3 earned a badge
      One Year In
    • One Year In
      DarkWun earned a badge
      One Year In
    • Dedicated
      Almohandis earned a badge
      Dedicated
    • Dedicated
      JuvenileDelinquent earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      519
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      87
    4. 4
      Michael Scrip
      81
    5. 5
      Steven P.
      72
  • Tell a friend

    Love Neowin? Tell a friend!