ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    How to Install Fedora 25 Minimal

    IT Discussion
    fedora 25 installation guide how to real instructions fedora
    9
    41
    11.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • FATeknollogeeF
      FATeknollogee @JaredBusch
      last edited by

      @JaredBusch Networking tab. In that case, let me go ahead & install the daemons

      1 Reply Last reply Reply Quote 0
      • stacksofplatesS
        stacksofplates @travisdh1
        last edited by stacksofplates

        @travisdh1 said in How to Install Fedora 25 Minimal:

        @FATeknollogee said in How to Install Fedora 25 Minimal:

        @JaredBusch said in How to Install Fedora 25 Minimal:

        @FATeknollogee said in How to Install Fedora 25 Minimal:

        @JaredBusch Let's say you want to use this VM as a file server.
        Is it better to create 2 disks (1 for o/s + 1 for storage) or just one big ass disk?

        As this example showed, I had a 127GB disk because I let Hyper-V Server 2016 use its default.

        Fedora only took 17GB of it. 2GB for swap and 15GB for root.

        The rest is sitting there waiting to be used however you want.

        So all you have to do is make the space usable.

        #create a logical volume named data
lvcreate -l 100%FREE -n data fedora

#format it to ext4
mkfs.ext4 /dev/fedora/data

#make a directory to mount it
mkdir /data

#mount it
mount /dev/fedora/data /data

        Obviously you will want to have this mounted on reboot, so add it to /etc/fstab

        nano /etc/fstab

