Bug#714974: [Jfs-discussion] NFS 'readdir loop' error on JFS
Interesting stuff. Out of curiosity I just tried this myself, both client server are virtual machines running Debian/stable (3.2.0-4-amd64) and I was able to reproduce this. A test case would be: ## server: $ apt-get install nfs-kernel-server jfsutils $ dd if=/dev/zero bs=1M count=256 /var/test.img $ losetup -f /var/test.img $ mkfs.jfs /dev/loop0 $ mount -t jfs /dev/loop0 /mnt/disk $ tar -C / -cf - usr/share | tar -C /mnt/disk/ -xf - $ tail -1 /etc/exports /mnt/disk 192.168.0.0/24(rw,sync,no_root_squash,no_subtree_check) $ service nfs-kernel-server restart ## client $ apt-get install nfs-common $ showmount -e server | tail -1 /mnt/disk 192.168.0.0/24 $ tail -1 /etc/fstab server:/mnt/disk /mnt/nfs nfs rsize=8192,wsize=8192,intr 0 0 $ mount /mnt/nfs $ mount | tail -1 server:/mnt/disk on /mnt/nfs type nfs4 (rw,relatime,vers=4,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.137,minorversion=0,local_lock=none,addr=192.168.0.138) $ tar -cf - /mnt/nfs/ /dev/null tar: Removing leading `/' from member names tar: Removing leading `/' from hard link targets tar: /mnt/nfs/usr/share/perl/5.14.2/Pod/: Cannot savedir: Too many levels of symbolic links tar: Exiting with failure status due to previous errors $ dmesg | tail [ 63.912327] RPC: Registered named UNIX socket transport module. [ 63.913801] RPC: Registered udp transport module. [ 63.914713] RPC: Registered tcp transport module. [ 63.915644] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 63.949485] FS-Cache: Loaded [ 63.972688] FS-Cache: Netfs 'nfs' registered for caching [ 63.993300] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 284.733629] loop: module loaded [ 840.372846] NFS: directory 5.14.2/Pod contains a readdir loop.Please contact your server vendor. The file: Simple has duplicate cookie 18 [ 840.375842] NFS: directory 5.14.2/Pod contains a readdir loop.Please contact your server vendor. The file: Simple has duplicate cookie 18 There are no messages on the server when this happens. The message on the client repeats on every attempt, this Cannot savedir above may be triggering it. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.10.1308092352550.7...@trent.utfs.org
Bug#714694: Acknowledgement (linux-image-amd64: Could not start debian)
Hello, I could not reproduce the problem on other computers, and the 'rootdelay=N' solution works for me. You can feel free to close the bug. Thanks, -- Sébastien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/520609d3.9020...@chimrod.com
Bug#714974: [Jfs-discussion] NFS 'readdir loop' error on JFS
On 08/10/2013 02:28 AM, Christian Kujau wrote: Interesting stuff. Out of curiosity I just tried this myself, both client server are virtual machines running Debian/stable (3.2.0-4-amd64) and I was able to reproduce this. A test case would be: I still haven't rebooted that machine - last chance to ask for any test info - as it looks like you have a test case anyway. I haven't lost any data that I know of - just programs complaining etc. IMO, at one time, jfs was really a better choice ( good set of tools). Even in a few cases where hardware failed the jfs tools worked well. Today with everyone banging on ext4 it has become the better choice. ( I don't think IBM is interested in supporting jfs - no idea if they are phasing out jfs2? ). Karl Schmidt EMail k...@xtronics.com Transtronics, Inc. WEB http://secure.transtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 The world runs on individuals pursuing their separate interests. The great achievements of civilization have not come from government bureaus. Einstein didn’t construct his theory under order from a bureaucrat. Henry Ford didn’t revolutionize the automobile industry that way. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/520697dc.1030...@xtronics.com
Re: uswsusp patches for initramfs-tools (was: Bug#632627: Re[2]: resume file)
On Fri, 09 Aug 2013, Ben Hutchings escribi�: On Fri, 2013-08-09 at 13:41 +, Rodolfo García Peñas (kix) wrote: Ben Hutchings b...@decadent.org.uk escribió: On Fri, 2013-08-09 at 14:22 +0200, Ben Hutchings wrote: [...] Reconfiguring uswsusp should definitely not affect the behaviour of swsusp; that would be very surprising. I think the configuration should be transferred the other way: uswsusp should copy the resume device and offset from initramfs-tools configuration (if initramfs-tools is installed). Note, I'm only suggesting that this should be done at installation time. I think it would be confusing to simply make either of the current configuration files override the other. I do think it would be preferable to switch to a single configuration file for resume device and offset (or none, if automatic selection can work) but we would need a transition plan that minimises confusion and breakage. Yes, the best option is have only one configuration file. The user must select the resume device (if there are more than one). What package should modify that file? Perhaps linux-base? No. uswsusp doesn't need the kernel package (you can boot from a floppy). We need a (new?) package. uswsusp and initramfs-tools should depend on it. This package should include a script (/usr/bin/update-resume-file?) and the script should create/update a config file. The config file will be used by initramfs-tools and uswsusp (and cryptsetup and probably others). The file should include two lines, one for the resume device and other for the offset. Perhaps we should continue this thread on debian-devel, because more people could help. Feel free to forward this mail (my Internet connection here is crap). kix. Ben. -- Ben Hutchings I say we take off; nuke the site from orbit. It's the only way to be sure. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130810203716.ga10...@what.com.es
Bug#691902: Unable to shutdown Debian Wheezy via normal means
Package: src:linux Followup-For: Bug #691902 Dear Maintainer, I am unable to shutdown the computer by any means other then pressing the power button. I tried poweroff, shutdown -h -p, shutdown from KDE, etc. I tried kernel 2.6.32-5-amd64 and that works, i.e., it shuts down correctly. I also tried to comment the (halt -p -f ) command in K12halt at runlevel 0 and then do a halt. In this situation it restarts after shutdown as well. When I halt the system before running: K03network-manager K03nslcd K03postgresql K03slapd K03spamassassin K03virtualbox-ose K04sendsigs K05rsyslog K06umountnfs.sh K07nfs-common K07rpcbind K08hwclock.sh K08networking K09umountfs 10mdadm-raid K10umountroot K11mdadm-waitidle the PC powers off correctly. I tried some kernel paramters like acpi=noirq, acpi=force to no avail. Any help or workaround would be greatly appreciated Cheers Michael -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.46-1 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=UUID=ff63dec0-9e54-497f-a57a-ad4ee06a7b98 ro acpi=noirq quiet splash ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [6.162796] EDAC amd64: DRAM ECC enabled. [6.162802] EDAC amd64: K8 revE or earlier detected (node 1). [6.162870] EDAC amd64: CS0: Registered Double data rate SDRAM [6.162873] EDAC amd64: CS2: Registered Double data rate SDRAM [6.162913] EDAC MC1: Giving out device to 'amd64_edac' 'K8': DEV :00:19.2 [6.163497] EDAC PCI0: Giving out device to module 'amd64_edac' controller 'EDAC PCI controller': DEV ':00:18.2' (POLLED) [6.171224] ACPI: resource :00:07.2 [io 0xcc00-0xcc1f] conflicts with ACPI region ECIO [io 0xcc00-0xcc1f] [6.171228] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [6.200461] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel. [6.200469] Disabling lock debugging due to kernel taint [6.470779] AMD768 RNG detected [6.487937] [fglrx] Maximum main memory to use for locked dma buffers: 8830 MBytes. [6.488437] [fglrx] vendor: 1002 device: 94cc count: 1 [6.489094] [fglrx] ioport: bar 4, base 0xb000, size: 0x100 [6.489147] pci :04:00.0: PCI-APIC IRQ transform: INT A - IRQ 28 [6.489157] pci :04:00.0: setting latency timer to 64 [6.489616] [fglrx] Kernel PAT support is enabled [6.489651] [fglrx] module loaded - fglrx 8.97.2 [Nov 16 2012] with 1 minors [6.496798] powernow-k8: Power state transitions not supported [6.496807] powernow-k8: Power state transitions not supported [6.517563] parport_pc 00:0a: reported by Plug and Play ACPI [6.517688] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP] [6.556089] ACPI: resource amd756_smbus [io 0x10e0-0x10ef] conflicts with ACPI region PMIO [io 0x1000-0x10fe] [6.556094] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [6.612377] parport_pc :02:02.0: PCI-APIC IRQ transform: INT A - IRQ 26 [6.612384] PCI parallel port detected: 1409:7268, I/O at 0x8c00(0x8480), IRQ 26 [6.612414] parport1: PC-style at 0x8c00 (0x8480), irq 26 [PCSPP,TRISTATE] [6.736515] psmouse serio1: logips2pp: Detected unknown Logitech mouse model 127 [7.140491] snd_hda_intel :04:00.1: PCI-APIC IRQ transform: INT B - IRQ 28 [7.140576] snd_hda_intel :04:00.1: setting latency timer to 64 [7.287432] input: ImExPS/2 Logitech Explorer Mouse as /devices/platform/i8042/serio1/input/input4 [ 10.168023] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x000f0001 [ 10.185655] HDMI status: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=0 [ 10.185814] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:0b.0/:03:03.0/:04:00.1/sound/card0/input5 [ 11.574752] Adding 979960k swap on /dev/sdb2. Priority:-1 extents:1 across:979960k [ 11.63] Adding 979960k swap on /dev/sdc2. Priority:-2 extents:1 across:979960k [ 12.210687] EXT3-fs (md1): using internal journal [ 12.326219] loop: module loaded [ 12.584849] vboxdrv: Found 2 processor cores. [ 12.585026] vboxdrv: fAsync=0 offMin=0x5c0 offMax=0x1a1c [ 12.585176] vboxdrv: TSC mode is 'asynchronous', kernel timer mode is 'normal'. [ 12.585179] vboxdrv: Successfully loaded version 4.2.16 (interface 0x001a0005). [ 14.849437] kjournald starting. Commit interval 5 seconds [ 14.877552] EXT3-fs (md0): using internal journal [ 14.877560] EXT3-fs (md0): mounted filesystem with ordered data mode [ 14.921990] kjournald starting. Commit interval 5 seconds [ 14.956090] EXT3-fs (md2): using internal journal [ 14.956094] EXT3-fs (md2): mounted filesystem with ordered data mode [ 14.981408]
