August 2022 - test - Fedora Mailing-Lists

Re: mount fails for btrfs filesystem, need help please.

by George R Goffe

Howdy, Thanks to all who responded... Chris, I tried the superblock mount but that still fails. Then I tried the rescue=all mount. That succeeded... I have copied all the files I need. From what I read, corrupted files get copied too... and there were some which I removed from the copies. From "https://lists.fedoraproject.org/archives/search?mlist=users%40lists.fedor..." I found some other commands that you wrote. I presume after unmounting this problematic filesystem. Is it time to run them? I'm not sure what they'll do though. btrfs rescue zero-log btrfs check --repair --init-extent-tree btrfs check --repair Please advise. Regards, George... Date: Mon, 22 Aug 2022 11:46:16 -0400 From: "Chris Murphy" <lists(a)colorremedies.com> Subject: Re: mount fails for btrfs filesystem, need help please. To: "For releases" <test(a)lists.fedoraproject.org> Message-ID: <efeb6908-565f-44ae-8cda-f487266c22d4(a)www.fastmail.com> Content-Type: text/plain On Sun, Aug 21, 2022, at 11:02 PM, George R Goffe via test wrote: > Hi, > > I started getting i/o error messages accessing this filesystem so I > rebooted the system. This might have been the wrong thing to do. This > subsequent boot went to maintenance mode due the filesystem's path > being in /etc/fstab. > > I need some help with this please. Here is what mount says: > > mount /dev/sda6 /opt. > > kernel: BTRFS info (device sda6): flagging fs with big metadata feature > kernel: BTRFS info (device sda6): disk space caching is enabled > kernel: BTRFS info (device sda6): has skinny extents > kernel: BTRFS error (device sda6): parent transid verify failed on > 148312850432 wanted 73476 found 73484 It usually means the hardware is not honoring the proper write order, by (occasionally) ignoring flush/FUA. And in this case Btrfs can be really sensitive to the problem. I suggest mounting with `-o ro,rescue=all` which gives the best chance of not changing the file system, while getting access to important files you maybe don't have backed up - and get them off while you can. Also while you're at it you can do: journalctl --since=yesterday -o short-monotonic --no-hostname | grep "Linux version\| ata\|Btrfs\|BTRFS\|] hd\| scsi\| sd\| sdhci\| mmc\| nvme\| usb\| vd" -D /mnt/root/var/log/journal I'm assuming you mount the volume at /mnt. You can copy off important files from /mnt/home/$username normally using any command you're familiar with. After that, you can umount the file system. And mount again with '-o rescue=usebackuproot' and hopefully it finds a good backup root, and can fix itself. If it gets confused again, it'll go read only to avoid making things worse. -- Chris Murphy

1 year, 8 months

2
1
0 / 0

mount fails for btrfs filesystem, need help please.

by George R Goffe

Hi, I started getting i/o error messages accessing this filesystem so I rebooted the system. This might have been the wrong thing to do. This subsequent boot went to maintenance mode due the filesystem's path being in /etc/fstab. I need some help with this please. Here is what mount says: mount /dev/sda6 /opt. kernel: BTRFS info (device sda6): flagging fs with big metadata feature kernel: BTRFS info (device sda6): disk space caching is enabled kernel: BTRFS info (device sda6): has skinny extents kernel: BTRFS error (device sda6): parent transid verify failed on 148312850432 wanted 73476 found 73484 kernel: BTRFS error (device sda6): failed to read block groups: -5 kernel: BTRFS error (device sda6): open_ctree failed

1 year, 8 months

4
5
0 / 0

Re: 2022-08-22 @ 16:00 UTC - Fedora 37 Blocker Review Meeting

by Luna Jernberg

Will try to show up On Mon, Aug 22, 2022 at 8:28 AM Adam Williamson <adamwill(a)fedoraproject.org> wrote: > # F36 Blocker Review meeting > # Date: 2022-08-22 > # Time: 16:00 UTC > # Location: #fedora-blocker-review on irc.libera.chat > > Hi folks! We have 3 proposed Beta blockers, 1 proposed Beta freeze > exception issue, and 13 proposed Final blockers to review, so let's > have a review meeting. Note, I'll try and cut that number > of Final blockers down before the meeting - it'll help if folks can > vote ahead. > > If you have time today, you can take a look at the proposed or > accepted blockers before the meeting - the full lists can be found > here: https://qa.fedoraproject.org/blockerbugs/ . > > Remember, you can also now vote on bugs outside of review meetings! If > you look at the bug list in the blockerbugs app, you'll see links > labeled "Vote!" next to all proposed blockers and freeze exceptions. > Those links take you to tickets where you can vote. > https://pagure.io/fedora-qa/blocker-review has instructions on how > exactly you do it. We usually go through the tickets shortly before the > meeting and apply any clear votes, so the meeting will just cover bugs > where there wasn't a clear outcome in the ticket voting yet. **THIS > MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** > > We'll be evaluating these bugs to see if they violate any of the > Release Criteria and warrant the blocking of a release if they're not > fixed. Information on the release criteria for F36 can be found on the > wiki [0]. > > For more information about the Blocker and Freeze exception process, > check out these links: > - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process > - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process > > And for those of you who are curious how a Blocker Review Meeting > works - or how it's supposed to go and you want to run one - check out > the SOP on the wiki: > - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting > > Have a good night/day and see you tomorrow/later today! > > [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria > -- > Adam Williamson > Fedora QA > IRC: adamw | Twitter: adamw_ha > https://www.happyassassin.net > > _______________________________________________ > desktop mailing list -- desktop(a)lists.fedoraproject.org > To unsubscribe send an email to desktop-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject... > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue >

1 year, 8 months

