User Tools

Site Tools


This is an old revision of the document!



A document for me to recall and make notes of what I read in the manual pages and what needs testing.

Basically during the Summer of 2016 I investigated if the HPCC could afford enterprise level storage. I wanted 99.999% uptime, snapshots, high availability and other goodies such as parallel NFS. Netapp came the closest but, eh, still at $42K lots of other options show up. The story is detailed here at The Storage Problem

This page is best read from the bottom up.

cluster idea

  • Storage servers: buy 2 now 4k+4k then 3rd in July 4k?
  • move test users over on 2 nodes, test, only change is $HOME
  • Home cluster
    • cottontail (mngt+admingiu)
    • 2-3 new units storage (+snapshots/meta backup)
    • cottontail2 meta + n38-n45 meta, all mirrored


  • cottontail:/usr/local/bin/beegfs-admin-gui

Resync Data #2

If you have 2 buddymirrors and 2 storage servers each with 2 storage objects, beegfs will write to all primary storage targets even if numtargets is to 1 … it will use all storage objects so best to numtargets's value equal to the number of primary storage objects. And then of course the content flow from primary to secondary for high availability.

How does one add a server?

# define storage objects, 2 per server
[root@petaltail ~]# /opt/beegfs/sbin/beegfs-setup-storage -p /data/lv1/beegfs_storage -s 217 -i 21701 -m cottontail
[root@petaltail ~]# /opt/beegfs/sbin/beegfs-setup-storage -p /data/lv2/beegfs_storage -s 217 -i 21702 -m cottontail
[root@swallowtail data]# /opt/beegfs/sbin/beegfs-setup-storage -p /data/lv1/beegfs_storage -s 136 -i 13601 -m cottontail 
[root@swallowtail data]# /opt/beegfs/sbin/beegfs-setup-storage -p /data/lv2/beegfs_storage -s 136 -i 13602 -m cottontail

[root@cottontail2 ~]# beegfs-df
TargetID        Pool        Total         Free    %      ITotal       IFree    %
========        ====        =====         ====    =      ======       =====    =
     250         low     122.3GiB     116.6GiB  95%        7.8M        7.6M  98%

TargetID        Pool        Total         Free    %      ITotal       IFree    %
========        ====        =====         ====    =      ======       =====    =
   13601         low     291.4GiB     164.6GiB  56%       18.5M       18.5M 100%
   13602         low     291.4GiB     164.6GiB  56%       18.5M       18.5M 100%
   21701         low     291.2GiB     130.5GiB  45%       18.5M       16.2M  87%
   21702         low     291.2GiB     130.5GiB  45%       18.5M       16.2M  87%

# define mirrrogroups
[root@cottontail2 ~]# beegfs-ctl --addmirrorgroup --primary=21701 --secondary=13601 --groupid=1
[root@cottontail2 ~]# beegfs-ctl --addmirrorgroup --primary=13602 --secondary=21702 --groupid=2

[root@cottontail2 ~]# beegfs-ctl --listmirrorgroups
     BuddyGroupID   PrimaryTargetID SecondaryTargetID
     ============   =============== =================
                1             21701             13601
                2             13602             21702

# define buddygroups, numtargets=1
[root@cottontail2 ~]# beegfs-ctl --setpattern --buddymirror /mnt/beegfs/home1 --chunksize=512k --numtargets=1
New chunksize: 524288
New number of storage targets: 1
Path: /home1
Mount: /mnt/beegfs

[root@cottontail2 ~]# beegfs-ctl --setpattern --buddymirror /mnt/beegfs/home2 --chunksize=512k --numtargets=1
New chunksize: 524288
New number of storage targets: 1
Path: /home2
Mount: /mnt/beegfs

# drop /home/hmeij in /mnt/beegfs/home1/hmeij
[root@petaltail mysql_bak_ptt]# find /data/lv1/beegfs_storage/ -type f | wc -l
[root@petaltail mysql_bak_ptt]# find /data/lv2/beegfs_storage/ -type f | wc -l
[root@swallowtail data]# find /data/lv1/beegfs_storage/ -type f | wc -l
[root@swallowtail data]# find /data/lv2/beegfs_storage/ -type f | wc -l

# redefine with numtargets=2
# resync 

Resync Data #1

StorageSynchronization Link

If the primary storage target of a buddy group is unreachable, it will get marked as offline and a failover to the secondary target will be issued. In this case, the former secondary target will become the new primary target.

