Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1877174
| Summary: | RFE: --btrfs option to help with troubleshooting btrfs specific issues | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chris Murphy <bugzilla> |
| Component: | fpaste | Assignee: | Ankur Sinha (FranciscoD) <sanjay.ankur> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 33 | CC: | jcpunk, kevin, lef, ngompa13, sanjay.ankur |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | fpaste-0.4.1.0-1.fc32 fpaste-0.4.1.0-1.fc33 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-09-19 22:39:03 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Chris Murphy
2020-09-09 01:56:24 UTC
Thanks, fpaste doesn't have different flags for different types of information. So, I'll just add it all to --sysinfo, which collects any system information in fpaste. I've opened a tracker ticket upstream now: https://pagure.io/fpaste/issue/44 Is there a timeline you'd like this done in? There's no urgency. In the meantime we can just ask for it: command|fpaste, post url. Thanks! On difference compared to --sysinfo is that for btrfs issues we often need the entire dmesg because problems can be related to other parts of the kernel, like SATA or USB errors. Therefore the 2nd bullet "* Kernel (uname -r ; cat /proc/cmdline)" is superfluous. We don't need that. The dmesg will have that. I do like 'journalctl -k' best because in some cases where the user needs to issue something like sysrq+w or t, it will totally fill up the dmesg buffer, but journalctl -k will have everything. It's so much more information than --sysinfo, that's why I was suggesting another flag. It could be --sysinfo2 or --sysinfoextra or whatever you want, if you prefer to keep the original one more concise. I added an option here. Could you test it out and see if it works? I'm not on btrfs yet: https://pagure.io/fpaste/tree/btrfs If that works, I can merge that and cut a new release. It works! On second thought we could omit "OS Release" entirely. It's clear from the kernel and btrfs-progs package versions. And saves 25 lines. Great, thanks for the quick test. I've removed the OS Release bit now. I'll cut a new release and push an update. FEDORA-2020-b12aeb8e45 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-b12aeb8e45 FEDORA-2020-86cfc4ffd3 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-86cfc4ffd3 FEDORA-2020-b12aeb8e45 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-b12aeb8e45` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-b12aeb8e45 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-86cfc4ffd3 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-86cfc4ffd3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-86cfc4ffd3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-86cfc4ffd3 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-b12aeb8e45 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. |