GlusterFS Setup · 3 min read · Feb 04, 2026
Striping Across Four Storage Nodes With GlusterFS On Debian Lenny - Page 2
3 Configurazione del Client GlusterFS
client1.example.com:
Sul client, dobbiamo installare fuse e GlusterFS. Invece di installare il pacchetto libfuse2 dal repository Debian, installiamo una versione patchata con un supporto migliore per GlusterFS.
Prima installiamo di nuovo i prerequisiti:
aptitude install sshfs build-essential flex bison byacc libdb4.6 libdb4.6-devPoi costruiamo fuse come segue (puoi trovare l’ultima versione patchata di fuse su ftp://ftp.zresearch.com/pub/gluster/glusterfs/fuse/):
cd /tmp
wget ftp://ftp.zresearch.com/pub/gluster/glusterfs/fuse/fuse-2.7.4glfs11.tar.gz
tar -zxvf fuse-2.7.4glfs11.tar.gz
cd fuse-2.7.4glfs11
./configure
make && make installDopo costruiamo GlusterFS (proprio come sul server)…
cd /tmp
wget http://ftp.gluster.com/pub/gluster/glusterfs/2.0/LATEST/glusterfs-2.0.1.tar.gz
tar xvfz glusterfs-2.0.1.tar.gz
cd glusterfs-2.0.1
./configure --prefix=/usr > /dev/nullmake && make install
ldconfig
glusterfs --version… e creiamo le seguenti due directory:
mkdir /mnt/glusterfs
mkdir /etc/glusterfsSuccessivamente creiamo il file /etc/glusterfs/glusterfs.vol:
vi /etc/glusterfs/glusterfs.vol| volume remote1 type protocol/client option transport-type tcp/client option remote-host server1.example.com option remote-subvolume brick end-volume volume remote2 type protocol/client option transport-type tcp/client option remote-host server2.example.com option remote-subvolume brick end-volume volume remote3 type protocol/client option transport-type tcp/client option remote-host server3.example.com option remote-subvolume brick end-volume volume remote4 type protocol/client option transport-type tcp/client option remote-host server4.example.com option remote-subvolume brick end-volume volume stripe type cluster/stripe option block-size 1MB subvolumes remote1 remote2 remote3 remote4 end-volume volume writebehind type performance/write-behind option window-size 1MB subvolumes stripe end-volume volume cache type performance/io-cache option cache-size 512MB subvolumes writebehind end-volume |
Assicurati di utilizzare i nomi host o gli indirizzi IP corretti nei parametri remote-host!
Ecco fatto! Ora possiamo montare il filesystem GlusterFS su /mnt/glusterfs con uno dei seguenti due comandi:
glusterfs -f /etc/glusterfs/glusterfs.vol /mnt/glusterfsoppure
mount -t glusterfs /etc/glusterfs/glusterfs.vol /mnt/glusterfsOra dovresti vedere la nuova condivisione negli output di…
mountclient1:~# mount
/dev/sda1 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
odev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
/etc/glusterfs/glusterfs.vol on /mnt/glusterfs type fuse.glusterfs (rw,max_read=131072,allow_other,default_permissions)
client1:~#… e…
df -hclient1:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 29G 896M 27G 4% /
tmpfs 126M 0 126M 0% /lib/init/rw
udev 10M 80K 10M 1% /dev
tmpfs 126M 0 126M 0% /dev/shm
/etc/glusterfs/glusterfs.vol
105G 3.4G 96G 4% /mnt/glusterfs
client1:~#( server1.example.com, server2.example.com, server3.example.com e server4.example.com hanno ciascuno circa 26GB di spazio per il filesystem GlusterFS, in modo che la condivisione risultante abbia una dimensione di circa 4 x 26GB (105GB).)
Invece di montare manualmente la condivisione GlusterFS sul client, potresti modificare /etc/fstab in modo che la condivisione venga montata automaticamente all’avvio del client.
Apri /etc/fstab e aggiungi la seguente riga:
vi /etc/fstab| [...] /etc/glusterfs/glusterfs.vol /mnt/glusterfs glusterfs defaults 0 0 |
Per testare se la tua modifica a /etc/fstab funziona, riavvia il client:
rebootDopo il riavvio, dovresti trovare la condivisione negli output di…
df -h… e…
mount4 Test
Ora creiamo un grande file di test sulla condivisione GlusterFS:
client1.example.com:
dd if=/dev/zero of=/mnt/glusterfs/test.img bs=1024k count=1000ls -l /mnt/glusterfsclient1:~# ls -l /mnt/glusterfs
total 1028032
-rw-r--r-- 1 root root 1048576000 2009-06-03 20:51 test.img
client1:~#Ora controlliamo la directory /data/export su server1.example.com, server2.example.com, server3.example.com e server4.example.com. Dovresti vedere il file test.img su ciascun nodo, ma con dimensioni diverse (a causa dello striping dei dati):
server1.example.com:
ls -l /data/exportserver1:~# ls -l /data/export
total 257008
-rw-r--r-- 1 root root 1045430272 2009-06-03 20:51 test.img
server1:~#server2.example.com:
ls -l /data/exportserver2:~# ls -l /data/export
total 257008
-rw-r--r-- 1 root root 1046478848 2009-06-03 20:55 test.img
server2:~#server3.example.com:
ls -l /data/exportserver3:~# ls -l /data/export
total 257008
-rw-r--r-- 1 root root 1047527424 2009-06-03 20:54 test.img
server3:~#server4.example.com:
ls -l /data/exportserver4:~# ls -l /data/export
total 257008
-rw-r--r-- 1 root root 1048576000 2009-06-03 20:02 test.img
server4:~#5 Link
- GlusterFS: http://www.gluster.org/
- Debian: http://www.debian.org/
Ricevi i nuovi post nella tua casella di posta.
Nessuno spam. Disiscriviti in qualsiasi momento.