
SB multihost format = 1401
Block size = 4096
Journals = 8
Resource Groups = 76
Mounted lock proto = "lock_dlm"
Mounted lock table = "tng3-cluster:mydata1"
Mounted host data = "jid=0:id=196609:first=1"
Journal number = 0
Lock module flags = 0
Local flocks = FALSE
Local caching = FALSE
Oopses OK = FALSE
Type Total Used Free use%
------------------------------------------------------------------------
inodes 33 33 0 100%
metadata 38 2 36 5%
data 4980077 178 4979899 0%
After running the gfs_jadd command, you can run the gfs_tool df MountPoint command
again to check that the new journals have been added to the file system.
Examples
In this example, one journal is added to the file system that is mounted at the /mnt/gfs
directory. The underlying logical volume for this filesystem is extended before the journal can be
added.
[root@tng3-1 ~]# lvextend -L35G /dev/gfsvg/gfslv
Extending logical volume gfslv to 35.00 GB
Logical volume gfslv successfully resized
[root@tng3-1 ~]# gfs_jadd -j1 /mnt/gfs
FS: Mount Point: /mnt/gfs
FS: Device: /dev/mapper/gfsvg-gfslv
FS: Options: rw,hostdata=jid=0:id=196609:first=1
FS: Size: 5242877
DEV: Size: 9175040
Preparing to write new FS information...
Done.
In this example, two journals are added to the file system on the /mnt/gfs directory.
[root@tng3-1 ~]# fs_jadd -j2 /mnt/gfs
FS: Mount Point: /mnt/gfs
FS: Device: /dev/mapper/gfsvg-gfslv
FS: Options: rw,hostdata=jid=0:id=196609:first=1
FS: Size: 5275632
DEV: Size: 9175040
Preparing to write new FS information...
Done.
Chapter 3. Managing GFS
28
Kommentare zu diesen Handbüchern