Testing out fail over and deletion of data on secondary then a full resync process:

  • started a full –resyncstorage –mirrorgroupid=101 –timestamp=0
  • got –getentryinfo EntryID for a file in my /mnt/beegfs/home/path/to/file and did the same for the directory the file was located in
  • did a cat /mnt/beegfs/home/path/to/file on a client (just fine)
  • brought primary storage down
  • redid the cat above (it hangs for a couple of minutes, then displays the file content)
  • while primary down, I ran rm -rf /mnt/beegfs/home/path/to/ removing directory holding file
  • a cat now generates the expected file not found error
  • brought up primary and started a full –resyncstorage –mirrorgroupid=101 –timestamp=0
  • the nr of files and dirs discovered is as expected lower by the correct values
  • when I now search for the EntryIDs obtained before they are gone from /data/beegfs-storage (as expected).

Nice that it works.

So you can full storage content mirror. You'll still need rsnapshots to recover lost data or point in time restores.

Mirror Data

When not all storage servers are up, client mounts will fail. This is just an optional “sanity check” which the client performs when it is mounted. Disable this check by setting “sysMountSanityCheckMS=0” in beegfs-client.conf. When the sanity check is disabled, the client mount will succeed even if no servers are running.

In order to able able to take a storage server off line without any impact, all content needs to mirrored.


[root@cottontail2 ~]# beegfs-df
TargetID        Pool        Total         Free    %      ITotal       IFree    %
========        ====        =====         ====    =      ======       =====    =
      48         low      29.5GiB      23.3GiB  79%        1.9M        1.5M  82%
      49         low      29.5GiB      23.1GiB  78%        1.9M        1.5M  82%
     250         low     122.3GiB     116.7GiB  95%        7.8M        7.6M  98%

TargetID        Pool        Total         Free    %      ITotal       IFree    %
========        ====        =====         ====    =      ======       =====    =
   13601         low     291.4GiB      50.6GiB  17%       18.5M       18.4M 100%
   21701         low     291.2GiB      61.8GiB  21%       18.5M       15.8M  85%


# define buddygroup - these are storage target IDs
[root@n7 ~]# beegfs-ctl --addmirrorgroup --primary=13601 --secondary=21701 --groupid=101
Mirror buddy group successfully set: groupID 101 -> target IDs 13601, 21701

[root@n7 ~]# beegfs-ctl --listmirrorgroups
     BuddyGroupID   PrimaryTargetID SecondaryTargetID
     ============   =============== =================
              101             13601             21701
# enable mirroring for data by directory -numTargets needs to be set to max nr of storage servers?
# changed to 11/02/2016:
[root@n7 ~]# beegfs-ctl --setpattern --buddymirror /mnt/beegfs/home --chunksize=512k 
[root@n7 ~]# beegfs-ctl --setpattern --buddymirror /mnt/beegfs/hmeij-mirror-data --chunksize=512k --numtargets=2
New chunksize: 524288
New number of storage targets: 2
Path: /hmeij-mirror-data
Mount: /mnt/beegfs

# copy some contents in (~hmeij is 10G)
[root@n7 ~]# rsync -vac --bwlimit /home/hmeij /mnt/beegfs/hmeij-mirror-data/ 


[root@n7 ~]# beegfs-df

METADATA SERVERS: (almost no changes...)
STORAGE TARGETS: (each target less circa 10G)
TargetID        Pool        Total         Free    %      ITotal       IFree    %
========        ====        =====         ====    =      ======       =====    =
   13601         low     291.4GiB      40.7GiB  14%       18.5M       18.4M  99%
   21701         low     291.2GiB      51.9GiB  18%       18.5M       15.8M  85%

# lets find an object
[root@n7 ~]# beegfs-ctl --getentryinfo /mnt/beegfs/hmeij-mirror-data/hmeij/xen/bvm1.img
Path: /hmeij-mirror-data/hmeij/xen/bvm1.img
Mount: /mnt/beegfs
EntryID: 178-581797C8-30
Metadata node: n38 [ID: 48]
Stripe pattern details:
+ Type: Buddy Mirror
+ Chunksize: 512K
+ Number of storage targets: desired: 2; actual: 1
+ Storage mirror buddy groups:
  + 101

# original
[root@n7 ~]# ls -lh /mnt/beegfs/hmeij-mirror-data/hmeij/xen/bvm1.img
-rwxr-xr-x 1 hmeij its 4.9G 2014-04-07 13:39 /mnt/beegfs/hmeij-mirror-data/hmeij/xen/bvm1.img

