Bug#317798: kernel-image-2.6.11-1-686-smp: nfs locking can cause a process to hang forever
Bastian Blank [EMAIL PROTECTED] writes: On Sun, Mar 26, 2006 at 12:31:58AM -0500, Marc Horowitz wrote: Do you have a reference to this document? Retrying forever doesn't seem awful (it wouldn't be my preference, but that's ok), but retrying *uninterruptably* seems like it would never be desirable behavior. mount(8) Ah, so it's not a soft mount I want. It's intr. I don't agree with the default, but it's clearly intentional, so you can close this bug. Thanks for all the help! Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317798: kernel-image-2.6.11-1-686-smp: nfs locking can cause a process to hang forever
Jurij Smakov [EMAIL PROTECTED] writes: I think that nfs strategy to retry forever is a documented feature, not a bug. You can override the behaviour by doing a 'soft' mount. If you believe that this bug should remain open, please provide additional information, otherwise I'll close this bug one week from now (Sunday, April 2nd 2006). Do you have a reference to this document? Retrying forever doesn't seem awful (it wouldn't be my preference, but that's ok), but retrying *uninterruptably* seems like it would never be desirable behavior. Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317798: kernel-image-2.6.11-1-686-smp: nfs locking can cause a process to hang forever
David Schmitt [EMAIL PROTECTED] writes: from nfs(5): soft If an NFS file operation has a major timeout then report an I/O error to the calling program. The default is to continue retrying NFS file operations indefinitely. So this seems to be a case of feature, not bug. It'd be great if you could test this with a soft-mount too. I set the mount on the client to soft, but the hang isn't happening with a hard mount right now. If I see the problem again, I'll experiment some more and report back. Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#328135: kernel-image-2.6.11-1-686-smp: nfs reading process stuck in disk wait
Package: kernel-image-2.6.11-1-686-smp
Version: 2.6.11-7
Severity: important
cvs D 0008 0 6344 3830 6345 6162 (NOTLB)
db6bdd18 0086 db6bdd08 0008 0002 e203cba4 c02edb60 0001
0001 0001 01d2 c013fe43 c02f33a0 c02f2b80 c1805fa0
b3f24580 000f9fc6 e3f4f540 e3f4f694 c02f33a0 0002
Call Trace:
[c013fe43] __alloc_pages+0x2e3/0x420
[c02ac668] io_schedule+0x28/0x40
[c013a6c5] sync_page+0x45/0x60
[c02ac9bf] __wait_on_bit_lock+0x5f/0x70
[c013a680] sync_page+0x0/0x60
[c0131f10] wake_bit_function+0x0/0x60
[c013af51] __lock_page+0x91/0xa0
[c0131f10] wake_bit_function+0x0/0x60
[c014286d] page_cache_readahead+0x24d/0x2d0
[c0131f10] wake_bit_function+0x0/0x60
[c013af9d] find_get_page+0x3d/0x50
[c013b897] do_generic_mapping_read+0x517/0x630
[c013bcb2] __generic_file_aio_read+0x212/0x250
[c013b9b0] file_read_actor+0x0/0xf0
[c013bd4b] generic_file_aio_read+0x5b/0x80
[f8cd1920] nfs_file_read+0xa0/0xf0 [nfs]
[c015ada7] do_sync_read+0xb7/0xf0
[c014d131] vma_merge+0xd1/0x1d0
[c014d7e1] do_mmap_pgoff+0x461/0x790
[c0131eb0] autoremove_wake_function+0x0/0x60
[c015aec5] vfs_read+0xe5/0x160
[c015b1e1] sys_read+0x51/0x80
[c0103123] syscall_call+0x7/0xb
I was doing a cvs add on a working directory in NFS, and the process
got stuck here. I don't know how to tell what file it was accessing.
I have seen this happen twice with this kernel in the past month, but
I don't know how to reliably reproduce it.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-1-686-smp
Locale: LANG=en_US.ISO8859-1, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Versions of packages kernel-image-2.6.11-1-686-smp depends on:
ii coreutils [fileutils] 5.2.1-2The GNU core utilities
ii initrd-tools 0.1.77 tools to create initrd image for p
ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327432: kernel-image-2.4.27-2-sparc32: upgrading from 2.2 kernel deadlocks with libc upgrade
Package: kernel-image-2.4.27-2-sparc32 Version: 2.4.27-9 Severity: important I had an old sparc which was running a 2.2.20 kernel (yes, old) and libc6 2.2.5-11.5. I tried to upgrade it (apt-get install dist-upgrade) and it choked. In particular, the kernel depends on a newer version of libc: locks-keyed-alike:~# apt-get install kernel-image-2.4-sparc32 Reading Package Lists... Done Building Dependency Tree... Done You might want to run `apt-get -f install' to correct these: Sorry, but the following packages have unmet dependencies: kernel-image-2.4-sparc32: Depends: kernel-image-2.4.27-2-sparc32 but it is not going to be installed libdb1-compat: Depends: libc6 (= 2.2.5-13) but 2.2.5-11.5 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). And the libc won't install without a newer kernel version: Do you want to upgrade glibc now? [Y/n] WARNING: You have a cpu which requires kernel 2.4.21 or greater in order to install this version of glibc. Please upgrade the kernel before installing this package. You should be able to install the latest version of the sparc kernel-image in order to satisfy this need. You can also download and compile the latest kernel source yourself from a kernel mirror (see http://www.kernel.org/). dpkg: error processing /var/cache/apt/archives/libc6_2.3.2.ds1-22_sparc.deb (--unpack): subprocess pre-installation script returned error exit status 1 At this point, apt-get -f install fails as above, I can't install the new libc without the new kernel, and I can't install the new kernel without the new libc. I eventually got myself out of this by replacing uname with a shell script which claimed I was running 2.4.21, and then actually upgraded everything, but this is a pretty absurd thing to have to do. -- System Information: Debian Release: 3.1 Architecture: sparc Kernel: Linux 2.4.27-2-sparc32 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-image-2.4.27-2-sparc32 depends on: ii initrd-tools 0.1.81.1 tools to create initrd image for p ii modutils 2.4.26-1.2 Linux module utilities -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327432: kernel-image-2.4.27-2-sparc32: upgrading from 2.2 kernel deadlocks with libc upgrade
Jurij Smakov [EMAIL PROTECTED] writes: On Fri, 9 Sep 2005, Marc Horowitz wrote: I had an old sparc which was running a 2.2.20 kernel (yes, old) and libc6 2.2.5-11.5. I tried to upgrade it (apt-get install dist-upgrade) and it choked. In particular, the kernel depends on a newer version of libc: This is a known issue, arising when attempting woody-sarge upgrade on sparc. Proper procedure for upgrading the kernel is documented in Sarge release notes (paragraph 4.3 and appendix A): http://www.debian.org/releases/stable/sparc/release-notes/ap-kernel-upgrade-howto.en.html Shouldn't the system somehow warn me I have a gun aimed at my foot *before* I pull the trigger? Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
