![]() The cookies is used to store the user consent for the cookies in the category "Necessary". This cookie is set by GDPR Cookie Consent plugin. The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly. ![]() btrfs-dir/test.img /mnt/btrfs auto loop 0 0 To permanently mount this device and have it automatically mounted at boot time, we need to modify the “fstab” file. # btrfs filesystem resize max /mnt/btrfsĬheck the available size. # losetup -c /dev/loop12Īnd resize the BTRFS file system. Now we want to expand this to 5 GB by adding 3GB to our existing image “test.img”. ![]() You can see our system created a loop device “/dev/loop12” with 1.9 GB space. # mount -o loop /btrfs-dir/test.img /mnt/btrfs/Ĭheck the size. Mount our image as a loop device on new mountpoint. Incompat features: extref, skinny-metadataĬreate a new mountpoint “/mnt/btrfs” (This is arbitrary so can be changed if desired). # mkfs.btrfs /btrfs-dir/test.img btrfs-progs v5.4.1 # truncate -s 2GB /btrfs-dir/test.imgĪnd create a BTRFS file system. ![]() # mkdir /btrfs-dirĬreate a new 2 GB image. We will further see how to expand a BTRFS loop device without losing the data already stored. In this tutorial, we will learn how to create a BTRFS loop device (virtual block device) and how to mount this device permanently so that it is available when the system reboots. ![]()
0 Comments
Leave a Reply. |