touchpad
by Richard Vickery
I wonder if anyone knows how to bring up a touchpad?
Best,
Richard
10 years, 5 months
Change of UID
by Timothy Murphy
I recently had a hard disk failure.
I was able to recover my old /home directory
from a backup disk.
But on re-installing the system
(which had been in operation for several years)
I found my UID had changed from 500 to 1000.
I dealt with this by chown -R, which worked fine.
But I remember reading some years ago about this,
with other solutions suggested.
The reason I'm interested is that I am trying
to put together the old system from pieces that survived,
or were backed up,
and each time I start the old system I have to chown again.
Any suggestions of an alternative to chown gratefully received.
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin 2, Ireland
10 years, 5 months
F19 suddenly very unstable
by Frédéric Bron
Hi,
My F19 has suddenly become very unstable. After about 10 minutes of
running with KDE, the opened windows start to be closed automatically.
I even cannot stop the machine. I have access to the fedora menu but
its rendering is very odd and clicking on shutdown does not do
anything. I cannot go to a terminal either (with konsole which I
cannot start or with Ctrl+Alt+F2).
I have noticed that if I start the computer and just wait at the login
screen of kdm, the keyboard start to not work when I try to type my
login.
I do not know where to look at to find the cause of this.
My F19 is uptodate, with kernel 3.11.7. I have tried to boot with
3.11.6 but experience the same issue.
I have a nvidia video card but I do not use the nvidia driver, the
nouveau one provided by F19 instead.
Thanks for any help,
Frédéric
10 years, 5 months
/var/lib/libvirt/images on BTRFS (it works!)
by Chris Murphy
I've learned some things also, based on benchmarking by using the Fedora installer as the test suite:
1. 3x3 matrix of host/guest cfq, noop, deadline, that on spinning rust cfq in both host and guest produces the best results.
2. 3x3 matrix of host/guest ext4, xfs, btrfs, also on spinning rust, that Btrfs on Btrfs products the best results. The configuration is host Btrfs has a preallocated Raw file with xattr +C. Both host and guest Btrfs's are created with defaults from current btrfs-progs-0.20.rc1.20131114git9f0c53f-1.fc20, meaning both have a leafsize/nodesize of 16KB.
Because the results are all actually quite similar, at least it means Btrfs is no worse than other file systems. Interestingly, while +C (nodatacow) also means no data checksumming for the file, the contained Btrfs file system of course does have checksumming for everything, so there isn't a loss of file integrity with this method.
3. I can successfully use qcow2 files, xattr +C, where fragmentation is reduced a lot by preallocation metadata. A 20GB QCOW2 starts out with 5 extents, at the end of each installation of Fedora 20 live desktop final TC1, file frag reports these results:upon creation> fedoratest.img: 5 extents found
after installation1> fedoratest.img: 1255 extents found
after installation2> fedoratest.img: 1773 extents found
after installation3> fedoratest.img: 2148 extents found
after installation4> fedoratest.img: 2245 extents found
I have no data that conclusively indicates a slow down as a result of additional extents created. So I'm uncertain of the long term ramifications of using qcow2 on Btrfs but it does work. I also don't know where these extents are located on the physical device. The Raw file is the only file on this particular Btrfs volume. If it were the case multiple qcow2 file extents were "interleaved" or otherwise non-contiguous, it's possible multiple VM performance would overall be better on Btrfs than on other file systems.
In any case, more testing is needed to demonstrate the pros and cons. This is also a question using LVM thinp as a backing for a VM for the same reasons.
Chris Murphy
10 years, 5 months
F17 boot with lvm does not create all the device nodes
by Deron Meranda
I have an F17 server that will no longer boot. When entering emergency
mode, it looks like not all of the device file nodes are being created.
All of the physician volumes and volume groups are okay, but only some of
the logical volumes have their device files created. In particular the
volume containing my /var filesystem doesn't show up.
When I enter 'lvs', all the logical volumes are listed, and they are
active. These are all on one physical volume.
If I enter 'vgscan --mknodes' then the missing device files do get created.
I can subsequently get to all my data (first using cryptsetup to decrypt
the LUKS volume that is stored inside the logical volume, and then mount).
However I can not get the system to continue booting beyond the emergency
mode, and upon the next reboot, again, some of the lvm device files are
missing.
Any ideas?
Thanks
--
Deron Meranda
http://deron.meranda.us/
10 years, 5 months
/dev/md[12] vanished
by Kevin H. Hobbs
On October 4 this :
--------------------- Mdadm Begin ------------------------
mdadm: cannot open /dev/md1: No such file or directory
/dev/md1 :
mdadm: cannot open /dev/md2: No such file or directory
/dev/md2 :
---------------------- Mdadm End -------------------------
and this :
--------------------- Disk Space Begin ------------------------
Filesystem Size Used Avail Use% Mounted on
devtmpfs 2.0G 0 2.0G 0% /dev
/dev/md127 48G 16G 31G 34% /
/dev/md126 475M 118M 328M 27% /boot
/dev/sdc1 917G 73G 798G 9% /mnt/WD1TB
/dev/md0 173G 65G 101G 40% /home
---------------------- Disk Space End -------------------------
began appearing in the logwatch e-mails of at least two of my
computers that run Fedora 18.
Somehow md1 and md2 became md127 and md126.
On October 3 and 4 there were lots of updates including a kernel
and dracut.
Does anybody have a clue what might have changed?
Everything works from my perspective but I don't want my arrays
to disappear on me if I haven't made some configuration change
before some later update
10 years, 5 months
/var/lib/libvirt/images on BTRFS (it works!)
by Gene Czarcinski
Some of you may be interested in running your qemu-kvm (or other) disk
image files on BTRFS. After some fumbling around, I have found out how
to do it so it works and works very well (especially if it is on an SSD).
Anyone investigating running on BTRFS immediately finds out that there
is a fragmentation problem (just putting image files on btrfs can result
in them having between 50,000 and 100,000 extents). Some may have seen
that adding nodatacow to the mount option is a solution ... it is not.
So what is the solution?
1. execute: chattr +C /var/lib/libvirt/images
or wherever your image files are. This needs to be done on the
directory whether you have a separate subvol or not.
2. This ONLY works for new files and ONLY works for "raw" storage
format files. Pretty much by definition, qcow2 files are sparse format
files and that is the primary problem on btrfs.
So that the vm creation wizard will create a new disk using the raw
storage format, you need to select:
Edit->Preferences->VM Details->Default Storage Format->Raw
After that, a created virtual will have the correct disk format.
You can use "filefrag" to verify that things are working.
Gene
10 years, 5 months
f19 emacs almost unuseable
by Jackson Byers
f19a13 df13mail]#
(emacs:14906): Gtk-WARNING **: Theme parsing error: gtk.css:67:18: Not
using units is deprecated. Assuming 'px'.
(emacs:14906): Gtk-WARNING **: Theme parsing error: gtk.css:67:20: Not
using units is deprecated. Assuming 'px'.
(emacs:14906): Gdk-CRITICAL **: gdk_device_get_source: assertion
`GDK_IS_DEVICE (device)' failed
recent f19 install, usad f19.netinst.iso
most things look ok, network up, chromium browser working
entering text in emacs extremely clumsy,
cant see what i typed without clicking..........
etc.
any advice?
]# uname -r3.11.1-200.fc19.i686.PAE
Jack
10 years, 5 months
keyboard layout problem fedora19 gnome3 shell
by Natxo Asenjo
hi,
I installed fedora 19 desktop edition and am having some trouble with
the keyboard layout (in the standard gnome3 shell).
What I need is this layout:
$ setxkbmap -query
rules: evdev
model: pc104
layout: us
variant: intl
options: kpdl:kposs
but what I get is:
$ setxkbmap -query
rules: evdev
model: pc104
layout: us
options: kpdl:kposs
I have tried adding an autostart file in $HOMEDIR/.config/autostart like this:
$ cat set_us_intl_keyboard.desktop
[Desktop Entry]
Type=Application
Name=set us intl keyboard layout
Comment=set us intl keyboard layout
Exec=setxkbmap us -variant intl
but every time I need to run the command manually because the settings
are not applied.
using the graphical tool 'Regional Settings' I choose as 'Input
source' : English (US, alternative international), but still no go.
What is the way to fix this? Why is it not appying the settings with
the autostart command? This is quite annoying, I should not be having
to bang my head against the wall for a simple keyboard layout ;-)
TIA,
--
Regards,
Natxo
--
Groeten,
natxo
10 years, 5 months
VT consoles annoyance
by Natxo Asenjo
hi,
another 'minor' annoyance in my fedora 19 laptop is the fact that VT
consoles are, in fact, unusable.
I constantly get info messages of NetworkManager.
I have tried tweaking sysctl.conf like this:
kernel.printk = 2 2 2 2
because of info I found here
http://superuser.com/questions/351387/how-to-stop-kernel-messages-from-fl...
But it does not resolve it.
In /etc/rsyslog.conf I have no kern.* line enabled
Any ideas?
--
Groeten,
natxo
--
Groeten,
natxo
10 years, 5 months
