Re: Is TRIM or DISCARD needed for regular HDDs

On 11/25/20 11:37 PM, Sreyan Chakravarty wrote: On Thu, Nov 26, 2020 at 1:04 AM Samuel Sieb > wrote: Your original post was using the thick LV which doesn't support it. You need to try it again now that you have a thin LV that does Using fstrim now gives th

Re: Is TRIM or DISCARD needed for regular HDDs

On Thu, Nov 26, 2020 at 1:04 AM Samuel Sieb wrote: > > Your original post was using the thick LV which doesn't support it. You > need to try it again now that you have a thin LV that does > Using fstrim now gives the output: $ fstrim -v / /: 584.8 GiB (627935141888 bytes) trimmed Do I have to

Re: Read-only flash drives

You’re still lucky. Once in a while we come across thumb-drives, that after using a couple of times, can’t even be reformatted. From: "Joe Zeff" mailto:j...@zeff.us>> Date: Thursday, 26 November 2020 at 00:02:35 To: "Community support for Fedora users" mailto:users@lists.fedoraproject.org>> Sub

Re: Read-only flash drives

On 26/11/2020 14:00, Joe Zeff wrote: On 11/25/20 6:06 PM, Jonathan Billings wrote: Or just copy/paste the output of ‘mount’. *Sigh!*  The drive we're having trouble with works Just Fine on my Fedora box, but not on my sister's Ubuntu box.  Not a Fedora issue. FWIW, I have a Ubuntu VM and th

Re: Sync rpms with other computer

On 25 Nov 2020 at 11:58, Mayavimmer wrote: To: fedora From: Mayavimmer Subject:Sync rpms with other computer Date sent: Wed, 25 Nov 2020 11:58:08 +0100 Send reply to: Community support for Fedora users > How do I sync

Strange pause after running gedit from regular text terminal window.

The pause varies in time, and sometimes shows message and sometimes doesn't?? Example $:gedit gccdirectory.1126 (org.gnome.gedit:4156283): Gtk-WARNING **: 07:13:25.756: Calling org.xfce.Session.Manager.Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “Inhib

Hibernate resume failed on kernel 5.9

Hi, I have upgraded to the latest 5.9 kernel on Fedora 32. But after upgrading I am getting the following error when I am resuming from hibernation: : PM: Loading and decompressing image data (771034 pages)... : PM: Image loading progress: 0% : PM: Image loading progress: 10% : PM: Image load

Re: Read-only flash drives

On 11/25/20 6:06 PM, Jonathan Billings wrote: Or just copy/paste the output of ‘mount’. *Sigh!* The drive we're having trouble with works Just Fine on my Fedora box, but not on my sister's Ubuntu box. Not a Fedora issue. ___ users mailing list --

Re: Read-only flash drives

On 26/11/2020 12:02, Samuel Sieb wrote: On 11/25/20 7:32 PM, Joe Zeff wrote: On 11/25/20 4:05 PM, Samuel Sieb wrote: What filesystem is on it and how are you mounting it? I'd presume VFAT, and I'm just inserting the drive and letting the OS do its thing, and my sister's doing the same way o

Re: Read-only flash drives

On 11/25/20 7:32 PM, Joe Zeff wrote: On 11/25/20 4:05 PM, Samuel Sieb wrote: What filesystem is on it and how are you mounting it? I'd presume VFAT, and I'm just inserting the drive and letting the OS do its thing, and my sister's doing the same way on Ubuntu. I've never had a problem with

Re: Read-only flash drives

On 11/25/20 4:05 PM, Samuel Sieb wrote: What filesystem is on it and how are you mounting it? I'd presume VFAT, and I'm just inserting the drive and letting the OS do its thing, and my sister's doing the same way on Ubuntu. ___ users mailing list -

Re: Sync rpms with other computer

On 11/25/20 2:58 AM, Mayavimmer wrote: 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 dow

Re: Read-only flash drives

On Nov 25, 2020, at 19:04, ToddAndMargo via users wrote: > > --> gparted: select the flash drive from the pull down in >the upper right > > --> View > > --> device information > > Post a screen shot over on [redacted] Or just copy/paste the output of ‘mount’. -- Jonathan Billings

Re: [SOLVED?] Re: NFS Problems in Fedora 33

On Nov 25, 2020, at 17:41, Richard Kimberly Heck wrote: > > But /home/rikiheck/files was an ordinary directory that I want to export, not > the root for NFSv4. It was being mounted as NFSv3 (trying to mount with nfs4 > would fail). But I'm guessing that it was being treated inconsistently > be

