NFS Problems in Fedora 33
by Richard Kimberly Heck
Hi, all,
Since upgrading to Fedora 33, I am having some problems accessing files
on NFS shares. I should say first that, immediately after the upgrade,
the shares would not mount at all. I was getting the error:
mount.nfs4: Operation not permitted when mounting NFS device
even when attempting to mount manually. Eventually, I found some info
online that suggested mounting manually as root, which created some
symlink or other. After that, the shares would mount automatically at boot.
However, now, as I said, I have problems accessing files on said shares.
The directory ~/files/ is an NFS mount from a server running CentOS 7.
My LyX user directory is at ~/files/config/lyx/ (symlinked from
~/.lyx/). LyX refuses to start, blocking at a call to
lockf(fd, F_LOCK, 0) at support/filetools.cpp, during startup. (I
believe that fd here points at a file on the NFS share.) I can
successfully start LyX via:
lyx -userdir ~/tmp/lyx
say. I can then restart LyX with the same command and all is well. I can
also start it with
lyx -userdir ~/files/lyxnew/
where that is a *non-existent* directory on the NFS share. In that case,
LyX goes through its configuration process and starts normally. However,
if I then attempt to run that same command again, LyX does not start.
Also, if ~/files/lyxnew/ does exist, then LyX will not start, even if it
is empty.
I am seeing a similar problem with Libre Office. I can starti fine, but
if I then attempt to open a file from ~/files/, Libre Office freezes. It
does not matter when it is ODT or ODS, say. I have not seen the problem
in other programs, but I only upgraded yesterday.
I am guessing that there is something wrong with the NFS configuration.
But I did not change anything myself.
Riki
3 years, 4 months
System completely unstable after migrating to thin pools
by Sreyan Chakravarty
Hi,
I have migrated to thin pools using partclone.
But now that I am using thin pools my system is completely unstable.
My swap is not activated :
swapon[1004]: swapon: /fedora.swap: read swap header failed
systemd[1]: fedora.swap.swap: Swap process exited, code=exited,
status=255/EXCEPTION
systemd[1]: fedora.swap.swap: Failed with result 'exit-code'.
Failed to activate swap /fedora.swap.
Dependency failed for Swap.
swap.target: Job swap.target/start failed with result 'dependency'.
My System logging service is not started:
rsyslog.service: Failed with result 'core-dump'.
Failed to start System Logging Service.
SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295
subj=system_u:system_r:init_t:s0 msg='unit=rsyslog comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
rsyslog.service: Scheduled restart job, restart counter is at 1.
And device mapper gives me weird messages during startup like:
kernel: device-mapper: btree spine: node_check failed: csum 3318704195 !=
wanted 3318554075
kernel: device-mapper: block manager: btree_node validator check failed
for block 220
kernel: device-mapper: btree spine: node_check failed: csum 3318704195 !=
wanted 3318554075
kernel: device-mapper: block manager: btree_node validator check failed
for block 220
kernel: device-mapper: btree spine: node_check failed: csum 3318704195 !=
wanted 3318554075
kernel: device-mapper: block manager: btree_node validator check failed
for block 220
kernel: device-mapper: btree spine: node_check failed: csum 3318704195 !=
wanted 3318554075
kernel: device-mapper: block manager: btree_node validator check failed
for block 220
Also some dracut module is missing:
dracut-initqueue[867]: /usr/sbin/thin_check: execvp failed: No such file or
directory
dracut-initqueue[867]: WARNING: Check is skipped, please install
recommended missing binary /usr/sbin/thin_check!
In short my system has gone to hell.
This all started when I did a fstrim like this:
sudo fstrim -v /
And it returned an input/output error.
My logical volumes were marked with two 'XX', I don't know what that means.
After that I restarted.
What can I do to get my system back to normal ?
Please help.
--
Regards,
Sreyan Chakravarty
3 years, 4 months
Spotify - Negativo17 vs FlatPak
by Jorge Fábregas
Hi everyone,
I've been using Spotify for the last year (via Flatpak) and it's been
working perfectly fine (not a single crash). I'm not fond on using
snaps, flatpaks or appimages unless really necessary but at the time I
installed it the general consensus was that Flatpak (at least for
Spotify) was the best option in Fedora.
I'm migrating from F31 to F33 soon and was wondering how's the
Negativo17 package these days? Or should I stick to the Flatpak?
I know there may be some dependency collisions between RPM Fusion and
Negativo17 but I think Spotify would be the only package I'll be using
from Negativo17 (with repo disabled afterwards except for updates).
Thanks.
--
Jorge
3 years, 4 months
Tablet
by GianPiero Puccioni
Hi,
a friend just got a tablet and and has some problems with it.
Is has F32 installed, the tablet is a Ugee M708 which is seen by lsusb as a
XP-Pen 10 (?).
It works as a mouse and can be used to draw in graphics programs but it doesn't
have all the extra stuff and cannot be configured or calibrated, at least not
with the usual Watcom program.
According to info on the net it should use the Digimend driver but that doesn't
seem to be available in the Fedore repository.
Any suggestion?
GiP
3 years, 4 months
F32 --> F33 upgrade fails .
by Kostas Sfakiotakis
Greetings ,
Upon trying to download the files in order to be able to upgrade from
F32 to F33 i get the following errors
Error:
Problem 1: package openssh-ldap-8.3p1-3.fc32.x86_64 requires openssh =
8.3p1-3.fc32, but none of the providers can be installed
- openssh-8.3p1-3.fc32.x86_64 does not belong to a distupgrade repository
- problem with installed package openssh-ldap-8.3p1-3.fc32.x86_64
Problem 2: package tomahawk-0.8.4-23.fc31.x86_64 requires
libboost_filesystem.so.1.69.0()(64bit), but none of the providers can be
installed
- boost-filesystem-1.69.0-18.fc32.x86_64 does not belong to a
distupgrade repository
- problem with installed package tomahawk-0.8.4-23.fc31.x86_64
(try to add '--skip-broken' to skip uninstallable packages)
The thing is that even if i try to use the --skip-broken option the
download of the files will not begin either . Now apart from deleting
the offending
packages , trying the upgrade and then reinstalling them is there
anything else that i can try ???
3 years, 4 months
Why is only 11 GB used of my 12 GB swap file ?
by Sreyan Chakravarty
Hi,
I have created my swap file using the command:
dd if=/dev/zero of=/fedora.swap bs=1M count=12288 status=progress
So this should produce a 12 GB file right ?
I can confirm it does:
$ ls -lh /fedora.swap
-rw-------. 1 root root 12G Nov 27 20:23 /fedora.swap
So why is the swap memory in my system reported as 11 GB by the free
command ?
$ free -h
total used free shared
buff/cache available
Mem: 7.7Gi 1.4Gi 4.5Gi 394Mi 1.8Gi
5.6Gi
Swap: 11Gi 0B 11Gi
Why is it 11 GB ? Shouldn't it be 12 GB ?
Am I missing something?
What is the reason for this?
--
Regards,
Sreyan Chakravarty
3 years, 4 months
Sync rpms with other computer
by Mayavimmer
How do I sync rpm packages with another computer?
I have a list of the remote's rpms generated with "rpm -qa".
I expect to have to modify a couple of packages in the list due to
hardware dependent rpms like xorg.
Otherwise it should be a simple matter of downloading the rpms from the
edited list and then installing them.
Or is there already a script for this?
3 years, 4 months
Is TRIM or DISCARD needed for regular HDDs
by Sreyan Chakravarty
Hi,
I am confused about whether I should use TRIM or DISCARD on my laptop.
I use LVM on top of LUKS and I do make frequent use of snapshots. Merging
them to my root volume.
I have a regular HDD and not a SSD.
Will enabling TRIM and DISCARD help me?
If so, how do I do that ? I have already tried enabling:
issue_discards=1
in /etc/lvm/lvm.conf and then dracut -f
But fstrim -v / still fails with :
fstrim: /: the discard operation is not supported
So how do I enable it in Fedora32 ?
--
Regards,
Sreyan Chakravarty
3 years, 4 months
Read-only flash drives
by Joe Zeff
Every now and then I buy a flash drive and find that when I mount it
it's owned by root and read only except by root. I can, of course,
change that by using chown and chmod, but that only lasts until I
unmount the drive. Generally, I need to reformat the drive to get it
working properly. And, it's not just Fedora; my sister uses Xubuntu,
and has the same issue. Does anybody know a way to keep this from
happening, or to fix it without reformatting?
3 years, 4 months
virt-install fails with F33 with "Failed to start Switch Root"
by Michal Schorm
Hello,
I am deploying VMs via kickstart files, so the process can be
completely non-interactive.
Right now I'm stuck with Fedora 33.
The following command works completely fine on F32, F31 and so on, but not F33.
Can you please help me fix it?
virt-install \
--connect qemu:///system \
--network bridge:virbr0 \
--initrd-inject /var/local/minimal.ks \
--name test_name_3 \
--disk /VMs/test_name_3.qcow2,size=10,format=qcow2 \
--memory 2048 \
--location https://download.fedoraproject.org/pub/fedora/linux/releases/32/Server/x8...
\
--hvm --vcpus=2 --check-cpu --accelerate \
--graphics none \
--extra-args 'ks=file:/minimal.ks console=tty0 console=ttyS0,115200'
Just change the URL to point to F33 repo. It will fail, after the
whole installation is complete and the VM should start one last time,
with following error:
Failed to start Switch Root.
Failed to switch root: Specified switch root path '/sysroot' does
not seem to be an OS tree. os-release file is missing.
I checked that the file "/etc/os-release" is in place and populated.
I uploaded the used Kickstarter file, as well as some logs here:
https://gitlab.com/Faramos/vm/-/snippets/2042979
I also tried to force installation with EXT4 partitions (instead of
F33 default BTRFS), but it hasn't made any difference.
Nothing else in
https://fedoraproject.org/wiki/Category:ChangeAcceptedF33 seems
suspicous to me.
I am using an F32 host.
--
Michal Schorm
Software Engineer
Core Services - Databases Team
Red Hat
--
3 years, 4 months