# copy on primary
[root@petaltail chroots]# ls -lh /var/chroots/data/beegfs_storage/buddymir/u2018/5817/9/60-58179513-30/178-581797C8-30
-rw-rw-rw- 1 root root 4.9G Apr  7  2014 /var/chroots/data/beegfs_storage/buddymir/u2018/5817/9/60-58179513-30/178-581797C8-30

# copy on secondary
[root@swallowtail ~]# find /data/beegfs_storage -name 178-581797C8-30
[root@swallowtail ~]# ls -lh /data/beegfs_storage/buddymir/u2018/5817/9/60-58179513-30/178-581797C8-30
-rw-rw-rw- 1 root root 4.9G Apr  7  2014 /data/beegfs_storage/buddymir/u2018/5817/9/60-58179513-30/178-581797C8-30

# seems to work, notice the ''buddymir'' directory on primary/secondary

Here is an important note, from community list:

  • “actual: 1” means “1 buddy mirror group”
    • so the important line that tells you that this file is mirrored is “Type: Buddy Mirror”.
  • “desired: 2” means you would like to stripe across 2 buddy groups. (targets are buddygroups here)

Another note: I changed paths for mirrormd and buddymirror to /mnt/beegfs/home and now I see connectivity data for meta node cottontail2 which was previously missing because I working on sub directory level.

