[Bug 246264] K3b freezing on verify disk (sometimes) DVD+RW
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=246264
--- Comment #7 from Brad <lazlow(a)charter.net> 2008-10-28 14:18:14 EDT ---
Just k3b just once in a while.
[fred@localhost ~]$ ps ax
PID TTY STAT TIME COMMAND
1 ? Ss 0:01 init [5]
2 ? S< 0:00 [kthreadd]
3 ? S< 0:00 [migration/0]
4 ? S< 0:00 [ksoftirqd/0]
5 ? S< 0:00 [watchdog/0]
6 ? S< 0:00 [migration/1]
7 ? S< 0:00 [ksoftirqd/1]
8 ? S< 0:00 [watchdog/1]
9 ? S< 0:00 [events/0]
10 ? S< 0:00 [events/1]
11 ? S< 0:00 [khelper]
60 ? S< 0:00 [kblockd/0]
61 ? S< 0:00 [kblockd/1]
64 ? S< 0:00 [kacpid]
65 ? S< 0:00 [kacpi_notify]
203 ? S< 0:00 [cqueue/0]
204 ? S< 0:00 [cqueue/1]
206 ? S< 0:00 [ksuspend_usbd]
211 ? S< 0:00 [khubd]
214 ? S< 0:00 [kseriod]
265 ? S 0:00 [pdflush]
266 ? S 0:00 [pdflush]
267 ? S< 0:00 [kswapd0]
319 ? S< 0:00 [aio/0]
320 ? S< 0:00 [aio/1]
463 ? S< 0:00 [kpsmoused]
501 ? S< 0:00 [ata/0]
502 ? S< 0:00 [ata/1]
503 ? S< 0:00 [ata_aux]
510 ? S< 0:00 [scsi_eh_0]
511 ? S< 0:00 [scsi_eh_1]
515 ? S< 0:00 [scsi_eh_2]
516 ? S< 0:00 [scsi_eh_3]
517 ? S< 0:00 [scsi_eh_4]
518 ? S< 0:00 [scsi_eh_5]
527 ? S< 0:00 [kjournald]
559 ? S< 0:00 [kauditd]
591 ? S<s 0:00 /sbin/udevd -d
1180 ? S< 0:00 [kgameportd]
1399 ? S< 0:00 [kmpathd/0]
1400 ? S< 0:00 [kmpathd/1]
1428 ? S< 0:00 [kjournald]
1429 ? S< 0:00 [kjournald]
1430 ? S< 0:00 [kjournald]
1541 ? S< 0:00 [kondemand/0]
1542 ? S< 0:00 [kondemand/1]
1817 ? Ss 0:00 /usr/sbin/restorecond
1827 ? Ss 0:04 irqbalance
1837 ? SLl 0:01 /sbin/multipathd
1853 ? Ss 0:00 rpcbind
1876 ? S< 0:00 [rpciod/0]
1877 ? S< 0:00 [rpciod/1]
1906 ? Ss 0:00 rpc.idmapd
1969 ? Ssl 0:01 pcscd
2123 ? Sl 0:00 rsyslogd -m 0
2127 ? Ss 0:00 rklogd -x
2141 ? S<sl 0:00 auditd
2143 ? S<sl 0:00 /sbin/audispd
2157 ? Ssl 0:00 dbus-daemon --system
2169 ? Ssl 0:04 /usr/bin/python -E /usr/sbin/setroubleshootd
2183 ? Ssl 0:02 automount
2201 ? Ss 0:00 /usr/sbin/acpid
2224 ? Ss 0:00 rpc.rquotad -p 4003
2246 ? S< 0:00 [nfsd4]
2247 ? S 0:00 [lockd]
2248 ? S 0:00 [nfsd]
2249 ? S 0:00 [nfsd]
2250 ? S 0:00 [nfsd]
2251 ? S 0:00 [nfsd]
2252 ? S 0:00 [nfsd]
2253 ? S 0:00 [nfsd]
2254 ? S 0:00 [nfsd]
2255 ? S 0:00 [nfsd]
2258 ? Ss 0:00 rpc.mountd -p 4002
2282 ? S 0:00 /usr/sbin/hddtemp -d -l 127.0.0.1 -d /dev/sda
/dev/sd
2292 ? S 0:00 nasd -b -local
2301 ? Ssl 0:00 console-kit-daemon
2371 ? Ss 0:00 crond
2379 ? Ss 0:00 /usr/sbin/atd
2389 ? Ss 0:00 avahi-daemon: running [linux.local]
2390 ? Ss 0:00 avahi-daemon: chroot helper
2399 ? Ss 0:00 cupsd
2410 ? Ss 0:00 hald
2411 ? S 0:00 hald-runner
2428 ? S 0:00 hald-addon-input: Listening on /dev/input/event5
/dev
2435 ? S 0:00 /usr/libexec/hald-addon-cpufreq
2437 ? S 0:00 hald-addon-acpi: listening on acpid socket
/var/run/a
2478 ? S 0:05 hald-addon-storage: polling /dev/sr0 (every 2 sec)
2568 ? Ss 0:00 NetworkManager
--pid-file=/var/run/NetworkManager/Net
2576 ? S 0:00 /usr/sbin/wpa_supplicant -c
/etc/wpa_supplicant/wpa_s
2578 ? S 0:00 /usr/sbin/nm-system-settings --config
/etc/NetworkMan
2591 ? S 0:00 /usr/sbin/smartd -q never
2599 tty1 Ss+ 0:00 /sbin/mingetty tty1
2600 tty2 Ss+ 0:00 /sbin/mingetty tty2
2601 tty3 Ss+ 0:00 /sbin/mingetty tty3
2602 tty4 Ss+ 0:00 /sbin/mingetty tty4
2603 tty5 Ss+ 0:00 /sbin/mingetty tty5
2604 tty6 Ss+ 0:00 /sbin/mingetty tty6
2605 ? Ss 0:00 /usr/sbin/gdm-binary -nodaemon
2682 ? S 0:00 /usr/sbin/gdm-binary -nodaemon
2686 ? S 0:13 /usr/sbin/gdm-binary -nodaemon
2687 tty7 SLs+ 5:28 /usr/bin/X :0 -br -audit 0 -auth /var/gdm/:0.Xauth
-n
2718 ? SL 0:00 /usr/bin/gnome-keyring-daemon -d
2719 ? Ssl 0:00 /usr/bin/gnome-session
2781 ? Ss 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch
--exit-with-s
2784 ? S 0:00 /usr/bin/dbus-launch --exit-with-session
/etc/X11/xin
2785 ? Ssl 0:00 /bin/dbus-daemon --fork --print-pid 4
--print-address
2792 ? S 0:37 /usr/libexec/gconfd-2 13
2796 ? Sl 0:03 /usr/libexec/gnome-settings-daemon
2800 ? Sl 0:22 /usr/bin/pulseaudio --log-target=syslog
2806 ? S 0:00 /usr/libexec/pulse/gconf-helper
2807 ? S 0:09 metacity --sm-client-id=default1
2809 ? S 0:07 gnome-panel --sm-client-id default2
2810 ? S 0:24 nautilus --no-default-window --sm-client-id default3
2814 ? Ss 0:00 gnome-volume-manager --sm-client-id default4
2816 ? Ssl 0:00 /usr/libexec/bonobo-activation-server --ac-activate
-
2821 ? S 0:00 /usr/libexec/gnome-vfs-daemon
2839 ? S 0:00 nm-applet --sm-disable
2841 ? S 0:00 python /usr/share/system-config-printer/applet.py
2842 ? S 0:00 pam-panel-icon --sm-client-id default0
2843 ? S 0:00 /sbin/pam_timestamp_check -d root
2846 ? S 0:01 /usr/bin/python -E /usr/bin/sealert -s
2847 ? Ss 0:01 gnome-power-manager
2860 ? S 0:10 /usr/libexec/wnck-applet
--oaf-activate-iid=OAFIID:GN
2862 ? S 0:00 /usr/libexec/trashapplet
--oaf-activate-iid=OAFIID:GN
2864 ? S 1:51 /usr/libexec/sensors-applet
--oaf-activate-iid=OAFIID
2889 ? Ss 0:36 gnome-screensaver
2892 ? S 0:00 /usr/libexec/mapping-daemon
2899 ? S 0:13 /usr/libexec/cpufreq-applet
--oaf-activate-iid=OAFIID
2904 ? S 0:00 /usr/libexec/notification-area-applet
--oaf-activate-
2906 ? S 0:00 /usr/libexec/fast-user-switch-applet
--oaf-activate-i
2908 ? S 0:01 /usr/libexec/clock-applet
--oaf-activate-iid=OAFIID:G
2910 ? Sl 0:00 /usr/libexec/mixer_applet2
--oaf-activate-iid=OAFIID:
2917 ? S 0:00 /usr/libexec/gam_server
3403 ? Sl 1669:13 /home/fred/mprime/mprime
6112 ? S 0:00 /bin/sh /usr/lib64/thunderbird-2.0.0.16/thunderbird
6116 ? S 0:00 /bin/sh
/usr/lib64/thunderbird-2.0.0.16/run-mozilla.s
6121 ? Sl 0:12 /usr/lib64/thunderbird-2.0.0.16/thunderbird-bin
6135 ? S 0:00 /bin/bash
/usr/lib64/thunderbird-2.0.0.16/open-browse
6139 ? S 0:00 /bin/sh /usr/lib64/firefox-2.0.0.17/firefox
http://ww
6156 ? S 0:00 /bin/sh /usr/lib64/firefox-2.0.0.17/run-mozilla.sh
/u
6161 ? Sl 3:55 /usr/lib64/firefox-2.0.0.17/firefox-bin
http://www.me
6762 ? Sl 0:00 gnome-terminal
6764 ? S 0:00 gnome-pty-helper
6765 pts/1 Ss 0:00 bash
6796 pts/1 R+ 0:00 ps ax
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years, 6 months
[Bug 229469] NFS fcntl locks being released locally but not on server
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=229469
--- Comment #27 from Michael Young <m.a.young(a)durham.ac.uk> 2008-10-28 07:38:41 EDT ---
Yes, you are right (though the Fedora 9 and Centos/RHEL 5 fix to get lockd
listening on udp is to uncomment the line LOCKD_UDPPORT=32769 in
/etc/sysconfig/nfs and presumably to change the value for security reasons).
What seems to have been happening in my tests were that once the lock was
released locally the other processes tried to get a lock and were of course
blocked, the netapp box releases the freed lock grants a new one but can't tell
the appropriate process. From then on, as the lock attempt that has unknowingly
succeeded times out, the lock gets passed unknowingly to another queuing
process, so the lock attempts never succeed.
So yes, provided the linux box is listening on UDP the locking seems to work
correctly now, but otherwise there is still the potential for competing locks
not to be granted to a process.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years, 6 months
[Bug 209110] iSCSI root device name should be dynamic
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=209110
--- Comment #14 from Hans de Goede <hdegoede(a)redhat.com> 2008-10-28 04:12:08 EDT ---
(In reply to comment #13)
> (In reply to comment #12)
>
> > What you are seeing here are 2 different problems:
> >
> > 1) The device name of iscsi disks is not stable
>
> Nope, that's not what I'm saying. My point is that the target name *is* stable
> and mkinitrd should be able to map the target name to a device name and map
> that device.
>
> > Solution: use a label or uuid for /
>
> Yep - that's one way of doing it, but "mount by target name" is a valid feature
> request too IMHO.
>
Agreed, but that indeed really is a *feature request*. To make this possible in
some sane manner we need a way to ask iscsiadm which device node / number the
iscsi subsystem has gotten / given to a certain target. Even better would be a
feature where iscsiadm on login would print the device name to stdout once the
login completes.
Actually having iscsiadm print the devicename it has gotten for a disk after
login would be absolutely great to have for anaconda too. Currently we're going
through much pain in anaconda to find a disk after we've logged in to the iscsi
target, and even when we've got a disk we do not know which disks corresponds
to which iscsi target.
I like the idea of iscsiadm login printing the device node for the disk after
login so much I'll file an RFE against iscsi-initiator-utils right away.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
15 years, 6 months