LVM Guide · 3 min read · Oct 08, 2025
Guida per principianti a LVM - Pagina 3
Fino ad ora abbiamo tre volumi logici, ma non abbiamo alcun filesystem in essi, e senza un filesystem non possiamo salvare nulla in essi. Pertanto, creiamo un filesystem ext3 in share, un filesystem xfs in backup e un filesystem reiserfs in 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
ATTENZIONE: DOVRESTE RIAVVIARE DOPO FDISK!
TUTTI I DATI SARANNO PERDUTI SU '/dev/fileserver/media'!
Continuare (y/n):y
Initializing journal - 0%....20%....40%....60%....80%....100%
Syncing..ok
Dite ai vostri amici di usare un kernel basato su 2.4.18 o successivo, e
specialmente non un kernel basato su 2.4.9, quando usate reiserFS. Divertitevi.
ReiserFS è stato creato con successo su /dev/fileserver/media.Ora siamo pronti per montare i nostri volumi logici. Voglio montare share in /var/share, backup in /var/backup e media in /var/media, quindi dobbiamo prima creare queste directory:
mkdir /var/media /var/backup /var/shareOra possiamo montare i nostri volumi logici:
mount /dev/fileserver/share /var/share
mount /dev/fileserver/backup /var/backup
mount /dev/fileserver/media /var/mediaOra esegui
df -hDovresti vedere i tuoi volumi logici nell’output:
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/mediaCongratulazioni, hai appena configurato il tuo primo sistema LVM! Ora puoi scrivere e leggere da /var/share, /var/backup e /var/media come al solito.
Abbiamo montato i nostri volumi logici manualmente, ma ovviamente ci piacerebbe che fossero montati automaticamente all’avvio del sistema. Pertanto, modifichiamo /etc/fstab:
mv /etc/fstab /etc/fstab_orig
cat /dev/null > /etc/fstabvi /etc/fstabMetti il seguente contenuto:
| # /etc/fstab: informazioni statiche sul filesystem. # # |
Se lo confronti con il nostro backup del file originale, /etc/fstab_orig, noterai che abbiamo aggiunto le righe:
/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 0Ora riavviamo il sistema:
shutdown -r nowDopo che il sistema è ripartito, esegui di nuovo
df -hdovrebbe ancora mostrare i nostri volumi logici nell’output:
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/mediaRicevi i nuovi post nella tua casella di posta.
Nessuno spam. Disiscriviti in qualsiasi momento.