Difference between File system created by fdisk and file system created by mkfs - linuxfile size returned...

Do the temporary hit points from the Battlerager barbarian's Reckless Abandon stack if I make multiple attacks on my turn?

Increase performance creating Mandelbrot set in python

Detecting if an element is found inside a container

Customer Requests (Sometimes) Drive Me Bonkers!

How do I rename a Linux host without needing to reboot for the rename to take effect?

Gears on left are inverse to gears on right?

How to write papers efficiently when English isn't my first language?

Trouble understanding the speech of overseas colleagues

Escape a backup date in a file name

Large drywall patch supports

Would this custom Sorcerer variant that can only learn any verbal-component-only spell be unbalanced?

Proof of work - lottery approach

How do I find the solutions of the following equation?

A particular customize with green line and letters for subfloat

Valid Badminton Score?

What happens if you roll doubles 3 times then land on "Go to jail?"

Roman Numeral Treatment of Suspensions

How to be diplomatic in refusing to write code that breaches the privacy of our users

Why, precisely, is argon used in neutrino experiments?

Why not increase contact surface when reentering the atmosphere?

How to safely derail a train during transit?

Method to test if a number is a perfect power?

How can I kill an app using Terminal?

Short story about space worker geeks who zone out by 'listening' to radiation from stars



Difference between File system created by fdisk and file system created by mkfs - linux


file size returned from ls - Linux vs OS XVMWare performance difference between using physical disk and virtual disk (VMFS)What's the difference between mounted file system and active file system?What is the difference between Ubuntu, Xubuntu, and LubuntuCreating a FAT file system and save it into a file in GNU/linux?Is there a difference between Windows-created NTFS and Gparted-created NTFS?What is the difference between partitioning and formatting a disk?huge difference between the filesystem size and the data size in a .image data. And I cannot shrink itWhy the new hard drive has to be partitioned if I don't need any logical partitions?Difference between UEFI USB Boot and UEFI Hard disk Boot













6















I'm a little bit confused with partitioning the filesystem in Linux.



Please tell me the difference between creating the file system with fdisk and mkfs (when formatting the disk).



I can't clearly tell my problem, so please look at this picture:
enter image description here










share|improve this question

























  • Honestly, just use gparted and save yourself the confusion.

    – user606723
    Aug 1 '11 at 17:00






  • 2





    Well, there're so many tools that I can use to handle these problems. But here I just wanna understand a bit more about the inside =)))

    – Hieu M. Nguyen
    Aug 1 '11 at 17:24











  • In that case, you should've said that in your question. Currently it sounds you're having an issue setting up your partitions.. not that you want to understand whats going on. There is a difference.

    – user606723
    Aug 1 '11 at 17:27
















6















I'm a little bit confused with partitioning the filesystem in Linux.



Please tell me the difference between creating the file system with fdisk and mkfs (when formatting the disk).



I can't clearly tell my problem, so please look at this picture:
enter image description here










share|improve this question

























  • Honestly, just use gparted and save yourself the confusion.

    – user606723
    Aug 1 '11 at 17:00






  • 2





    Well, there're so many tools that I can use to handle these problems. But here I just wanna understand a bit more about the inside =)))

    – Hieu M. Nguyen
    Aug 1 '11 at 17:24











  • In that case, you should've said that in your question. Currently it sounds you're having an issue setting up your partitions.. not that you want to understand whats going on. There is a difference.

    – user606723
    Aug 1 '11 at 17:27














6












6








6


2






I'm a little bit confused with partitioning the filesystem in Linux.



Please tell me the difference between creating the file system with fdisk and mkfs (when formatting the disk).



I can't clearly tell my problem, so please look at this picture:
enter image description here










share|improve this question
















I'm a little bit confused with partitioning the filesystem in Linux.



Please tell me the difference between creating the file system with fdisk and mkfs (when formatting the disk).