#add this
/dev/fedora/data /data                    ext4    defaults        1 2

        Anyone have a simple "how to do this" guide on /dev/xvdb or /dev/sdb ? (I read some guides on the 'net, thy all seem long & winded)

        Off the top of my head even, let's go!

        pvcreate /dev/xvdb
vgcreate vgname /dev/xvdb
lvcreate -n 'lvname' vgname -l 100%FREE
mkfs.xfs /dev/vgname/lvname
mount /dev/vgname/lvname /mountpoint

        If you add an xfs volume to fstab, it's recommended to make the last two options (dump and fsck) zero. Yeah, xfs can really speed up boot times if you're switching from another file system that needs to run an fsck at boot.

        https://mangolassi.it/topic/11302/travis-hershberger-linux-lvm-storage

        If you're doing -l 100%FREE it doesn't necessarily matter. But if you are ever going to have more than one volume, I'd do vgcreate -s 1G (or more depending on volume size). 4M chunks become annoying to manage, especially when you can do vgcreate -l 1 vs vgcreate -l $((1024000 / 4096)).

        travisdh1T 1 Reply Last reply Reply Quote 0
        • travisdh1T
          travisdh1 @stacksofplates
          last edited by travisdh1

          @stacksofplates said in How to Install Fedora 25 Minimal:

          @travisdh1 said in How to Install Fedora 25 Minimal:

          @FATeknollogee said in How to Install Fedora 25 Minimal:

          @JaredBusch said in How to Install Fedora 25 Minimal:

          @FATeknollogee said in How to Install Fedora 25 Minimal:

          @JaredBusch Let's say you want to use this VM as a file server.
          Is it better to create 2 disks (1 for o/s + 1 for storage) or just one big ass disk?

          As this example showed, I had a 127GB disk because I let Hyper-V Server 2016 use its default.

          Fedora only took 17GB of it. 2GB for swap and 15GB for root.

          The rest is sitting there waiting to be used however you want.

          So all you have to do is make the space usable.

          #create a logical volume named data
lvcreate -l 100%FREE -n data fedora

#format it to ext4
mkfs.ext4 /dev/fedora/data

#make a directory to mount it
mkdir /data

#mount it
mount /dev/fedora/data /data

          Obviously you will want to have this mounted on reboot, so add it to /etc/fstab

          nano /etc/fstab

#add this
/dev/fedora/data /data                    ext4    defaults        1 2

          Anyone have a simple "how to do this" guide on /dev/xvdb or /dev/sdb ? (I read some guides on the 'net, thy all seem long & winded)

          Off the top of my head even, let's go!

          pvcreate /dev/xvdb
vgcreate vgname /dev/xvdb
lvcreate -n 'lvname' vgname -l 100%FREE
mkfs.xfs /dev/vgname/lvname
mount /dev/vgname/lvname /mountpoint

          If you add an xfs volume to fstab, it's recommended to make the last two options (dump and fsck) zero. Yeah, xfs can really speed up boot times if you're switching from another file system that needs to run an fsck at boot.

          https://mangolassi.it/topic/11302/travis-hershberger-linux-lvm-storage

          If you're doing -l 100%FREE it doesn't necessarily matter. But if you are ever going to have more than one volume, I'd do vgcreate -s 1G (or more depending on volume size). 4M chunks become annoying to manage, especially when you can do vgcreate -l 1 vs vgcreate -l $((1024000 / 4096)).

          I have to ask, how do the 4M chunks become annoying to manage?

          The -l 100%FREE should really be a lower percentage anyway, so you can take a snapshot on the volume when you want to run a backup.

          stacksofplatesS 1 Reply Last reply Reply Quote 0
          • stacksofplatesS
            stacksofplates @travisdh1
            last edited by

            @travisdh1 said in How to Install Fedora 25 Minimal:

            @stacksofplates said in How to Install Fedora 25 Minimal:

            @travisdh1 said in How to Install Fedora 25 Minimal:

            @FATeknollogee said in How to Install Fedora 25 Minimal:

            @JaredBusch said in How to Install Fedora 25 Minimal:

            @FATeknollogee said in How to Install Fedora 25 Minimal:

            @JaredBusch Let's say you want to use this VM as a file server.
            Is it better to create 2 disks (1 for o/s + 1 for storage) or just one big ass disk?

            As this example showed, I had a 127GB disk because I let Hyper-V Server 2016 use its default.

            Fedora only took 17GB of it. 2GB for swap and 15GB for root.

            The rest is sitting there waiting to be used however you want.

            So all you have to do is make the space usable.

            #create a logical volume named data
lvcreate -l 100%FREE -n data fedora

#format it to ext4
mkfs.ext4 /dev/fedora/data

#make a directory to mount it
mkdir /data

#mount it
mount /dev/fedora/data /data

            Obviously you will want to have this mounted on reboot, so add it to /etc/fstab

            nano /etc/fstab

#add this
/dev/fedora/data /data                    ext4    defaults        1 2

            Anyone have a simple "how to do this" guide on /dev/xvdb or /dev/sdb ? (I read some guides on the 'net, thy all seem long & winded)

            Off the top of my head even, let's go!

            pvcreate /dev/xvdb
vgcreate vgname /dev/xvdb
lvcreate -n 'lvname' vgname -l 100%FREE
mkfs.xfs /dev/vgname/lvname
mount /dev/vgname/lvname /mountpoint

            If you add an xfs volume to fstab, it's recommended to make the last two options (dump and fsck) zero. Yeah, xfs can really speed up boot times if you're switching from another file system that needs to run an fsck at boot.

            https://mangolassi.it/topic/11302/travis-hershberger-linux-lvm-storage

            If you're doing -l 100%FREE it doesn't necessarily matter. But if you are ever going to have more than one volume, I'd do vgcreate -s 1G (or more depending on volume size). 4M chunks become annoying to manage, especially when you can do vgcreate -l 1 vs vgcreate -l $((1024000 / 4096)).

            I have to ask, how do the 4M chunks become annoying to manage?

            The -l 100%FREE should really be a lower percentage anyway, so you can take a snapshot on the volume when you want to run a backup.

            You get both performance gains from using larger chunks and you don't need to do math when you grow your volume. If you only grow your volume to what you need at the time, it's much easier to just type the size in GB vs the number of extents / 4M.

            travisdh1T 1 Reply Last reply Reply Quote 0
            • travisdh1T
              travisdh1 @stacksofplates
              last edited by

              @stacksofplates said in How to Install Fedora 25 Minimal:

              @travisdh1 said in How to Install Fedora 25 Minimal:

              @stacksofplates said in How to Install Fedora 25 Minimal:

              @travisdh1 said in How to Install Fedora 25 Minimal:

              @FATeknollogee said in How to Install Fedora 25 Minimal:

              @JaredBusch said in How to Install Fedora 25 Minimal:

              @FATeknollogee said in How to Install Fedora 25 Minimal:

              @JaredBusch Let's say you want to use this VM as a file server.
              Is it better to create 2 disks (1 for o/s + 1 for storage) or just one big ass disk?

              As this example showed, I had a 127GB disk because I let Hyper-V Server 2016 use its default.

              Fedora only took 17GB of it. 2GB for swap and 15GB for root.

              The rest is sitting there waiting to be used however you want.

              So all you have to do is make the space usable.

              #create a logical volume named data
lvcreate -l 100%FREE -n data fedora

#format it to ext4
mkfs.ext4 /dev/fedora/data

#make a directory to mount it
mkdir /data

#mount it
mount /dev/fedora/data /data

              Obviously you will want to have this mounted on reboot, so add it to /etc/fstab

              nano /etc/fstab

#add this
/dev/fedora/data /data                    ext4    defaults        1 2

              Anyone have a simple "how to do this" guide on /dev/xvdb or /dev/sdb ? (I read some guides on the 'net, thy all seem long & winded)

              Off the top of my head even, let's go!

              pvcreate /dev/xvdb
vgcreate vgname /dev/xvdb
lvcreate -n 'lvname' vgname -l 100%FREE
mkfs.xfs /dev/vgname/lvname
mount /dev/vgname/lvname /mountpoint

              If you add an xfs volume to fstab, it's recommended to make the last two options (dump and fsck) zero. Yeah, xfs can really speed up boot times if you're switching from another file system that needs to run an fsck at boot.

              https://mangolassi.it/topic/11302/travis-hershberger-linux-lvm-storage

              If you're doing -l 100%FREE it doesn't necessarily matter. But if you are ever going to have more than one volume, I'd do vgcreate -s 1G (or more depending on volume size). 4M chunks become annoying to manage, especially when you can do vgcreate -l 1 vs vgcreate -l $((1024000 / 4096)).

              I have to ask, how do the 4M chunks become annoying to manage?

              The -l 100%FREE should really be a lower percentage anyway, so you can take a snapshot on the volume when you want to run a backup.

              You get both performance gains from using larger chunks and you don't need to do math when you grow your volume. If you only grow your volume to what you need at the time, it's much easier to just type the size in GB vs the number of extents / 4M.

              It's LVM, so it really doesn't care if you tell it the number of extents to use or the size in GB. Two different ways of telling it the same thing. Mix and match to your hearts content.

              stacksofplatesS 1 Reply Last reply Reply Quote 0
              • stacksofplatesS
                stacksofplates @travisdh1
                last edited by

                @travisdh1 said in How to Install Fedora 25 Minimal:

                @stacksofplates said in How to Install Fedora 25 Minimal:

                @travisdh1 said in How to Install Fedora 25 Minimal:

                @stacksofplates said in How to Install Fedora 25 Minimal:

                @travisdh1 said in How to Install Fedora 25 Minimal:

                @FATeknollogee said in How to Install Fedora 25 Minimal:

                @JaredBusch said in How to Install Fedora 25 Minimal:

                @FATeknollogee said in How to Install Fedora 25 Minimal:

                @JaredBusch Let's say you want to use this VM as a file server.
                Is it better to create 2 disks (1 for o/s + 1 for storage) or just one big ass disk?

                As this example showed, I had a 127GB disk because I let Hyper-V Server 2016 use its default.

                Fedora only took 17GB of it. 2GB for swap and 15GB for root.

                The rest is sitting there waiting to be used however you want.

                So all you have to do is make the space usable.

                #create a logical volume named data
lvcreate -l 100%FREE -n data fedora

#format it to ext4
mkfs.ext4 /dev/fedora/data

#make a directory to mount it
mkdir /data

#mount it
mount /dev/fedora/data /data

                Obviously you will want to have this mounted on reboot, so add it to /etc/fstab

                nano /etc/fstab

#add this
/dev/fedora/data /data                    ext4    defaults        1 2

                Anyone have a simple "how to do this" guide on /dev/xvdb or /dev/sdb ? (I read some guides on the 'net, thy all seem long & winded)

                Off the top of my head even, let's go!

                pvcreate /dev/xvdb
vgcreate vgname /dev/xvdb
lvcreate -n 'lvname' vgname -l 100%FREE
mkfs.xfs /dev/vgname/lvname
mount /dev/vgname/lvname /mountpoint

                If you add an xfs volume to fstab, it's recommended to make the last two options (dump and fsck) zero. Yeah, xfs can really speed up boot times if you're switching from another file system that needs to run an fsck at boot.

                https://mangolassi.it/topic/11302/travis-hershberger-linux-lvm-storage

                If you're doing -l 100%FREE it doesn't necessarily matter. But if you are ever going to have more than one volume, I'd do vgcreate -s 1G (or more depending on volume size). 4M chunks become annoying to manage, especially when you can do vgcreate -l 1 vs vgcreate -l $((1024000 / 4096)).

                I have to ask, how do the 4M chunks become annoying to manage?

                The -l 100%FREE should really be a lower percentage anyway, so you can take a snapshot on the volume when you want to run a backup.

                You get both performance gains from using larger chunks and you don't need to do math when you grow your volume. If you only grow your volume to what you need at the time, it's much easier to just type the size in GB vs the number of extents / 4M.

                It's LVM, so it really doesn't care if you tell it the number of extents to use or the size in GB. Two different ways of telling it the same thing. Mix and match to your hearts content.

                You can do a -L and pass the size in GB but if you don't know exactly how many extents you have left you have to calculate that before you can pass a size. You also gain performance in using larger chunks.

                1 Reply Last reply Reply Quote 0
                • stacksofplatesS
                  stacksofplates
                  last edited by

                  For example a volume with 4041 free extents in 4MB chunks.

                  >$ sudo lvcreate -L 20G -n test rhel
Volume group "rhel" has insufficient free space (4041 extents): 5120 required.

                  So now if you can't grow your volume group, you have to calculate how much space 4041 extents is.

                  vgdisplay will show you PE size, but you still have to calculate how much free space to leave so you don't over commit.

                  1 Reply Last reply Reply Quote 0
                  • stacksofplatesS
                    stacksofplates
                    last edited by

                    So if you're working with 400M volumes, sure leave it at 4M. But anything in the normal sizes today (hundreds of GB), it saves time, mistakes, and gains performance by setting a larger chunk size.

                    1 Reply Last reply Reply Quote 0
                    • black3dynamiteB
                      black3dynamite
                      last edited by

                      Unlike installing Linux Integration Services, Hot-Add support is not enabled by default after installing hyperv-daemons.

                      Create a file /etc/udev/rules.d/100-balloon.rules. You may use any other desired name for the file.

                      Add the following content to the file: SUBSYSTEM=="memory", ACTION=="add", ATTR{state}="online"

                      Reboot the system to enable Hot-Add support.

                      See Note 8 on Supported CentOS and Red Hat Enterprise Linux virtual machines on Hyper-V

                      JaredBuschJ 1 Reply Last reply Reply Quote 0
                      • JaredBuschJ
                        JaredBusch @black3dynamite
                        last edited by

                        @black3dynamite said in How to Install Fedora 25 Minimal:

                        Unlike installing Linux Integration Services, Hot-Add support is not enabled by default after installing hyperv-daemons.

                        Create a file /etc/udev/rules.d/100-balloon.rules. You may use any other desired name for the file.

                        Add the following content to the file: SUBSYSTEM=="memory", ACTION=="add", ATTR{state}="online"

                        Reboot the system to enable Hot-Add support.

                        See Note 8 on Supported CentOS and Red Hat Enterprise Linux virtual machines on Hyper-V

                        You mean for dynamic memory to work?

                        black3dynamiteB 1 Reply Last reply Reply Quote 0
                        • black3dynamiteB
                          black3dynamite @JaredBusch
                          last edited by

                          @JaredBusch said in How to Install Fedora 25 Minimal:

                          @black3dynamite said in How to Install Fedora 25 Minimal:

                          Unlike installing Linux Integration Services, Hot-Add support is not enabled by default after installing hyperv-daemons.

                          Create a file /etc/udev/rules.d/100-balloon.rules. You may use any other desired name for the file.

                          Add the following content to the file: SUBSYSTEM=="memory", ACTION=="add", ATTR{state}="online"

                          Reboot the system to enable Hot-Add support.

                          See Note 8 on Supported CentOS and Red Hat Enterprise Linux virtual machines on Hyper-V

                          You mean for dynamic memory to work?

                          Yes, dynamic memory for ballooning and hot-add.

                          1 Reply Last reply Reply Quote 2
                          • 1
                          • 2
                          • 3
                          • 2 / 3
                          • First post
                            Last post