Blog
BeeGFS has grown up (quietly): Introducing 7.2.10, 7.3.4, and 7.4.0
30th June 2023 If you have seen the latest BeeGFS release notes you may be puzzled why we now have not two, but THREE release branches. Worry not, this is just another sign of the times, the buzziest file system is growing up. Record scratch–you’re probably wondering how we ended up here. Sometimes, BeeGFS is referred to as the "baby Lustre", a comparison we've always found amusing. It is, indeed, a fitting analogy, as BeeGFS has evolved by learning from the path paved by other High-Performance Computing (HPC) storage systems. Like a younger sibling benefiting from their elder’s experiences, BeeGFS Read More
On the importance of using connAuthFile in BeeGFS
10th May 2022 Yesterday, we were alerted to a conversation on Twitter about potential security issues with BeeGFS on systems that don't use a connAuthFile. If no such file is used to authenticate connections between nodes, it is possible to spoof network messages to BeeGFS servers which can be used to trigger file system operations. The code that is being discussed on Twitter uses that to create a setuid file, which can then later be used to gain root privileges on a connected client. We are aware of this issue and have always been advising our users to use connAuthFiles Read More
BeeGFS now supports NVIDIA Magnum IO GPUDirect Storage. So, what’s the big deal?
How did we get here? Where does BeeGFS need to go to support its users for years to come? What changes are needed to enable the next generation of AI and HPC workloads, not just today, but for the next decade and beyond? These are questions ThinkParQ and NetApp ask ourselves, our mutual customers, and the greater BeeGFS community almost obsessively. Read More
BeeGFS Data Management
by Peter Braam, CTO, ThinkParQ, January 2021 Welcome to the BeeGFS blog. I intend to occasionally publish some of our architectural thoughts, specifically to solicit feedback, publicly in blog comments or on our mailing list. Alternatively you can send an email to cto <at> thinkparq <dot> com. Probably we’ll find that posts here will be most useful during our early consideration of features, and perhaps there will be 2-4 posts per year. Read More