[root@cottontail2 ~]# beegfs-net
cottontail2 [ID: 250]
   Connections: RDMA: 1 (;

[root@cottontail2 ~]# beegfs-ctl --listnodes --nodetype=meta --details
cottontail2 [ID: 250]
   Ports: UDP: 8005; TCP: 8005
   Interfaces: ib1(RDMA) ib1(TCP) eth1(TCP) eth0(TCP)


  • setup XFS
  • enable beegfs quota on all clients
  • enforce quota
    • set quotas using a text file
    • seems straightforward
  • do BEFORE populating XFS file systems

Meta Backup/Restore

External Link

# latest tar
rpm -Uvh /sanscratch/tmp/beegfs/tar-1.23-15.el6_8.x86_64.rpm

# backup
cd /data; tar czvf /sanscratch/tmp/beegfs/meta-backup/n38-meta.tar.gz beegfs_meta/ --xattrs

# restore
cd /data;  tar xvf /sanscratch/tmp/beegfs/meta-backup/n38-meta.tar.gz --xattrs

# test
cd /data; diff -r beegfs_meta beegfs_meta.orig
# no results

Resync Meta

External Link

  • older versions
  • new future version will work like storage mirror with HA and self-healing

Mirror Meta

Metadata mirroring can currently not be disabled after it has been enabled for a certain directory

Definitely want Meta content mirrored, that way I can use the n38-n45 nodes with local 15K disk, plus maybe cottontail2 (raid 1 with hot and cold spare).

Content mirroring will require more disk space. Perhaps snapshots to another node is more useful, also solves backup issue.

# enable meta mirroring, directory based
# change to 11/04/2016: used --createdir to make this home.
[root@n7 ~]# beegfs-ctl --mirrormd /mnt/beegfs/home
[root@n7 ~]# beegfs-ctl --mirrormd /mnt/beegfs/hmeij-mirror
Mount: '/mnt/beegfs'; Path: '/hmeij-mirror'
Operation succeeded.

# put some new content in 
[root@n7 ~]# rsync -vac /home/hmeij/iozone-tests /mnt/beegfs/hmeij-mirror/

# lookup meta tag
[root@n7 ~]# beegfs-ctl --getentryinfo /mnt/beegfs/hmeij-mirror/iozone-tests/current.tar
Path: /hmeij-mirror/iozone-tests/current.tar
Mount: /mnt/beegfs
EntryID: 3-581392E1-31

# find
[root@sharptail ~]# ssh n38 find /data/beegfs_meta -name 3-581392E1-31
                  ^^^^^^ ^^
# and find
[root@sharptail ~]# ssh n39 find /data/beegfs_meta -name 3-581392E1-31

# seems to work

Writing some initial content to both storage and meta servers; vanilla out of the box beegfs seems to balance the writes across both equally. Here are some stats.


  • Source content 110G in XFS with ~100,000 files in ~2,000 dirs
    • /home/hmeij (mix of files, nothing large) plus
    • /home/fstarr/filler (lots of tiny files)
  • File content spread across 2 storage servers
  • petaltail:/var/chroot/data/beegfs_storage
  • swallowtail:/data/beegfs_storage
  • 56G used in beegfs-storage per storage server
  • ~92,400 files per storage server
  • ~1,400 dirs per storage server mostly in “chunks” dir
  • Meta content spread across 2 meta servers (n37 and n38)
    • 338MB per beegfs-meta server so 0.006% space wise for 2 servers
    • ~105,000 files per metadata server
    • ~35,000 dirs almost spread evenly across “dentries” and “inodes”
  • Client (n7 and n8) see 110G in /mnt/beegfs
    • 110G in /mnt/beegfs
    • ~100,000 files
    • ~2,000 dirs

Looks like:

  • NOTE: failed to mount /mn/beegfs is the result of out of space storage servers.
# file content

[root@swallowtail ~]# ls -lR /data/beegfs_storage/chunks/u0/57E4/2/169-57E42E75-31
total 672
-rw-rw-rw- 1 root root 289442 Jun 26  2015 D8-57E42E89-30
-rw-rw-rw- 1 root root   3854 Jun 26  2015 D9-57E42E89-30
-rw-rw-rw- 1 root root  16966 Jun 26  2015 DA-57E42E89-30
-rw-rw-rw- 1 root root  65779 Jun 26  2015 DB-57E42E89-30
-rw-rw-rw- 1 root root  20562 Jun 26  2015 DF-57E42E89-30
-rw-rw-rw- 1 root root 259271 Jun 26  2015 E0-57E42E89-30
-rw-rw-rw- 1 root root    372 Jun 26  2015 E1-57E42E89-30

[root@petaltail ~]# ls -lR /var/chroots/data/beegfs_storage/chunks/u0/57E4/2/169-57E42E75-31
total 144
-rw-rw-rw- 1 root root     40 Jun 26  2015 DC-57E42E89-30
-rw-rw-rw- 1 root root  40948 Jun 26  2015 DD-57E42E89-30
-rw-rw-rw- 1 root root 100077 Jun 26  2015 DE-57E42E89-30

# meta content

[root@sharptail ~]# ssh n38 find /data/beegfs_meta -name 169-57E42E75-31

[root@sharptail ~]# ssh n39 find /data/beegfs_meta -name 169-57E42E75-31
(none, no mirror)


  • global interfaces files ib0→eth1→eth0
    • connInterfacesFile = /home/tmp/global/beegfs.connInterfacesFile
    • set in /etc/beegfs-[storage|client|meta|admon|mgmtd].conf and restart services
  • backup/restore/mirror
    • see more towards top this page
  • storage server tuning
    • set on cottontail on sdb, both values were 128 (seems to help – late summer 2016)
    • echo 4096 > /sys/block/sd?/queue/nr_requests
    • echo 4096 > /sys/block/sd?/queue/read_ahead_kb
    • set on cottontail, was 90112 + /etc/rc.local
    • echo 262144 > /proc/sys/vm/min_free_kbytes
  • do same on greentail? (done late fall 2016)
    • all original values same as cottontail (all files)
    • set on c1d1 thru c1d6
  • do same on sharptail?
    • no such values for sdb1
    • can only find min_free_kbytes, same value as cottontail
  • stripe and chunk size
[root@n7 ~]# beegfs-ctl --getentryinfo /mnt/beegfs/
Mount: /mnt/beegfs
EntryID: root
Metadata node: n38 [ID: 48]
Stripe pattern details:
+ Type: RAID0
+ Chunksize: 512K
+ Number of storage targets: desired: 4
  • The cache type can be set in the client config file (/etc/beegfs/beegfs-client.conf).
    • buffered is default, few 100k per file
  • tuneNumWorkers in all /etc/beegfs/beggfs-C.conf file
    • for meta, storage and clients …
  • metadata server tuning
    • read in more detail


  • made easy External Link
  • rpms pulled from repository via petaltail in greentail:/sanscratch/tmp/beegfs
[root@cottontail ~]# ssh n7 beegfs-net

cottontail [ID: 1]
   Connections: TCP: 1 (;

n38 [ID: 48]
   Connections: TCP: 1 (;
n39 [ID: 49]
   Connections: TCP: 1 (;

swallowtail [ID: 136]
   Connections: TCP: 1 ( [fallback route]);
petaltail [ID: 217]
   Connections: TCP: 1 ( [fallback route]);


cluster/151.1479756814.txt.gz · Last modified: 2016/11/21 14:33 by hmeij07