Re: Read-only flash drives

On 2020-11-25 15:05, Samuel Sieb wrote: On 11/25/20 3:01 PM, Joe Zeff wrote: 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 dr

Re: Read-only flash drives

On 11/25/20 3:01 PM, Joe Zeff wrote: 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 d

Read-only flash drives

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

Re: [SOLVED?] Re: NFS Problems in Fedora 33

On 26/11/2020 06:40, Richard Kimberly Heck wrote: This problem seems to have been solved. I believe that the issue was a misconfiguration of the NFS server. I had: /home/rikiheck/files 192.168.1.0/24(rw,sync,no_subtree_check,fsid=0) /home/nancy/files 192.168.1.0/24(rw,sync,no_subtree_check) /h

[SOLVED?] Re: NFS Problems in Fedora 33

This problem seems to have been solved. I believe that the issue was a misconfiguration of the NFS server. I had: /home/rikiheck/files 192.168.1.0/24(rw,sync,no_subtree_check,fsid=0) /home/nancy/files 192.168.1.0/24(rw,sync,no_subtree_check) /home/photos 192.168.1.0/24(rw,sync,no_subtree_check

Re: NFS Problems in Fedora 33

On 11/25/20 4:28 PM, Richard Kimberly Heck wrote: On 11/25/20 12:56 PM, Ed Greshko wrote: On 25/11/2020 22:51, Richard Kimberly Heck wrote: I can mount fine. The problem is that various programs (LyX, LibreOffice) freeze when attempting to open files on those filesystems. In LyX, I was able

Re: NFS Problems in Fedora 33

On 11/25/20 4:28 PM, Richard Kimberly Heck wrote: On 11/25/20 12:56 PM, Ed Greshko wrote: On 25/11/2020 22:51, Richard Kimberly Heck wrote: I can mount fine. The problem is that various programs (LyX, LibreOffice) freeze when attempting to open files on those filesystems. In LyX, I was able

Re: NFS Problems in Fedora 33

On 11/25/20 12:56 PM, Ed Greshko wrote: On 25/11/2020 22:51, Richard Kimberly Heck wrote: I can mount fine. The problem is that various programs (LyX, LibreOffice) freeze when attempting to open files on those filesystems. In LyX, I was able to trace the problem to a call to lockd, which nev

Re: NFS Problems in Fedora 33

On 26/11/2020 03:36, Robert wrote: My fstab entry is as follows. 192.168.2.100:/STUF/STUFF /home/me/STUFF nfs rw 0 0 OK.  Using just nfs on the fstab entry would mean that it should use the default protocol on the server.  I am using a Centos7 server that hasn't been modified.  So, nfs-v4 is

Re: Is TRIM or DISCARD needed for regular HDDs

On 11/25/20 10:34 AM, Sreyan Chakravarty wrote: Well if you read my original post you will see that I included:  fstrim -v / still fails with :                  fstrim: /: the discard operation is not supported Your original post was using the thick LV which doesn't support it. You need t

Re: Is TRIM or DISCARD needed for regular HDDs

On Wed, Nov 25, 2020 at 11:27 PM Chris Murphy wrote: > You don't have to enable anything. The fstrim.timer his enabled by default > and runs fstrim.service once per week. > > That command will issue fstrim on all mounted file systems listed in > fstab. It has no effect on HDD, or conventional "th

Re: Is TRIM or DISCARD needed for regular HDDs

On Wed, Nov 25, 2020 at 11:31 PM Ed Greshko wrote: > > > Well, reading the link I sent suggests that the file system supports it. > > Do you get the same error when you use the fstrim command from the command > line? The > format being... > > fstrim [-Aa] [-o offset] [-l length] [-m minimum-size

Re: Is TRIM or DISCARD needed for regular HDDs

On 26/11/2020 00:35, Sreyan Chakravarty wrote: On Wed, Nov 25, 2020 at 2:48 PM Ed Greshko mailto:ed.gres...@greshko.com>> wrote: The difference here is the "thin-provisioned" lvm.  In this case the Trim/Discard isn't being used to extend or improve the performance of the underlying h

Re: NFS Problems in Fedora 33

On 25/11/2020 22:51, Richard Kimberly Heck wrote: I can mount fine. The problem is that various programs (LyX, LibreOffice) freeze when attempting to open files on those filesystems. In LyX, I was able to trace the problem to a call to lockd, which never returns. So it seems there is some proble

Re: Is TRIM or DISCARD needed for regular HDDs

You don't have to enable anything. The fstrim.timer his enabled by default and runs fstrim.service once per week. That command will issue fstrim on all mounted file systems listed in fstab. It has no effect on HDD, or conventional "thick" lvm. But it does have an effect on thin volumes, it will re

Re: Is TRIM or DISCARD needed for regular HDDs

On Wed, Nov 25, 2020 at 2:48 PM Ed Greshko wrote: > > The difference here is the "thin-provisioned" lvm. In this case the > Trim/Discard isn't being used > to extend or improve the performance of the underlying hardware. It is > being used to free/return > unused blocks to the "pool". > The qu

Re: NFS Problems in Fedora 33

On 11/25/20 5:23 AM, Ed Greshko wrote: On 25/11/2020 09:40, Ed Greshko wrote: Can you confirm that the NFS server is on a Centos7 system? Is NFS-v3 required, or can you switch to NFS-v4? FWIW, I installed a Centos7 VM.  And enabled nfs-server.service. The server has the following: [root@co

Sync rpms with other computer

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 an

xournal++ dev

Hello, I am not sure that it is the right list to post it, but there is a development version of xournalpp 1.1 which is not available in fedora Is there a chance to have it soon? Actually, I have not been able to get the sources. =

Re: NFS Problems in Fedora 33

On 25/11/2020 09:40, Ed Greshko wrote: Can you confirm that the NFS server is on a Centos7 system? Is NFS-v3 required, or can you switch to NFS-v4? FWIW, I installed a Centos7 VM.  And enabled nfs-server.service. The server has the following: [root@cos7 etc]# firewall-cmd --get-active-zones

virt-install fails with F33 with "Failed to start Switch Root"

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 \ --ne

Re: Keyboard switches to US keyboard after each reboot

On 11/25/20 9:58 AM, Joachim Backes wrote: Hi, I'm running F33 with Cinnamon/German nodeadkeys keyboard layout. Having the problem that after each reboot the keyboad layout switches to US layout. Workaround (not permanent; valid until next reboot): "loadkeys de" in some console windowd (Ct

Re: Bricked system after migrating to thin LVMs

On 25/11/2020 16:42, Sreyan Chakravarty wrote: On Tue, Nov 24, 2020 at 6:12 PM Ed Greshko mailto:ed.gres...@greshko.com>> wrote: Well, the module is located here in my f32 systems. [egreshko@f32k ~]$ locate dm-thin-pool /usr/lib/modules/5.8.13-200.fc32.x86_64/kernel/drivers/md/dm-

Re: Is TRIM or DISCARD needed for regular HDDs

On 25/11/2020 16:44, Sreyan Chakravarty wrote: On Mon, Nov 23, 2020 at 3:07 PM Ed Greshko mailto:ed.gres...@greshko.com>> wrote: Ahhh, never mind.  It may be useful/supported with thin LV. I am completely confused. Are you sure TRIM and DISCARD are needed for normal HDDs ? because wha

Keyboard switches to US keyboard after each reboot

Hi, I'm running F33 with Cinnamon/German nodeadkeys keyboard layout. Having the problem that after each reboot the keyboad layout switches to US layout. Workaround (not permanent; valid until next reboot): "loadkeys de" in some console windowd (Ctrl Fx ...) Anybody sees a solution for this

Re: Is TRIM or DISCARD needed for regular HDDs

On Mon, Nov 23, 2020 at 3:07 PM Ed Greshko wrote: > > Ahhh, never mind. It may be useful/supported with thin LV. > I am completely confused. Are you sure TRIM and DISCARD are needed for normal HDDs ? because whatever I find on the internet says that I should use that when I have a SSD. -- R

Re: Bricked system after migrating to thin LVMs

On Tue, Nov 24, 2020 at 6:12 PM Ed Greshko wrote: > Well, the module is located here in my f32 systems. > > [egreshko@f32k ~]$ locate dm-thin-pool > > /usr/lib/modules/5.8.13-200.fc32.x86_64/kernel/drivers/md/dm-thin-pool.ko.xz > > /usr/lib/modules/5.8.14-200.fc32.x86_64/kernel/drivers/md/dm-thin

Re: Bricked system after migrating to thin LVMs

On Tue, Nov 24, 2020 at 9:23 PM Roger Heflin wrote: > If you have a "rescue" option in grub then boot it, the rescue install > should be built with hostonly=no and is expected to include all > drivers including that one. I verified on one of my machines that one > is included in my rescue. The