New upstream version 8.1.0

This commit is contained in:
geos_one
2025-08-10 01:34:16 +02:00
commit c891bb7105
4398 changed files with 838833 additions and 0 deletions

35
.github/ISSUE_TEMPLATE/bug_report.md vendored Normal file
View File

@@ -0,0 +1,35 @@
---
name: Bug report
about: Create a report to help us improve BeeGFS
title: ''
labels: bug, new
assignees: ''
---
**Describe the bug**
A clear and concise description of what the bug is, which component (mgmtd, meta, storage, client, others or any combination) is affected and what effects (error messages, performance degradation, crashes, ...) can be observed.
**Describe the system**
A short description of the system BeeGFS is running on that covers all information relevant to the issue. For example (but not limited to):
1. Number and type of BeeGFS services and their distribution across physical machines
2. Information about the network interconnect (technology, protocols, topology)
3. Information about underlying file systems and storage hardware
4. Operating system and proprietary driver information (versions, RDMA drivers)
5. Software that is accessing BeeGFS
**To Reproduce**
Steps to reproduce the behavior:
1. Set configuration option "x" to "y" for component "c"
2. Start component "c" on machine "m"
3. Run application "a" with parameters "p"
4. Observe behavior "b"
**Expected behavior**
A clear and concise description of what you expected to happen.
**Log messages, error outputs**
If available, add relevant log files (anonymize if necessary), error messages, `perf` measurements, `strace` outputs, core dumps and everything else you have collected and can share publicly.
**Additional context**
Add any other context not covered above.

View File

@@ -0,0 +1,20 @@
---
name: Feature request
about: Suggest a feature or improvement for BeeGFS
title: ''
labels: enhancement, new
assignees: ''
---
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context about the feature request here.