I can't clearly tell my problem, so please look at this picture:
enter image description here







linux partitioning filesystems






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 1 '11 at 16:58









Lance Roberts

6,98684175




6,98684175










asked Aug 1 '11 at 16:50









Hieu M. NguyenHieu M. Nguyen

4502613




4502613













  • Honestly, just use gparted and save yourself the confusion.

    – user606723
    Aug 1 '11 at 17:00






  • 2





    Well, there're so many tools that I can use to handle these problems. But here I just wanna understand a bit more about the inside =)))

    – Hieu M. Nguyen
    Aug 1 '11 at 17:24











  • In that case, you should've said that in your question. Currently it sounds you're having an issue setting up your partitions.. not that you want to understand whats going on. There is a difference.

    – user606723
    Aug 1 '11 at 17:27



















  • Honestly, just use gparted and save yourself the confusion.

    – user606723
    Aug 1 '11 at 17:00






  • 2





    Well, there're so many tools that I can use to handle these problems. But here I just wanna understand a bit more about the inside =)))

    – Hieu M. Nguyen
    Aug 1 '11 at 17:24











  • In that case, you should've said that in your question. Currently it sounds you're having an issue setting up your partitions.. not that you want to understand whats going on. There is a difference.

    – user606723
    Aug 1 '11 at 17:27

















Honestly, just use gparted and save yourself the confusion.

– user606723
Aug 1 '11 at 17:00





Honestly, just use gparted and save yourself the confusion.

– user606723
Aug 1 '11 at 17:00




2




2





Well, there're so many tools that I can use to handle these problems. But here I just wanna understand a bit more about the inside =)))

– Hieu M. Nguyen
Aug 1 '11 at 17:24





Well, there're so many tools that I can use to handle these problems. But here I just wanna understand a bit more about the inside =)))

– Hieu M. Nguyen
Aug 1 '11 at 17:24













In that case, you should've said that in your question. Currently it sounds you're having an issue setting up your partitions.. not that you want to understand whats going on. There is a difference.

– user606723
Aug 1 '11 at 17:27





In that case, you should've said that in your question. Currently it sounds you're having an issue setting up your partitions.. not that you want to understand whats going on. There is a difference.

– user606723
Aug 1 '11 at 17:27










3 Answers
3






active

oldest

votes


















14














Fdisk partitions your hard drive. It sets up partitions on the disk by creating a partition table.



mkfs formats the partition after it has been created. It formats it based on a specific filesystem like NTFS, FAT32, Unix ext2 & ext2.



So fdisk isn't really creating a filesystem, it's setting up the hard drive so that a filesystem can be created on it. I'm not sure I see a problem in your picture, did you not want NTFS?






share|improve this answer


























  • So fdisk does not create the file system, right? I use fdisk to create a partition with ext4, ext2,.. types and I use mkfs.ntfs to format the disk. I wonder, which is actually the file system? ext4 or ntfs?

    – Hieu M. Nguyen
    Aug 1 '11 at 17:27








  • 3





    NTFS is the filesystem.

    – Lance Roberts
    Aug 1 '11 at 17:32






  • 1





    @Hieusun2011: if you're familiar with DOS, mkfs in Linux is like FORMAT in DOS, and fdisk in Linux is like FDISK in DOS. If you're familiar with the Disk Mgmt tool in Windows, it has one GUI for both but partitioning a disk and formatting a partition are still separate steps there. The basic concepts are the same, and this was intentional, to support dual-booting.

    – gatkin
    Aug 1 '11 at 17:53



















11














To use an analogy, think of fdisk as setting up the fences around your garden with small fences separating the areas that you want to have for grass, fruit trees and vegetables. While it sets up these walls (partitons) for you it does not actually put anything in those spaces.



Then you use mkfs to format those areas into the ways that you are wanting, you choose your filesystem (be it grass, fruit or vegetable) and mkfs puts it all in place and makes it usable.



