Category Archives: BeaST

Modelling basic architectures of data storage systems

Posted on 14.10.2020 by mezzantrop

Nowadays majority of the modern and powerful block-level storage systems around the world are built to work in expensive Fibre Channel or more cheaper iSCSI SAN environments. Independent of their class, capacity and performance they are created on well-known principles, … Continue reading →

Posted in BeaST, My projects | Tagged , , , , , , , | 1 Comment

The BeaST Grid storage early stage

Posted on 28.08.2020 by mezzantrop

I completely devoted my vacation to the development of the BeaST Grid family of my storage architecture and in the early days I was naive enough to plan a release. The Grid family was, and still is, the essential step … Continue reading →

Posted in BeaST, BeaST Quorum, My projects, Storage | Tagged , , , , , , | Leave a comment

FreeBSD 12.x CTL HA kernel panic

Posted on 27.08.2020 by mezzantrop

Recently I discovered the issue with kern.cam.ctl.ha_role kernel variable. At first, I wrongly suspected, that the problem appears when both iSCSI target and iSCSI initiator are configured on the system, but now, I have discovered that, the kernel panic happens … Continue reading →

Posted in BeaST, My projects | Tagged , , | 1 Comment

The BeaST storage concept side-notes

Posted on 12.08.2020 by mezzantrop

The BeaST Quorum daemon updated to version 1.2. Actually, I added only auto-detection of the block-size of the drive to work with sectors larger than 512 bytes. While trying to setup the Grid configuration of the BeaST storage system concept … Continue reading →

Posted in BeaST, BeaST Quorum, Storage | Tagged , , , , , | 2 Comments

The real hardware for the BeaST storage system

Posted on 18.01.2019 by mezzantrop

Shortly after I finished developing the BeaST storage system concept and ended testing it in the virtual environment I faced a problem of how to find a two-headed bare-metal server with a bunch of shared drives. In fact I did … Continue reading →

Posted in BeaST, IRL, My projects, Storage | Tagged , | 1 Comment

My 2018 as a free software developer

Posted on 20.11.2018 by mezzantrop

The year is almost near the end and I’m feeling Christmas in the air already, now it’s time to recall what was done and count some results. So, the first half of the year I used GitHub as a platform to … Continue reading →

Posted in BeaST, BeaST Quorum, Misc, My projects, sp_ping, svcstats.py | Tagged , , , , , , , , , | Leave a comment

Configuring Linux server to work with the BeaST storage system over iSCSI protocol

Posted on 26.10.2018 by mezzantrop

I continue to test the BeaST on a real hardware and here is an update to the Linux client configuration guide:

Posted in BeaST, Storage | Tagged , , , , , , | Leave a comment

Compare two regular or device files block by block

Posted on 22.07.2018 by mezzantrop

Yes, there are a number of utilities like cmp, bdiff and etc that allow to compare binary files and even create patches.Β Anyway, here is my script, which I hope, will ease tracking changes on block granularity within storage volumes and … Continue reading →

Posted in BeaST, BeaST Quorum, Storage, Storage Automation | Tagged , , , , , , | Leave a comment

Configuring Linux server to work with the BeaST storage system over iSCSI protocol

Posted on 14.07.2018 by mezzantrop

It’s weekend, so I continue to work on the BeaST storage system. Here is my small HOW-TO describing multipath connection with the BeaST from a RHEL/Centos Linux server via iSCSI:Β Configuring Linux server to work with the BeaST storage system over … Continue reading →

Posted in BeaST, My projects, Storage | Tagged , , , , , , , , , | Leave a comment

The BeaST again!

Posted on 03.06.2018 by mezzantrop

I’m working hard now to run the BeaST Storage system on the real hardware and hope to have some results and good news to post in the future. Meanwhile, I have updatedΒ The BeaST Classic – dual-controller storage system with RAID … Continue reading →

Posted in BeaST, Storage Automation | Tagged , , , , , , , , , | Leave a comment