1
0
0 / 0

Re: [Test-Announce] Proposal to CANCEL: 2022-08-22 Fedora QA Meeting

by Tim Flink

At some point, we do need to wrap up the TCMS conversation. If not this week then hopefully next week or the week after. Tim On 8/22/22 00:25, Adam Williamson wrote: > Hi folks! I'm proposing we cancel the QA meeting today/tomrrow. I > don't have anything much for the agenda again. There will be a > blocker review meeting, though. > > If you're aware of anything it would be useful to discuss this week, > please do reply to this mail and we can run the meeting. > > Thanks folks!

1 year, 8 months

1
0
0 / 0

rpm -ivh kernel installation put no vmlinuz* in /boot/

by Felix Miata

Is this normal procedure now in rawhide? I copied vmlinuz directly from the rpm to /boot/ and renamed it vmlinuz-5.19.0-0.rc8.20220729git6e2c0490769e.62.fc37.x86_64, though I could have symlinked its location in the /lib/modules tree. It works. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

1 year, 8 months

2
9
0 / 0

test with debug kernel for F37 with DKMS ...

by Cătălin George Feștilă

I try to test the dkms for Huion WH tablet but I think this cannot be done with debug kernel , right ? https://github.com/DIGImend/digimend-kernel-drivers [root@fedora mythcat]# ls /usr/src/kernels/ 5.19.0-65.fc37.x86_64+debug [root@fedora mythcat]# dkms build digimend/6 EFI variables are not supported on this system Sign command: /lib/modules/5.19.0-65.fc37.x86_64/build/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Binary sign-file not found, module won't be signed Error! Your kernel headers for kernel 5.19.0-65.fc37.x86_64 cannot be found at /lib/modules/5.19.0-65.fc37.x86_64/build or /lib/modules/5.19.0-65.fc37.x86_64/source. Please install the linux-headers-5.19.0-65.fc37.x86_64 package or use the --kernelsourcedir option to tell DKMS where it's located.

1 year, 8 months

2
3
0 / 0

Fedora 37 Spin Python tested on VirtualBox on Windows 11

by Cătălin George Feștilă

You can see is something wrong in this console area ... maybe because my hardware is old. I try with two download iso files and run it like administrator, but the same strange string. https://imgur.com/CcG7RkB

1 year, 8 months

1
0
0 / 0

Testing FWS F37 branched 20220816.n.0

by pmkellly＠frontier.com

Good day everyone, Testing FWS F37 branched 20220816.n.0. This was a bare metal install on a Lenovo M53 with a i5-4570 CPU. The ISO was check summed and passed then loaded to a thumb drive using Media Writer. The test machine booted to Live normally when the (start F37 live) was selected in Grub. Anaconda started normally. Options to delete all and reclaim space were selected for the hard drive. Install ran normally. The reboot to the hard drive was normal. Part two of the install was normal. When the (test media then start F37) was selected in Grub the media test would not run due to lack of files "[ 5.973632] dracut-pre-udev[501]: sh: line 1: /sbin/sysctl: No such file or directory The media check is complete, the result is: NA. No checksum information available, unable to verify media". this has been the case since I started testing F37 branched. I did not file a bug report since I think this is probably already receiving lots of attention. From my results F37 seems in rather good condition at this stage. I'm particularly please by the fact that my HL-L6200DW printer installs during the Fedora install process and the only thing I have to do is set double sided printing. It even works with Firefox. The only unique problems (don't already have a bug report) I found had to do with things that aren't in the repository yet so I can't install them. These were codecs and OBS-Studio. The packages for F37 seem to be available, but aren't in the F37 repo yet. Not a problem at this stage. Have a Great Day! Pat (tablepc)

1 year, 8 months

1
0
0 / 0

IoT testing page cleanups

by Brandon Nielsen

I've been meaning to ask these questions for awhile but keep forgetting. In regards to IoT test pages, such as for the latest nominated compose[0]: 1 - My understanding is the non-ostree composes aren't intended for general consumption[1]. Is it feasible to remove them from the downloads list? Where would I poke about to do that? Assuming it's feasible, I'll go double check on the IoT list[2] if it would be okay to do so. 2 - The "Wired Network" result doesn't appear in relval. Would that be fixed "automatically" if I add a "Wired Network" section to the QA:TestCase_IoT_Hardware[3] page, and then add a corresponding link to the Template:General_IoT_test_matrix page[4]? Thanks for any guidance, just wanted to double check before I break everything. [0] - https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_36_RC_20220302.0_S... [1] - https://bugzilla.redhat.com/show_bug.cgi?id=2002840#c1 [2] - https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org/ [3] - https://fedoraproject.org/wiki/QA:Testcase_IoT_Hardware [4] - https://fedoraproject.org/wiki/Template:General_IoT_test_matrix

1 year, 8 months

2
3
0 / 0

Re: [Test-Announce] Proposal to CANCEL: 2022-08-01 Fedora QA Meeting

by Luna Jernberg

The Bug Blocker Review meeting got cancelled today as Ben has other things to take care of On Mon, Aug 15, 2022 at 2:23 PM Adam Williamson <adamwill(a)fedoraproject.org> wrote: > Hi folks! Sorry for the late notice, but I'm proposing we cancel the > QA meeting today. I am going to be on a plane to devconf.us, so I > won't be able to run it. > > Thanks folks! > -- > Adam Williamson > Fedora QA > IRC: adamw | Twitter: adamw_ha > https://www.happyassassin.net > > _______________________________________________ > test-announce mailing list -- test-announce(a)lists.fedoraproject.org > To unsubscribe send an email to > test-announce-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/test-announce@lists.fedorap... > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue >

1 year, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test August 2022