What you are seeing in "partition type" is a legacy identifier that tells the system what type of operating system is likely to be able to read the contents, this is mainly so that an operating system such as Windows can quickly look at the partition type and (if it is a type it does not understand) then it can quickly move to the next partition to check that for filesystems. This does not stop the operating system from going further and actually checking the filesystem itself to see if it can read it, it just gives the OS an idea what to expect.



You can still put a Windows filesystem (NTFS) in a Linux (type 83) partition as you have done but whether or not any operating system chooses to read or ignore it is up to the designers of that operating system.






share|improve this answer


























  • Does and can an operating system such as Windows only the partition type and not proceed further? If yes, does this mean that the contents would remain inaccessible until the partition type is updated?

    – Motivated
    Dec 27 '18 at 17:45



















0














sdb--fdisk--(sdb1,sdb2)--vg--lv--mkfs (partition,lvm)



sdb--fdisk--(sdb1,sdb2)--mkfs (partition,no lvm)



sdb--pvcreate--sdb1--vg--lv--mkfs (no partition,lvm)



sdb--pvcreate--sdb1--mkfs (no partition,no lvm)





share








New contributor




zhi qiang wei is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f317724%2fdifference-between-file-system-created-by-fdisk-and-file-system-created-by-mkfs%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    14














    Fdisk partitions your hard drive. It sets up partitions on the disk by creating a partition table.



    mkfs formats the partition after it has been created. It formats it based on a specific filesystem like NTFS, FAT32, Unix ext2 & ext2.



    So fdisk isn't really creating a filesystem, it's setting up the hard drive so that a filesystem can be created on it. I'm not sure I see a problem in your picture, did you not want NTFS?






    share|improve this answer


























    • So fdisk does not create the file system, right? I use fdisk to create a partition with ext4, ext2,.. types and I use mkfs.ntfs to format the disk. I wonder, which is actually the file system? ext4 or ntfs?

      – Hieu M. Nguyen
      Aug 1 '11 at 17:27








    • 3





      NTFS is the filesystem.

      – Lance Roberts
      Aug 1 '11 at 17:32






    • 1





      @Hieusun2011: if you're familiar with DOS, mkfs in Linux is like FORMAT in DOS, and fdisk in Linux is like FDISK in DOS. If you're familiar with the Disk Mgmt tool in Windows, it has one GUI for both but partitioning a disk and formatting a partition are still separate steps there. The basic concepts are the same, and this was intentional, to support dual-booting.

      – gatkin
      Aug 1 '11 at 17:53
















    14














    Fdisk partitions your hard drive. It sets up partitions on the disk by creating a partition table.



    mkfs formats the partition after it has been created. It formats it based on a specific filesystem like NTFS, FAT32, Unix ext2 & ext2.



    So fdisk isn't really creating a filesystem, it's setting up the hard drive so that a filesystem can be created on it. I'm not sure I see a problem in your picture, did you not want NTFS?






    share|improve this answer


























    • So fdisk does not create the file system, right? I use fdisk to create a partition with ext4, ext2,.. types and I use mkfs.ntfs to format the disk. I wonder, which is actually the file system? ext4 or ntfs?

      – Hieu M. Nguyen
      Aug 1 '11 at 17:27








    • 3





      NTFS is the filesystem.

      – Lance Roberts
      Aug 1 '11 at 17:32






    • 1





      @Hieusun2011: if you're familiar with DOS, mkfs in Linux is like FORMAT in DOS, and fdisk in Linux is like FDISK in DOS. If you're familiar with the Disk Mgmt tool in Windows, it has one GUI for both but partitioning a disk and formatting a partition are still separate steps there. The basic concepts are the same, and this was intentional, to support dual-booting.

      – gatkin
      Aug 1 '11 at 17:53














    14












    14








    14







    Fdisk partitions your hard drive. It sets up partitions on the disk by creating a partition table.



    mkfs formats the partition after it has been created. It formats it based on a specific filesystem like NTFS, FAT32, Unix ext2 & ext2.



    So fdisk isn't really creating a filesystem, it's setting up the hard drive so that a filesystem can be created on it. I'm not sure I see a problem in your picture, did you not want NTFS?






    share|improve this answer















    Fdisk partitions your hard drive. It sets up partitions on the disk by creating a partition table.



    mkfs formats the partition after it has been created. It formats it based on a specific filesystem like NTFS, FAT32, Unix ext2 & ext2.



    So fdisk isn't really creating a filesystem, it's setting up the hard drive so that a filesystem can be created on it. I'm not sure I see a problem in your picture, did you not want NTFS?







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Aug 1 '11 at 17:34









    Mike Insch

    2,263118




    2,263118










    answered Aug 1 '11 at 17:04









    Lance RobertsLance Roberts

    6,98684175




    6,98684175













    • So fdisk does not create the file system, right? I use fdisk to create a partition with ext4, ext2,.. types and I use mkfs.ntfs to format the disk. I wonder, which is actually the file system? ext4 or ntfs?

      – Hieu M. Nguyen
      Aug 1 '11 at 17:27








    • 3





      NTFS is the filesystem.

      – Lance Roberts
      Aug 1 '11 at 17:32






    • 1





      @Hieusun2011: if you're familiar with DOS, mkfs in Linux is like FORMAT in DOS, and fdisk in Linux is like FDISK in DOS. If you're familiar with the Disk Mgmt tool in Windows, it has one GUI for both but partitioning a disk and formatting a partition are still separate steps there. The basic concepts are the same, and this was intentional, to support dual-booting.

      – gatkin
      Aug 1 '11 at 17:53



















    • So fdisk does not create the file system, right? I use fdisk to create a partition with ext4, ext2,.. types and I use mkfs.ntfs to format the disk. I wonder, which is actually the file system? ext4 or ntfs?

      – Hieu M. Nguyen
      Aug 1 '11 at 17:27








    • 3





      NTFS is the filesystem.

      – Lance Roberts
      Aug 1 '11 at 17:32






    • 1





      @Hieusun2011: if you're familiar with DOS, mkfs in Linux is like FORMAT in DOS, and fdisk in Linux is like FDISK in DOS. If you're familiar with the Disk Mgmt tool in Windows, it has one GUI for both but partitioning a disk and formatting a partition are still separate steps there. The basic concepts are the same, and this was intentional, to support dual-booting.

      – gatkin
      Aug 1 '11 at 17:53

















    So fdisk does not create the file system, right? I use fdisk to create a partition with ext4, ext2,.. types and I use mkfs.ntfs to format the disk. I wonder, which is actually the file system? ext4 or ntfs?

    – Hieu M. Nguyen
    Aug 1 '11 at 17:27







    So fdisk does not create the file system, right? I use fdisk to create a partition with ext4, ext2,.. types and I use mkfs.ntfs to format the disk. I wonder, which is actually the file system? ext4 or ntfs?

    – Hieu M. Nguyen
    Aug 1 '11 at 17:27






    3




    3





    NTFS is the filesystem.

    – Lance Roberts
    Aug 1 '11 at 17:32





    NTFS is the filesystem.

    – Lance Roberts
    Aug 1 '11 at 17:32




    1




    1





    @Hieusun2011: if you're familiar with DOS, mkfs in Linux is like FORMAT in DOS, and fdisk in Linux is like FDISK in DOS. If you're familiar with the Disk Mgmt tool in Windows, it has one GUI for both but partitioning a disk and formatting a partition are still separate steps there. The basic concepts are the same, and this was intentional, to support dual-booting.

    – gatkin
    Aug 1 '11 at 17:53





    @Hieusun2011: if you're familiar with DOS, mkfs in Linux is like FORMAT in DOS, and fdisk in Linux is like FDISK in DOS. If you're familiar with the Disk Mgmt tool in Windows, it has one GUI for both but partitioning a disk and formatting a partition are still separate steps there. The basic concepts are the same, and this was intentional, to support dual-booting.

    – gatkin
    Aug 1 '11 at 17:53













    11














    To use an analogy, think of fdisk as setting up the fences around your garden with small fences separating the areas that you want to have for grass, fruit trees and vegetables. While it sets up these walls (partitons) for you it does not actually put anything in those spaces.



    Then you use mkfs to format those areas into the ways that you are wanting, you choose your filesystem (be it grass, fruit or vegetable) and mkfs puts it all in place and makes it usable.



    What you are seeing in "partition type" is a legacy identifier that tells the system what type of operating system is likely to be able to read the contents, this is mainly so that an operating system such as Windows can quickly look at the partition type and (if it is a type it does not understand) then it can quickly move to the next partition to check that for filesystems. This does not stop the operating system from going further and actually checking the filesystem itself to see if it can read it, it just gives the OS an idea what to expect.



    You can still put a Windows filesystem (NTFS) in a Linux (type 83) partition as you have done but whether or not any operating system chooses to read or ignore it is up to the designers of that operating system.






    share|improve this answer


























    • Does and can an operating system such as Windows only the partition type and not proceed further? If yes, does this mean that the contents would remain inaccessible until the partition type is updated?

      – Motivated
      Dec 27 '18 at 17:45
















    11














    To use an analogy, think of fdisk as setting up the fences around your garden with small fences separating the areas that you want to have for grass, fruit trees and vegetables. While it sets up these walls (partitons) for you it does not actually put anything in those spaces.



    Then you use mkfs to format those areas into the ways that you are wanting, you choose your filesystem (be it grass, fruit or vegetable) and mkfs puts it all in place and makes it usable.



    What you are seeing in "partition type" is a legacy identifier that tells the system what type of operating system is likely to be able to read the contents, this is mainly so that an operating system such as Windows can quickly look at the partition type and (if it is a type it does not understand) then it can quickly move to the next partition to check that for filesystems. This does not stop the operating system from going further and actually checking the filesystem itself to see if it can read it, it just gives the OS an idea what to expect.



    You can still put a Windows filesystem (NTFS) in a Linux (type 83) partition as you have done but whether or not any operating system chooses to read or ignore it is up to the designers of that operating system.






    share|improve this answer


























    • Does and can an operating system such as Windows only the partition type and not proceed further? If yes, does this mean that the contents would remain inaccessible until the partition type is updated?

      – Motivated
      Dec 27 '18 at 17:45














    11












    11








    11







    To use an analogy, think of fdisk as setting up the fences around your garden with small fences separating the areas that you want to have for grass, fruit trees and vegetables. While it sets up these walls (partitons) for you it does not actually put anything in those spaces.



    Then you use mkfs to format those areas into the ways that you are wanting, you choose your filesystem (be it grass, fruit or vegetable) and mkfs puts it all in place and makes it usable.



    What you are seeing in "partition type" is a legacy identifier that tells the system what type of operating system is likely to be able to read the contents, this is mainly so that an operating system such as Windows can quickly look at the partition type and (if it is a type it does not understand) then it can quickly move to the next partition to check that for filesystems. This does not stop the operating system from going further and actually checking the filesystem itself to see if it can read it, it just gives the OS an idea what to expect.



    You can still put a Windows filesystem (NTFS) in a Linux (type 83) partition as you have done but whether or not any operating system chooses to read or ignore it is up to the designers of that operating system.






    share|improve this answer















    To use an analogy, think of fdisk as setting up the fences around your garden with small fences separating the areas that you want to have for grass, fruit trees and vegetables. While it sets up these walls (partitons) for you it does not actually put anything in those spaces.



    Then you use mkfs to format those areas into the ways that you are wanting, you choose your filesystem (be it grass, fruit or vegetable) and mkfs puts it all in place and makes it usable.



    What you are seeing in "partition type" is a legacy identifier that tells the system what type of operating system is likely to be able to read the contents, this is mainly so that an operating system such as Windows can quickly look at the partition type and (if it is a type it does not understand) then it can quickly move to the next partition to check that for filesystems. This does not stop the operating system from going further and actually checking the filesystem itself to see if it can read it, it just gives the OS an idea what to expect.



    You can still put a Windows filesystem (NTFS) in a Linux (type 83) partition as you have done but whether or not any operating system chooses to read or ignore it is up to the designers of that operating system.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Aug 1 '11 at 17:41

























    answered Aug 1 '11 at 17:26









    MokubaiMokubai

    58.1k16139157




    58.1k16139157













    • Does and can an operating system such as Windows only the partition type and not proceed further? If yes, does this mean that the contents would remain inaccessible until the partition type is updated?

      – Motivated
      Dec 27 '18 at 17:45



















    • Does and can an operating system such as Windows only the partition type and not proceed further? If yes, does this mean that the contents would remain inaccessible until the partition type is updated?

      – Motivated
      Dec 27 '18 at 17:45

















    Does and can an operating system such as Windows only the partition type and not proceed further? If yes, does this mean that the contents would remain inaccessible until the partition type is updated?

    – Motivated
    Dec 27 '18 at 17:45





    Does and can an operating system such as Windows only the partition type and not proceed further? If yes, does this mean that the contents would remain inaccessible until the partition type is updated?

    – Motivated
    Dec 27 '18 at 17:45











    0














    sdb--fdisk--(sdb1,sdb2)--vg--lv--mkfs (partition,lvm)



    sdb--fdisk--(sdb1,sdb2)--mkfs (partition,no lvm)



    sdb--pvcreate--sdb1--vg--lv--mkfs (no partition,lvm)



    sdb--pvcreate--sdb1--mkfs (no partition,no lvm)





    share








    New contributor




    zhi qiang wei is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.

























      0














      sdb--fdisk--(sdb1,sdb2)--vg--lv--mkfs (partition,lvm)



      sdb--fdisk--(sdb1,sdb2)--mkfs (partition,no lvm)



      sdb--pvcreate--sdb1--vg--lv--mkfs (no partition,lvm)



      sdb--pvcreate--sdb1--mkfs (no partition,no lvm)





      share








      New contributor




      zhi qiang wei is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.























        0












        0








        0







        sdb--fdisk--(sdb1,sdb2)--vg--lv--mkfs (partition,lvm)



        sdb--fdisk--(sdb1,sdb2)--mkfs (partition,no lvm)



        sdb--pvcreate--sdb1--vg--lv--mkfs (no partition,lvm)



        sdb--pvcreate--sdb1--mkfs (no partition,no lvm)





        share








        New contributor




        zhi qiang wei is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.










        sdb--fdisk--(sdb1,sdb2)--vg--lv--mkfs (partition,lvm)



        sdb--fdisk--(sdb1,sdb2)--mkfs (partition,no lvm)



        sdb--pvcreate--sdb1--vg--lv--mkfs (no partition,lvm)



        sdb--pvcreate--sdb1--mkfs (no partition,no lvm)






        share








        New contributor




        zhi qiang wei is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.








        share


        share






        New contributor




        zhi qiang wei is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 4 mins ago









        zhi qiang weizhi qiang wei

        1




        1




        New contributor




        zhi qiang wei is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        zhi qiang wei is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        zhi qiang wei is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f317724%2fdifference-between-file-system-created-by-fdisk-and-file-system-created-by-mkfs%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Couldn't open a raw socket. Error: Permission denied (13) (nmap)Is it possible to run networking commands...

            VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

            Why not use the yoke to control yaw, as well as pitch and roll? Announcing the arrival of...