LVM · 3 min read · Oct 08, 2025
Um Guia para Iniciantes sobre LVM - Página 3
Até agora, temos três volumes lógicos, mas não temos nenhum sistema de arquivos neles, e sem um sistema de arquivos não podemos salvar nada neles. Portanto, criamos um sistema de arquivos ext3 em share, um sistema de arquivos xfs em backup e um sistema de arquivos reiserfs em media:
mkfs.ext3 /dev/fileserver/shareserver1:~# 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/backupserver1:~# 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=0mkfs.reiserfs /dev/fileserver/mediaserver1:~# 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
ATENÇÃO: VOCÊ DEVE REINICIAR APÓS FDISK!
TODOS OS DADOS SERÃO PERDIDOS EM '/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.Agora estamos prontos para montar nossos volumes lógicos. Quero montar share em /var/share, backup em /var/backup e media em /var/media, portanto, devemos criar esses diretórios primeiro:
mkdir /var/media /var/backup /var/shareAgora podemos montar nossos volumes lógicos:
mount /dev/fileserver/share /var/share
mount /dev/fileserver/backup /var/backup
mount /dev/fileserver/media /var/mediaAgora execute
df -hVocê deve ver seus volumes lógicos na saída:
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/mediaParabéns, você acabou de configurar seu primeiro sistema LVM! Agora você pode gravar e ler de /var/share, /var/backup e /var/media como de costume.
Montamos nossos volumes lógicos manualmente, mas, claro, gostaríamos que eles fossem montados automaticamente quando o sistema inicializa. Portanto, modificamos /etc/fstab:
mv /etc/fstab /etc/fstab_orig
cat /dev/null > /etc/fstabvi /etc/fstabColoque o seguinte nele:
| # /etc/fstab: informações do sistema de arquivos estático. # # |
Se você comparar com nosso backup do arquivo original, /etc/fstab_orig, você notará que adicionamos as linhas:
/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 0Agora reiniciamos o sistema:
shutdown -r nowApós o sistema ter reiniciado, execute
df -hnovamente. Ele ainda deve mostrar nossos volumes lógicos na saída:
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/mediaReceba novas postagens na sua caixa de entrada
Sem spam. Cancele a assinatura a qualquer momento.