LVM 가이드 · 3 min read · Oct 08, 2025

LVM 초보자 가이드 - 3페이지

지금까지 우리는 세 개의 논리 볼륨을 만들었지만, 그 안에 파일 시스템이 없기 때문에 아무것도 저장할 수 없습니다. 따라서 share에 ext3 파일 시스템을, backup에 xfs 파일 시스템을, media에 reiserfs 파일 시스템을 생성합니다:

mkfs.ext3 /dev/fileserver/share
server1:~# mkfs.ext3 /dev/fileserver/share  
 mke2fs 1.40-WIP (14-Nov-2006)  
 Filesystem label=  
 OS type: Linux  
 Block size=4096 (log=2)  
 Fragment size=4096 (log=2)  
 5242880 inodes, 10485760 blocks  
 524288 blocks (5.00%) reserved for the super user  
 First data block=0  
 Maximum filesystem blocks=0  
 320 block groups  
 32768 blocks per group, 32768 fragments per group  
 16384 inodes per group  
 Superblock backups stored on blocks:  
         32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,  
         4096000, 7962624  
 
 Writing inode tables: done  
 Creating journal (32768 blocks): done  
 Writing superblocks and filesystem accounting information: done  
 
 This filesystem will be automatically checked every 23 mounts or  
 180 days, whichever comes first.  Use tune2fs -c or -i to override.
mkfs.xfs /dev/fileserver/backup
server1:~# mkfs.xfs /dev/fileserver/backup  
 meta-data=/dev/fileserver/backup isize=256    agcount=8, agsize=163840 blks  
         =                       sectsz=512   attr=0  
 data     =                       bsize=4096   blocks=1310720, imaxpct=25  
         =                       sunit=0      swidth=0 blks, unwritten=1  
 naming   =version 2              bsize=4096  
 log      =internal log           bsize=4096   blocks=2560, version=1  
         =                       sectsz=512   sunit=0 blks  
 realtime =none                   extsz=65536  blocks=0, rtextents=0
mkfs.reiserfs /dev/fileserver/media
server1:~# mkfs.reiserfs /dev/fileserver/media  
 mkfs.reiserfs 3.6.19 (2003 www.namesys.com)  
 
 A pair of credits:  
 Alexander Lyamin keeps our hardware running, and was very generous to our  
 project in many little ways.  
 
 Chris Mason wrote the journaling code for V3, which was enormously more useful  
 to users than just waiting until we could create a wandering log filesystem as  
 Hans would have unwisely done without him.  
 Jeff Mahoney optimized the bitmap scanning code for V3, and performed the big  
 endian cleanups.  
 
 
 Guessing about desired format.. Kernel 2.6.17-2-486 is running.  
 Format 3.6 with standard journal  
 Count of blocks on the device: 262144  
 Number of blocks consumed by mkreiserfs formatting process: 8219  
 Blocksize: 4096  
 Hash function used to sort names: "r5"  
 Journal Size 8193 blocks (first block 18)  
 Journal Max transaction length 1024  
 inode generation number: 0  
 UUID: 2bebf750-6e05-47b2-99b6-916fa7ea5398  
 ATTENTION: YOU SHOULD REBOOT AFTER FDISK!  
         ALL DATA WILL BE LOST ON '/dev/fileserver/media'!  
 Continue (y/n):y  
 Initializing journal - 0%....20%....40%....60%....80%....100%  
 Syncing..ok  
 
 Tell your friends to use a kernel based on 2.4.18 or later, and especially not a  
 kernel based on 2.4.9, when you use reiserFS. Have fun.  
 
 ReiserFS is successfully created on /dev/fileserver/media.

이제 우리는 논리 볼륨을 마운트할 준비가 되었습니다. share를 /var/share에, backup을 /var/backup에, media를 /var/media에 마운트하고 싶으므로 먼저 이러한 디렉토리를 생성해야 합니다:

mkdir /var/media /var/backup /var/share

이제 논리 볼륨을 마운트할 수 있습니다:

mount /dev/fileserver/share /var/share  
 mount /dev/fileserver/backup /var/backup  
 mount /dev/fileserver/media /var/media

이제 실행하세요

df -h

출력에서 논리 볼륨을 확인할 수 있어야 합니다:

server1:~# df -h  
 Filesystem            Size  Used Avail Use% Mounted on  
 /dev/sda2              19G  665M   17G   4% /  
 tmpfs                  78M     0   78M   0% /lib/init/rw  
 udev                   10M   88K   10M   1% /dev  
 tmpfs                  78M     0   78M   0% /dev/shm  
 /dev/sda1             137M   17M  114M  13% /boot  
 /dev/mapper/fileserver-share  
                       40G  177M   38G   1% /var/share  
 /dev/mapper/fileserver-backup  
                       5.0G  144K  5.0G   1% /var/backup  
 /dev/mapper/fileserver-media  
                       1.0G   33M  992M   4% /var/media

축하합니다. 당신은 첫 번째 LVM 시스템을 설정했습니다! 이제 /var/share, /var/backup 및 /var/media에 일반적으로 읽고 쓸 수 있습니다.

우리는 논리 볼륨을 수동으로 마운트했지만, 물론 시스템 부팅 시 자동으로 마운트되기를 원합니다. 따라서 /etc/fstab을 수정합니다:

mv /etc/fstab /etc/fstab_orig  
 cat /dev/null > /etc/fstab
vi /etc/fstab

다음 내용을 입력합니다:

| # /etc/fstab: static file system information. # # proc /proc proc defaults 0 0 /dev/sda2 / ext3 defaults,errors=remount-ro 0 1 /dev/sda1 /boot ext3 defaults 0 2 /dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0 /dev/fileserver/share /var/share ext3 rw,noatime 0 0 /dev/fileserver/backup /var/backup xfs rw,noatime 0 0 /dev/fileserver/media /var/media reiserfs rw,noatime 0 0 |

원본 파일의 백업인 /etc/fstab_orig와 비교하면 다음 줄을 추가했음을 알 수 있습니다:

/dev/fileserver/share   /var/share     ext3       rw,noatime    0 0  
 /dev/fileserver/backup    /var/backup      xfs        rw,noatime    0 0  
 /dev/fileserver/media    /var/media      reiserfs   rw,noatime    0 0

이제 시스템을 재부팅합니다:

shutdown -r now

시스템이 다시 시작된 후, 다시 실행하세요

df -h

여전히 출력에서 논리 볼륨이 표시되어야 합니다:

server1:~# df -h  
 Filesystem            Size  Used Avail Use% Mounted on  
 /dev/sda2              19G  665M   17G   4% /  
 tmpfs                  78M     0   78M   0% /lib/init/rw  
 udev                   10M   88K   10M   1% /dev  
 tmpfs                  78M     0   78M   0% /dev/shm  
 /dev/sda1             137M   17M  114M  13% /boot  
 /dev/mapper/fileserver-share  
                       40G  177M   38G   1% /var/share  
 /dev/mapper/fileserver-backup  
                       5.0G  144K  5.0G   1% /var/backup  
 /dev/mapper/fileserver-media  
                       1.0G   33M  992M   4% /var/media
Share: X/Twitter LinkedIn
#LVM 가이드

새 게시물을 받은 편지함에서 받기

스팸은 없습니다. 언제든지 구독 해지 가능합니다.