Re: Is there an officially Fedora supported replacement for the old rc.local? - still an issue
On Mon, Jul 18, 2022 at 10:50:03PM +0200, Peter Boy wrote: Am 18.07.2022 um 22:18 schrieb Peter Boy : I got it finally working. After some tests: It isn’t. The programs I have to start depend on the existence of some (virtual) network interfaces. rc.local is ordered after network.target, which doesn’t mean, the network is functional then. Therefore, the program start via rc.local is in indeterministic process. Sometimes it works, sometimes not, sometimes only for some. Maybe this from: SYSTEMD-RC-LOCAL-GENERATOR(8) Also note that rc-local.service is ordered after network.target, which does not mean that the network is functional, see systemd.special(7). If the script requires a configured network connection, it may be desirable to pull in and order it after network-online.target with a drop-in: # /etc/systemd/system/rc-local.service.d/network.conf [Unit] Wants=network-online.target After=network-online.target Documentation mentions a drop in at /etc/systemd/system/rc-local.service.d/network.conf. But there is no subdirectory /etc/systemd/system/rc-local.service.d/ Should I really mess around with vim and mkdir in the directories managed by the distribution? Seems like a bad idea to me. Or have I missed something? Am 18.07.2022 um 18:08 schrieb Tom Horsley : Is it really gone, or are they simply not creating the rc.local file any longer? The file is really gone. You have to create it at the right location. The documentation is inconsistent. Some say /etc/rc.local, some /etc/rc.d/rc.local. The latter is correct. What I did: (1) Create /etc/rc.d/rc.local (with bash shebang), put in the execute commands needed, made it executable for user und group root (but just user root should be ok). (2) Executed /usr/lib/systemd/system-generators/systemd-rc-local-generator Is not on the path, you have to enter the complete path yourself - great. This step is indispensable! (3) Reboot, voila the included programs got started. I think, this is a better way than to hide the execute commands in user root’s crontab. Thanks for all the support! ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure End of included message <<< -- Jon H. LaBadie jo...@jgcomp.com ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: qemu crashes kernel-5.18.11-200.fc36.x86_64
On 19/07/2022 07.42, Sam Varshavchik wrote: Am I the only one lucky enough to have kernel-5.18.11-200.fc36.x86_64 crash reliably, on particular hardware, after starting a VM in virt-manager? At least I think it's a crash. One second after a VM start it's brick-city. Display frozen, no response from the network. I've got nothing: after a reboot there's nothing in journalctl -r -b -1. This brings up fond memories -- ages ago I had a null modem adapter hooked up to a serial port, the kernel configured for a serial console, thusly I was able to capture OOPSes over the serial console, in situations like these. But, these days, no more RS-232 ports. I dimly recall that a USB-serial option is possible; but I don't have any of that in any case. Anyway, reverting to 5.18.9 made this VM happy, and my VMs on another hardware, also running the same kernel, are also fine. But, 5.18.11 gets reliably clusterfarked by qemu on at least on some hardware combinations. I wish I had more useful data points, but I've got nuthin' worth putting into Bugzilla. Just a data point for you. I run 5.18.11-200.fc36.x86_64 on the host and on the guest (KVM). No crashes so far. However, sound is now broken, highly distorted, so maybe there is something bad with this kernel? You bay want to set rsyslog to log to the host, hoping to catch messages that did not make it to the guests fs. I have all my machines log to my server (which is the host too). A special, long incantation is appended to /etc/rsyslog.conf (on the guest). On the host I Provided TCP/UDP syslog reception in the same conf file. -- Eyal Lebedinsky (fed...@eyal.emu.id.au) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there an officially Fedora supported replacement for the old rc.local? - still an issue
> Am 18.07.2022 um 23:17 schrieb Garry T. Williams : > > and then create a .service file to run whatever program you want to > start at boot-time. Yeah, that’s the correct way. But in my case I don’t need a permanent solution (hopefully). I have to start some systemd containers, which of course already have a service file. Unfortunately, the autostart function doesn’t work, specifically with virtual interfaces of the host which the container depends on. I proposed a bug fix using network-online target instead of network target. It worked until F35, but with F36 the autostart function is removed and made a „FutureFeature“. So it is „broken by design“, but hopefully temporarily (whatever that means in terms of the timeframe). ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: A simple question
sudo inxi with various parameters? suomi On 18/07/2022 22.56, Garry T. Williams wrote: On Saturday, July 16, 2022 2:55:25 PM EDT Joe Zeff wrote: Recently, my laptop died and I had to buy a new one. Now, I'd like to take a look at what hardware is inside. I know that there used to be a program to show you all of the hardware, but it's been so long since I needed it that I can't remember its name. I'd appreciate it if somebody could point me in the right direction. You might try sudo fpaste --sysinfo to see what it does. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Is it possible to protect OpenSSH Daemon logins with 2nd factor authentication (2FA)?
Subject: Is it possible to protect OpenSSH Daemon logins with 2nd factor authentication (2FA)? Good day from Singapore, Is it possible to protect OpenSSH Daemon logins with 2nd factor authentication (2FA)? If it is possible, could you give me the links to excellent and well-written guides on how to do so? Thank you very much. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore 19 July 2022 Tuesday Blogs: https://tdtemcerts.blogspot.com https://tdtemcerts.wordpress.com ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: diagnosing XFS corruption after upgrading to Fedora 36
Just to close this out, and not be "that guy" (https://xkcd.com/979/), I ended up just rolling the kernel back to the Fedora 35 kernel (5.14.10). Without a good way to isolate where the problem is (between XFS & LVM), I really didn't want to waste time tracking this down, and restoring my system every couple hours. I'll try again in 6 months or so and see if maybe it's been found and fixed. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: qemu crashes kernel-5.18.11-200.fc36.x86_64
On Mon, 2022-07-18 at 17:42 -0400, Sam Varshavchik wrote: > But, these days, no more RS-232 ports. If it's not a laptop, there may still be one. But just on a header that needs a flylead to an external connector. -- uname -rsvp Linux 3.10.0-1160.71.1.el7.x86_64 #1 SMP Tue Jun 28 15:37:28 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there an officially Fedora supported replacement for the old rc.local?
On Mon, 2022-07-18 at 22:18 +0200, Peter Boy wrote: > The documentation is inconsistent. Some say /etc/rc.local, some > /etc/rc.d/rc.local. The latter is correct. On my other OS, /etc/rc.local is a symlink to the other one, which must be chmod +x (it starts off without it). I dare say the linking is so that it works where older users expect it to be, before they move it to the newer location (where it makes no sense, since what you put in it is not a daemon). -- uname -rsvp Linux 3.10.0-1160.71.1.el7.x86_64 #1 SMP Tue Jun 28 15:37:28 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there an officially Fedora supported replacement for,> the old rc.local? - still an issue
Am 18.07.2022 um 22:18 schrieb Peter Boy: wrote I got it finally working. After some tests: It isn’t. The programs I have to start depend on the existence of some (virtual) network interfaces. rc.local is ordered after network.target, which doesn’t mean, the network is functional then. Therefore, the program start via rc.local is in indeterministic process. Sometimes it works, sometimes not, sometimes only for some. Documentation mentions a drop in at/etc/systemd/system/rc-local.service.d/network.conf. But there is no subdirectory /etc/systemd/system/rc-local.service.d/ Should I really mess around with vim and mkdir in the directories managed by the distribution? Seems like a bad idea to me. Or have I missed something? There is a cleaner workaround, which does, unfortunately mean you have to do some minor file amendments (with vim, *of course*!) Your original /etc/rc.d/rc.local is renamed: mv rc.local the-real-rc.local /etc/rc.d/rc.local is replaced with a new version: #!/bin/bash # to run rc.local type things, without interference from systemd # rc-local: /usr/bin/at -M now <<'HERE' > /dev/null 2>&1 /etc/rc.d/the-real-rc.local HERE # And everything I used to run in rc.local now gets run # from the-real-rc.local, untouched by systemd meddling # (Resistance was futile, I was assimilated). Both of these files have to be executable (chmod 755). The /usr/systemd/rc-local.service file IS NOT TOUCHED, so there are no problems with it being overwritten. (might need to be enabled. I cannot remember.) The rc-local service checks the rc.local file, and IF it is executable, will run it. The new version rc.local calls 'the-real-rc.local'. Your 'the-real-rc.local' file can have a sleep or structured pause until the networks respond properly and signal they are awake. This sleight-of-hand was posted by someone on an Arch distro forum/mailing list. I do not have his name, but kudos and thanks whoever you are. It works In addition, you can also split your 'real' file, by creating a semaphore file in /tmp, and run different sections. If you prefer you can run a 'real' files only on the first run after a boot, or even after an install. If you have not yet changed, for example, /var/lib/mysql from a directory to a link to somewhere else, then this is the first run after a re-install, and that has not yet been done: an install, in my experience, whether told to format or not to format, will wipe the /var partition, and all of the databases in that folder. I put them elsewhere and link to there, so no losses. So obviously one thing I want to do is change the folder to a link to the proper place. And obviously there are a plethora of things which need to be done *once* after an install. Needs one 'if' statement in the bash script. A re-run will skip the block. Geoff ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Cannot connect to 2g wireless network
On 7/18/22 14:44, c. marlow wrote: I just got a Lenovo ThinkPad 3rd gen I installed Fedora 36 KDE on it And I cannot get it to connect to the 2G connection. It only will allow me to connect to the 5g connection. From the subject and even that description, I thought you were talking about a cell phone connection. Wifi is 2.4GHz. I have changed the name of the access point, changed the password several times only letters and numbers, letters numbers and basic symbols, no symbols... Nothing... I even downloaded Fedora 36 XFCE and ran the Live ISO.. Same thing... The Workstation live image would be a better test. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: custom '.local' folder - ?
On 18Jul2022 12:05, lejeczek wrote: >Won't do for me - fails with any bit more "complex" case when multiple >nodes are involved and user landing on each such node would have >unique/different '.local' dir, having whole home dir net mounted. If the whole homedir is net mountd (shared from a central storage server, yes?) what does the .local actually do? Surely as things are it would be common to all. Or is that the problem you're trying to solve? If so, you really need to sort out some per-node persistent personal area. That might need a per-node custom solution :-( And /tmp might be too unstable for you. And you'd still need to get things to hook into it of course... >I was hoping (& expecting) that would be controlled via a env var but >it does not seem that way - which makes me wonder - that must the >software which knows/chooses '.local' internally or might ignore that >all rogether and use own path(s), if it is not the OS providing that >information? hmm.. It will be per app. There are some conventions, which is why all these things land in .local, but each app will honour them in its own way. I do not know if there is a recommended envvar to govern ~/.local as a whole. You may need to find a solution on a per-app basis. Note that your _should_ be able to fiddle the $HOME envvar. How well that works again depends on the app, but you'd hope that most things would use it in _preference_ to looking up your homedir from the passwd mapping. Then you can do a hack like: SHARED_HOME=$HOME HOME=$SHARED_HOME/.local-`hostname` export HOME SHARED_HOME in your startup. And then you can put symlinks in $SHARED_HOME for the common top level things (.profile, etc etc) but have a per-hostname .local. A bit inverted, and some things will doubtless not play nicely. Cheers, Cameron Simpson ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Cannot connect to 2g wireless network
Hi Ya'll, I just got a Lenovo ThinkPad 3rd gen I installed Fedora 36 KDE on it And I cannot get it to connect to the 2G connection. It only will allow me to connect to the 5g connection. I have changed the name of the access point, changed the password several times only letters and numbers, letters numbers and basic symbols, no symbols... Nothing... I even downloaded Fedora 36 XFCE and ran the Live ISO.. Same thing... Here is a list of things that i've tried already: https://www.reddit.com/r/kde/comments/w1lu9b/comment/ignuby6/? %2524deep_link=true_id=20d64062-9dc4-4bba-9118- b37f22c5ace2=email_comment_reply_campaign=email_comment_reply_source=email&%25243p=e_as&_branch_match_id=1077582248353422136_medium=Email%20Amazon%20SES&_branch_referrer=H4sIA32O22rDMAyGnya7S9LYWbYMyhiMvYZQbKU1dWwjO5i%2B%2FRTa3Q4kocP3S7qWkvJH3zNZ60qHKXXehVuv02ejRp3OBJhfJI3sLi6gh539%2BXqoGv3VqB%2BxWmv31Ju4SYPFb5YkSr1RKPmgBr%2FPy2MC1XkPIRZAYygVqVcHCXOuka0w7hL25T4d%2B7WcGC1RguOxRn8X3mX1ZCIzeSwuBnBW%2Bupkp%2FE0qXa2ZmzHZcF2Hob3dtFvq1LmFQ0p0TGtAtOGzsPzPWBK%2Fv6YgcEtodz%2FF8pxZ0N%2FyC%2BAHs7bRQEAAA%3D%3D I am stumped I am hoping maybe someone will be able to figure this out! --- Thanks, Chris Please send all off list messages to ch...@cwm030.com ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
qemu crashes kernel-5.18.11-200.fc36.x86_64
Am I the only one lucky enough to have kernel-5.18.11-200.fc36.x86_64 crash reliably, on particular hardware, after starting a VM in virt-manager? At least I think it's a crash. One second after a VM start it's brick-city. Display frozen, no response from the network. I've got nothing: after a reboot there's nothing in journalctl -r -b -1. This brings up fond memories -- ages ago I had a null modem adapter hooked up to a serial port, the kernel configured for a serial console, thusly I was able to capture OOPSes over the serial console, in situations like these. But, these days, no more RS-232 ports. I dimly recall that a USB-serial option is possible; but I don't have any of that in any case. Anyway, reverting to 5.18.9 made this VM happy, and my VMs on another hardware, also running the same kernel, are also fine. But, 5.18.11 gets reliably clusterfarked by qemu on at least on some hardware combinations. I wish I had more useful data points, but I've got nuthin' worth putting into Bugzilla. pgpOLK_izNWTF.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there an officially Fedora supported replacement for the old rc.local? - still an issue
On Mon, 18 Jul 2022 22:50:03 +0200 Peter Boy wrote: > The programs I have to start depend on the existence of some (virtual) > network interfaces. Yea, when I was doing stuff with rc.local I had that problem as well. What I wound up doing was using the "at" command to start the scripts I really wanted to run about 20 or 30 seconds after rc.local is executed (picking time delays that always seemed to work well enough). P.S. You can't just do a "sleep" because systemd hates rc.local jobs that don't finish right away and kills them off (or it did at one time anyway). Using the "at" command runs them separately so systemd is no longer involved. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there an officially Fedora supported replacement for the old rc.local? - still an issue
On Monday, July 18, 2022 4:50:03 PM EDT Peter Boy wrote: > > Am 18.07.2022 um 22:18 schrieb Peter Boy : > > > > I got it finally working. > > After some tests: It isn’t. > > The programs I have to start depend on the existence of some > (virtual) network interfaces. rc.local is ordered after > network.target, which doesn’t mean, the network is functional then. > Therefore, the program start via rc.local is in indeterministic > process. Sometimes it works, sometimes not, sometimes only for some. You probably should (carefully) read this: https://systemd.io/NETWORK_ONLINE/ and then create a .service file to run whatever program you want to start at boot-time. -- Garry T. Williams ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: A simple question
On Saturday, July 16, 2022 2:55:25 PM EDT Joe Zeff wrote: > Recently, my laptop died and I had to buy a new one. Now, I'd like > to take a look at what hardware is inside. I know that there used > to be a program to show you all of the hardware, but it's been so > long since I needed it that I can't remember its name. I'd > appreciate it if somebody could point me in the right direction. You might try sudo fpaste --sysinfo to see what it does. -- Garry T. Williams ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there an officially Fedora supported replacement for the old rc.local? - still an issue
> Am 18.07.2022 um 22:18 schrieb Peter Boy : > > I got it finally working. After some tests: It isn’t. The programs I have to start depend on the existence of some (virtual) network interfaces. rc.local is ordered after network.target, which doesn’t mean, the network is functional then. Therefore, the program start via rc.local is in indeterministic process. Sometimes it works, sometimes not, sometimes only for some. Documentation mentions a drop in at /etc/systemd/system/rc-local.service.d/network.conf. But there is no subdirectory /etc/systemd/system/rc-local.service.d/ Should I really mess around with vim and mkdir in the directories managed by the distribution? Seems like a bad idea to me. Or have I missed something? > >> Am 18.07.2022 um 18:08 schrieb Tom Horsley : >> >> Is it really gone, or are they simply not creating the rc.local >> file any longer? > > The file is really gone. You have to create it at the right location. > > The documentation is inconsistent. Some say /etc/rc.local, some > /etc/rc.d/rc.local. The latter is correct. > > > What I did: > > (1) > Create /etc/rc.d/rc.local (with bash shebang), put in the execute commands > needed, made it executable for user und group root (but just user root should > be ok). > > (2) > Executed > /usr/lib/systemd/system-generators/systemd-rc-local-generator > > Is not on the path, you have to enter the complete path yourself - great. > This step is indispensable! > > (3) > Reboot, voila the included programs got started. > > I think, this is a better way than to hide the execute commands in user > root’s crontab. > > > Thanks for all the support! > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there an officially Fedora supported replacement for the old rc.local?
I got it finally working. > Am 18.07.2022 um 18:08 schrieb Tom Horsley : > > Is it really gone, or are they simply not creating the rc.local > file any longer? The file is really gone. You have to create it at the right location. The documentation is inconsistent. Some say /etc/rc.local, some /etc/rc.d/rc.local. The latter is correct. What I did: (1) Create /etc/rc.d/rc.local (with bash shebang), put in the execute commands needed, made it executable for user und group root (but just user root should be ok). (2) Executed /usr/lib/systemd/system-generators/systemd-rc-local-generator Is not on the path, you have to enter the complete path yourself - great. This step is indispensable! (3) Reboot, voila the included programs got started. I think, this is a better way than to hide the execute commands in user root’s crontab. Thanks for all the support! ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there an officially Fedora supported replacement for the old rc.local?
On Mon, Jul 18, 2022 at 10:52:42AM -0700, Mike Wright wrote: On 7/18/22 10:47, Tom Horsley wrote: On Mon, 18 Jul 2022 10:38:03 -0700 Mike Wright wrote: /etc/rc.local I think it is some more obscure location like /etc/rc.d/rc.local. [Unit] Description=/etc/rc.local Compatibility Documentation=man:systemd-rc-local-generator(8) ConditionFileIsExecutable=/etc/rc.local After=network.target [Service] Type=forking ExecStart=/etc/rc.local start <--- TimeoutSec=0 RemainAfterExit=yes GuessMainPID=no Other tidbits: /usr/share/man/man8/systemd-rc-local-generator.8.gz /usr/lib/systemd/system-generators/systemd-rc-local-generator -- Jon H. LaBadie jo...@jgcomp.com ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there an officially Fedora supported replacement for the old rc.local?
On 7/18/22 10:47, Tom Horsley wrote: On Mon, 18 Jul 2022 10:38:03 -0700 Mike Wright wrote: /etc/rc.local I think it is some more obscure location like /etc/rc.d/rc.local. [Unit] Description=/etc/rc.local Compatibility Documentation=man:systemd-rc-local-generator(8) ConditionFileIsExecutable=/etc/rc.local After=network.target [Service] Type=forking ExecStart=/etc/rc.local start <--- TimeoutSec=0 RemainAfterExit=yes GuessMainPID=no ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there an officially Fedora supported replacement for the old rc.local?
On Mon, 18 Jul 2022 10:38:03 -0700 Mike Wright wrote: > /etc/rc.local I think it is some more obscure location like /etc/rc.d/rc.local. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there an officially Fedora supported replacement for the old rc.local?
On 7/18/22 09:00, Peter Boy wrote: I have to run some scripts at the end of the boot process to establish various workarounds for bugs in systemd. In the days of System V, /etc/rc.d/rc.local would be the right place for this. My research revealed several solutions with conflicting recommendations: (a) There is - also in Fedora - systemd-rc-local service. In the man file it is advised not to use it. A Fedora default installation also does not completely create the necessary directory structure. And if one wants to execute this service as far as possible at the end of the boot process, further adjustments are necessary. (b) There is the DIY suggestion to create a service of one's own, and to place it as far as possible at the end of the system start. (c) A suggestion is to insert in the root-crontab at the end @reboot systemctl start …. The latter seems to be the most reliable solution at the moment. /etc/rc.local must be set executable If I remember correctly, systemd will execute rc-local.service which checks for /etc/rc.local then checks if it is executable. If so, it executes /etc/rc.local. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there an officially Fedora supported replacement for the old rc.local?
using the rc.local is going to be easier to support than creating your own systemd service to do exactly the same thing. I have been using the rc.local stuff for a while for anything that does not have a native systemd unit file. I think the comment of not using it is for other developers to not put into their instructions to add xxx to rc.local and telling them to create a proper systemd unit file. There have always been a lot of projects out there that just say add it to rc.local and do not create a proper startup script to be used. On Mon, Jul 18, 2022 at 11:01 AM Peter Boy wrote: > > I have to run some scripts at the end of the boot process to establish > various workarounds for bugs in systemd. In the days of System V, > /etc/rc.d/rc.local would be the right place for this. > > My research revealed several solutions with conflicting recommendations: > (a) > There is - also in Fedora - systemd-rc-local service. In the man file it is > advised not to use it. A Fedora default installation also does not completely > create the necessary directory structure. And if one wants to execute this > service as far as possible at the end of the boot process, further > adjustments are necessary. > > (b) > There is the DIY suggestion to create a service of one's own, and to place it > as far as possible at the end of the system start. > > (c) > A suggestion is to insert in the root-crontab at the end > @reboot systemctl start …. > > The latter seems to be the most reliable solution at the moment. > > Any recommendations and/or experiences? > > > > > > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there an officially Fedora supported replacement for the old rc.local?
On Mon, 18 Jul 2022 18:00:30 +0200 Peter Boy wrote: > Any recommendations and/or experiences? Is it really gone, or are they simply not creating the rc.local file any longer? I'm pretty sure I remember it working the last time I used it, just had to make the file myself and make it executable. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: diagnosing XFS corruption after upgrading to Fedora 36
You might include a full dmesg/messages. This is the sort of error you get when there is an underlying read failure/breakage on the device that the data is actually on. You get scsi errors/block errors first and then that shows up as filesystem errors similar to these. This sounds like the underlying device has issues (bad, bad cable, bad power...). On Sun, Jul 17, 2022 at 10:10 PM Patrick Hemmer wrote: > > Ever since upgrading to Fedora 36, my root filesystem is getting corrupted > every few hours. I maintain block level backups, and I have to restore every > time this happens. xfs_repair can fix the filesystem, but the system is > typically unusable as there's often over 10k files in lost+found. > > I have tried creating a brand new filesystem (mkfs.xfs), but it still gets > corrupted. > > I would file a bug, but the caveat is that I also have LVM underneath the > filesystem. And so I don't know whether it's a problem with XFS, or LVM. I > have other XFS filesystems also on LVM, and have seen corruption on them as > well, but it's nowhere near as significant or frequent as on the root > filesystem. > > Sometimes I can detect the corruption before the kernel does, by doing a > snapshot, and running `xfs_repair -n` on the snapshot. And sometimes the > kernel will detect the corruption first, usually with a message like: > > Jul 17 15:06:52 whistler kernel: XFS (dm-0): Metadata corruption detected at > xfs_buf_ioend+0x14c/0x5d0 [xfs], xfs_inode block 0x46057c8 > xfs_inode_buf_verify > Jul 17 15:06:52 whistler kernel: XFS (dm-0): Unmount and run xfs_repair > Jul 17 15:06:52 whistler kernel: XFS (dm-0): First 128 bytes of corrupted > metadata buffer: > Jul 17 15:06:52 whistler kernel: : 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: 0010: 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: 0020: 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: 0030: 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: 0040: 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: 0050: 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: 0060: 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: 0070: 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: XFS (dm-0): metadata I/O error in > "xfs_imap_to_bp+0x40/0x50 [xfs]" at daddr 0x46057c8 len 32 error 117 > Jul 17 15:06:52 whistler kernel: XFS (dm-0): Metadata I/O Error (0x1) > detected at xfs_trans_read_buf_map+0x179/0x2d0 [xfs] > (fs/xfs/xfs_trans_buf.c:296). Shutting down filesystem. > Jul 17 15:06:52 whistler kernel: XFS (dm-0): Please unmount the filesystem > and rectify the problem(s) > > So how can I proceed on this? Is there any way to determine whether this is > an LVM issue or an XFS issue? > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Is there an officially Fedora supported replacement for the old rc.local?
I have to run some scripts at the end of the boot process to establish various workarounds for bugs in systemd. In the days of System V, /etc/rc.d/rc.local would be the right place for this. My research revealed several solutions with conflicting recommendations: (a) There is - also in Fedora - systemd-rc-local service. In the man file it is advised not to use it. A Fedora default installation also does not completely create the necessary directory structure. And if one wants to execute this service as far as possible at the end of the boot process, further adjustments are necessary. (b) There is the DIY suggestion to create a service of one's own, and to place it as far as possible at the end of the system start. (c) A suggestion is to insert in the root-crontab at the end @reboot systemctl start …. The latter seems to be the most reliable solution at the moment. Any recommendations and/or experiences? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Long timeouts on logging out/shutting down
On Mon, 18 Jul 2022 14:34:13 +0100 Patrick O'Callaghan wrote: > I just created a new file in the system.conf.d directory. Didn't have > to touch the SElinux context. I guess that makes sense, since the file doesn't exist on the system, so there isn't any selinux rule for it. I was just being thorough, have been bitten by copying a file and losing the context before. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Long timeouts on logging out/shutting down
On Mon, 2022-07-18 at 06:08 -0700, stan via users wrote: > On Sun, 17 Jul 2022 19:14:09 +0200 > francis.montag...@inria.fr wrote: > > > Did you specified the [Manager] tag in the drop-in file ? > > > > Example: > > > > ## Weird: systemd seems to uses internally a ...USec name for that > > systemctl show --property=DefaultTimeoutStopUSec > > DefaultTimeoutStopUSec=1min 30s > > > > mkdir /usr/lib/systemd/system.conf.d > > echo -e '[Manager]\nDefaultTimeoutStopSec=5s' > > > /usr/lib/systemd/system.conf.d/99-stop-fast.conf > > > > systemctl daemon-reload > > > > systemctl show --property=DefaultTimeoutStopUSec > > DefaultTimeoutStopUSec=5s > > > I can confirm that this also works. I copied > /etc/systemd/system.conf > to the newly created directory, /usr/lib/systemd/system.conf.d with a > new name starting with 99, fixed the permissions and selinux context, > uncommented the appropriate entry, changed its value, and it is > working > as if I changed it in /etc/systemd/system.conf and > /etc/systemd/user.conf. I just created a new file in the system.conf.d directory. Didn't have to touch the SElinux context. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Long timeouts on logging out/shutting down
On Sun, 17 Jul 2022 19:14:09 +0200 francis.montag...@inria.fr wrote: > Did you specified the [Manager] tag in the drop-in file ? > > Example: > > ## Weird: systemd seems to uses internally a ...USec name for that > systemctl show --property=DefaultTimeoutStopUSec > DefaultTimeoutStopUSec=1min 30s > > mkdir /usr/lib/systemd/system.conf.d > echo -e '[Manager]\nDefaultTimeoutStopSec=5s' > > /usr/lib/systemd/system.conf.d/99-stop-fast.conf > > systemctl daemon-reload > > systemctl show --property=DefaultTimeoutStopUSec > DefaultTimeoutStopUSec=5s > I can confirm that this also works. I copied /etc/systemd/system.conf to the newly created directory, /usr/lib/systemd/system.conf.d with a new name starting with 99, fixed the permissions and selinux context, uncommented the appropriate entry, changed its value, and it is working as if I changed it in /etc/systemd/system.conf and /etc/systemd/user.conf. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: diagnosing XFS corruption after upgrading to Fedora 36
On Mon, 2022-07-18 at 07:29 -0300, George N. White III wrote: > Cables and connectors should also be considered. Try swapping cables > and connections. "Contact enhancer" sometimes solves connection > problems (now that cars are full of computers, you can buy > contact enhancer at auto supply stores). As someone who's been in electronics servicing for well over 30 years, I can attest that connectors are the cause of many mysterious faults where nothing else was wrong with the equipment. Unplugging and replugging fixed many faults, and using contact cleaner helps stop the problem from rapidly recurring. But use proper contact cleaner, not *ordinary* WD40 (it's corrosive, and will cause worse contact problems down the track, not to mention how horrible it is the the lungs). I used to encounter many connector problems with PCs years ago (when I frequently fixed other people's computers) because the case wasn't rigid enough. When people moved the box about, even by small amounts, the chassis would twist and it pulled cards partway out of their sockets. I had one that pretty much had to stay untouched on the shelf. Thermal expansion and contraction also walks connectors apart. One of my early computers had a very solid case, and it had a metal bar between the front and back of the case, and another that was screwed down over the top of plug-in cards to hold them firmly into place. Modern SATA drive data and power connectors are not very good, in my opinion, compared to the older style. They had a much tighter grip. Some of the better SATA cables have a metal catch to stop them slipping out. -- uname -rsvp Linux 3.10.0-1160.71.1.el7.x86_64 #1 SMP Tue Jun 28 15:37:28 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: custom '.local' folder - ?
On 15/07/2022 23:25, Cameron Simpson wrote: On 15Jul2022 16:12, lejeczek wrote: would anybody know if user's '.local' folder, its path & name are configurable in some way? Perhaps by a var or/and os-wide configs? Maybe not, but nothing stops you making it, or particular things inside it, symlinks to better locations. My local machine: [~]fleet2*> ls -ld .local drwxr-xr-x 3 cameron cameron 96 27 Jun 2020 .local [~]fleet2*> L .local/ total 0 drwxr-xr-x3 cameron cameron96 27 Jun 2020 . drwxr-sr-x+ 223 cameron cameron 7136 16 Jul 08:22 .. drwxr-xr-x5 cameron cameron 160 26 Jul 2021 share [~]fleet2*> L .local/share total 0 drwxr-xr-x 5 cameron cameron 160 26 Jul 2021 . drwxr-xr-x 3 cameron cameron 96 27 Jun 2020 .. drwxr-xr-x 3 cameron cameron 96 27 Jun 2020 direnv drwx-- 4 cameron cameron 128 26 Jul 2021 fish lrwxrwxr-x 1 cameron cameron 12 14 Aug 2020 vt -> ../../var/vt I keep a lot of things in ~/var, a lot of configs in ~/rc, yea, even to the point of: [~]fleet2*> ls -ld .config lrwxrwxr-x 1 cameron staff 2 11 May 2017 .config -> rc and machine specific configs in ~/rc-local. Won't do for me - fails with any bit more "complex" case when multiple nodes are involved and user landing on each such node would have unique/different '.local' dir, having whole home dir net mounted. I was hoping (& expecting) that would be controlled via a env var but it does not seem that way - which makes me wonder - that must the software which knows/chooses '.local' internally or might ignore that all rogether and use own path(s), if it is not the OS providing that information? hmm.. thanks, L. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: diagnosing XFS corruption after upgrading to Fedora 36
On Mon, Jul 18, 2022 at 12:10 AM Patrick Hemmer wrote: > Ever since upgrading to Fedora 36, my root filesystem is getting corrupted > every few hours. I maintain block level backups, and I have to restore > every time this happens. xfs_repair can fix the filesystem, but the system > is typically unusable as there's often over 10k files in lost+found. > > I have tried creating a brand new filesystem (mkfs.xfs), but it still gets > corrupted. > > I would file a bug, but the caveat is that I also have LVM underneath the > filesystem. And so I don't know whether it's a problem with XFS, or LVM. I > have other XFS filesystems also on LVM, and have seen corruption on them as > well, but it's nowhere near as significant or frequent as on the root > filesystem. > > Sometimes I can detect the corruption before the kernel does, by doing a > snapshot, and running `xfs_repair -n` on the snapshot. And sometimes the > kernel will detect the corruption first, usually with a message like: > > Jul 17 15:06:52 whistler kernel: XFS (dm-0): Metadata corruption detected > at xfs_buf_ioend+0x14c/0x5d0 [xfs], xfs_inode block 0x46057c8 > xfs_inode_buf_verify > Jul 17 15:06:52 whistler kernel: XFS (dm-0): Unmount and run xfs_repair > Jul 17 15:06:52 whistler kernel: XFS (dm-0): First 128 bytes of corrupted > metadata buffer: > Jul 17 15:06:52 whistler kernel: : 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: 0010: 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: 0020: 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: 0030: 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: 0040: 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: 0050: 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: 0060: 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: 0070: 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 > Jul 17 15:06:52 whistler kernel: XFS (dm-0): metadata I/O error in > "xfs_imap_to_bp+0x40/0x50 [xfs]" at daddr 0x46057c8 len 32 error 117 > Jul 17 15:06:52 whistler kernel: XFS (dm-0): Metadata I/O Error (0x1) > detected at xfs_trans_read_buf_map+0x179/0x2d0 [xfs] > (fs/xfs/xfs_trans_buf.c:296). Shutting down filesystem. > Jul 17 15:06:52 whistler kernel: XFS (dm-0): Please unmount the filesystem > and rectify the problem(s) > > So how can I proceed on this? Is there any way to determine whether this > is an LVM issue or an XFS issue? > LVM and XFS on linux have been very reliable, so you need to rule out hardware problems. If the drive supports S.M.A.R.T then smartmontools can run the internal tests. Some vendors provide test software (often Windows only). Cables and connectors should also be considered. Try swapping cables and connections. "Contact enhancer" sometimes solves connection problems (now that cars are full of computers, you can buy contact enhancer at auto supply stores). It is very useful to have an external drive to USB adapter. For nvme, a USB-C nvme case provides a way to test nvme drives, and a cast-off 128G nvme card can be used in the adapter as a fast alternative to USB memory "keys". > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- George N. White III ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
