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 - RFE: --btrfs option to help with troubleshooting btrfs specific issues
Summary: RFE: --btrfs option to help with troubleshooting btrfs specific issues
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fpaste
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ankur Sinha (FranciscoD)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-09 01:56 UTC by Chris Murphy
Modified: 2020-09-25 16:58 UTC (History)
5 users (show)

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:
Clone Of:
Environment:
Last Closed: 2020-09-19 22:39:03 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Pagure fpaste issue 44 0 None None None 2020-09-09 08:01:32 UTC

Description Chris Murphy 2020-09-09 01:56:24 UTC 
Discussion:
https://pagure.io/fedora-btrfs/project/issue/15

* OS Release (grep PRETTY_NAME /etc/os-release)
* Kernel (uname -r ; cat /proc/cmdline)
* btrfs-progs (rpm -q btrfs-progs)
* Mounts (grep btrfs /proc/mounts)
* Block devices (lsblk -ft)
* Kernel messages (journalctl -o short-monotonic --no-hostname -k)
* Btrfs usage (btrfs filesystem usage -T /)


Leaving device stats out for now since it requires root privileges. Usually such stats, if relevant, end up in kernel messages if they're a factor.
Comment 1 Ankur Sinha (FranciscoD) 2020-09-09 08:01:32 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?
Comment 2 Chris Murphy 2020-09-09 17:35:46 UTC 
There's no urgency. In the meantime we can just ask for it: command|fpaste, post url. Thanks!
Comment 3 Chris Murphy 2020-09-09 17:40:28 UTC 
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.
Comment 4 Ankur Sinha (FranciscoD) 2020-09-13 16:27:48 UTC 
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.
Comment 5 Chris Murphy 2020-09-14 20:12:56 UTC 
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.
Comment 6 Ankur Sinha (FranciscoD) 2020-09-14 20:29:19 UTC 
Great, thanks for the quick test. I've removed the OS Release bit now. I'll cut a new release and push an update.
Comment 7 Fedora Update System 2020-09-14 20:42:59 UTC 
FEDORA-2020-b12aeb8e45 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-b12aeb8e45
Comment 8 Fedora Update System 2020-09-14 20:43:00 UTC 
FEDORA-2020-86cfc4ffd3 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-86cfc4ffd3
Comment 9 Fedora Update System 2020-09-15 14:53:40 UTC 
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.
Comment 10 Fedora Update System 2020-09-15 16:23:12 UTC 
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.
Comment 11 Fedora Update System 2020-09-19 22:39:03 UTC 
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.
Comment 12 Fedora Update System 2020-09-25 16:58:16 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.