Bug#858967: initramfs-tools: Superfluous LVM errors before passphrase prompt after LUKS+LVM install
Package: initramfs-tools Version: 0.127 Severity: minor Although minor, it's pretty ugly to look at first thing when booting; see attached screenshot. After using the debian installer's guided LUKS+LVM option, the LVM volumes are inside a LUKS container which must be unlocked with a passphrase before any of them are visible. Everything works fine, except that for some reason the initramfs tries to bring up LVM, and even looks for the hidden volume group by name, before asking for the passphrase. After that fails, it asks for the passphrase, and then seems to start LVM again, which succeeds and boot proceeds successfully. It would be better if initramfs were aware that this volume group depends on a certain crypttab entry, and didn't try to bring the former up before unlocking the latter. This way, the first thing seen at boot would be the passphrase prompt. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 20M Mar 28 17:34 /boot/initrd.img-4.9.0-1-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-4.9.0-1-amd64 root=/dev/mapper/stretch--vg-root ro quiet -- resume RESUME=/dev/mapper/stretch--vg-swap_1 -- /proc/filesystems ext3 ext2 ext4 -- lsmod Module Size Used by uinput 20480 0 snd_hda_codec_generic69632 1 ppdev 20480 0 qxl69632 4 snd_hda_intel 36864 3 ttm98304 1 qxl snd_hda_codec 135168 2 snd_hda_intel,snd_hda_codec_generic drm_kms_helper155648 1 qxl snd_hda_core 81920 3 snd_hda_intel,snd_hda_codec,snd_hda_codec_generic snd_hwdep 16384 1 snd_hda_codec drm 360448 7 qxl,ttm,drm_kms_helper snd_pcm 110592 3 snd_hda_intel,snd_hda_codec,snd_hda_core pcspkr 16384 0 joydev 20480 0 snd_timer 32768 1 snd_pcm evdev 24576 6 virtio_balloon 16384 0 virtio_console 24576 0 snd86016 12 snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_generic,snd_pcm serio_raw 16384 0 soundcore 16384 1 snd sg 32768 0 parport_pc 28672 0 parport49152 2 parport_pc,ppdev acpi_cpufreq 20480 0 tpm_tis16384 0 tpm_tis_core 20480 1 tpm_tis tpm45056 2 tpm_tis,tpm_tis_core button 16384 0 ip_tables 24576 0 x_tables 36864 1 ip_tables autofs440960 2 ext4 585728 2 crc16 16384 1 ext4 jbd2 106496 1 ext4 crc32c_generic 16384 0 fscrypto 28672 1 ext4 ecb16384 0 mbcache16384 3 ext4 algif_skcipher 20480 0 af_alg 16384 1 algif_skcipher hid_generic16384 0 usbhid 53248 0 hid 122880 2 hid_generic,usbhid dm_crypt 24576 1 dm_mod118784 9 dm_crypt sr_mod 24576 0 cdrom 61440 1 sr_mod ata_generic16384 0 virtio_net 28672 0 virtio_blk 20480 3 crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 crc32c_intel 24576 2 ghash_clmulni_intel16384 0 aesni_intel 167936 3 aes_x86_64 20480 1 aesni_intel lrw16384 1 aesni_intel gf128mul 16384 1 lrw glue_helper16384 1 aesni_intel ablk_helper16384 1 aesni_intel cryptd 24576 4 ablk_helper,ghash_clmulni_intel,aesni_intel psmouse 135168 0 ata_piix 36864 0 libata249856 2 ata_piix,ata_generic floppy 69632 0 uhci_hcd 45056 0 ehci_pci 16384 0 ehci_hcd 81920 1 ehci_pci scsi_mod 225280 3 libata,sr_mod,sg usbcore 249856 4 usbhid,ehci_hcd,uhci_hcd,ehci_pci i2c_piix4 24576 0 virtio_pci 24576 0 virtio_ring24576 5 virtio_blk,virtio_net,virtio_balloon,virtio_console,virtio_pci usb_common 16384 1 usbcore virtio 16384 5 virtio_blk,virtio_net,virtio_balloon,virtio_console,virtio_pci -- /etc/initramfs-tools/modules -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=auto KEYMAP=n COMPRESS=gzip DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /etc/crypttab vda5_crypt UUID=f96f4a3e-07a8-4aa4-8123-d83ba6c24f53 none luks -- mkinitramfs hooks /etc/initramfs-tools/hooks/: /usr/share/initramfs-tools/hooks: cryptgnupg cryptkeyctl cryptopenct cryptopensc cryp
Bug#847999: marked as done (Maintainer and Vcs information are out-of-date)
Your message dated Wed, 29 Mar 2017 01:48:46 + with message-id and subject line Bug#847999: fixed in mkvmlinuz 39 has caused the Debian Bug report #847999, regarding Maintainer and Vcs information are out-of-date to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 847999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mkvmlinuz Version: 38 Severity: normal Milan, the Vcs-* fields in mkvmlinuz point to the kernel team's old Subversion repository but you never committed there. Please remove or update these fields. You seem to be the only maintainer for the package and are not using a kernel team repository, so please also update the Maintainer and Uploaders fields to show this. Ben. -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: mkvmlinuz Source-Version: 39 We believe that the bug you reported is fixed in the latest version of mkvmlinuz, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 847...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated mkvmlinuz package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 29 Mar 2017 02:27:50 +0100 Source: mkvmlinuz Binary: mkvmlinuz Architecture: source Version: 39 Distribution: unstable Urgency: medium Maintainer: Milan Kupcevic Changed-By: Ben Hutchings Description: mkvmlinuz - create a kernel to boot a PowerPC machine from Open Firmware Closes: 847999 Changes: mkvmlinuz (39) unstable; urgency=medium . * Team upload * Update maintainer and Vcs information (Closes: #847999): - Hand over from kernel team to Milan Kupcevic - Remove references to now-unused svn repository * Conform to Debian Policy standards version 3.9.8 (no changes required) * Bump debhelper compatibility to 9 Checksums-Sha1: fb6c2ee2921df4203f0ba4a4f8a8011fcdf63703 1466 mkvmlinuz_39.dsc 27667b0017070698a4cd24edd5673e53152457f2 52772 mkvmlinuz_39.tar.xz d287951eabadaa45d0bafcb4392726e100925645 5761 mkvmlinuz_39_source.buildinfo Checksums-Sha256: bb1d41f482b22e7218b726ae11715a810fe955439b089eece529deafef63c87c 1466 mkvmlinuz_39.dsc 23722a19fee4a8e4461a9ed51bc8789594381c8ef9c581a4029515be1ff4e349 52772 mkvmlinuz_39.tar.xz 7d3358c8124bfb95e9d17eae8137ee5fa3340a87f19b5abeb3079c1f4c882173 5761 mkvmlinuz_39_source.buildinfo Files: 31b15962b140ed4b20444830b7be9317 1466 utils optional mkvmlinuz_39.dsc a7a8ee5c7bdad4000db604dc21e405df 52772 utils optional mkvmlinuz_39.tar.xz 0539ba2c202ea598e21aed133b233a45 5761 utils optional mkvmlinuz_39_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAljbD5YACgkQ57/I7JWG EQnbRQ/9HdNsVPulO1KtD+FBC0CyqI6ZylWNCF5iDPUOmwogr4f6VrwCvjuIu8F/ 850AMl1yTCEvJ6K1wrSQHQiLtPLAsE1zdgbZy6NkEW5orAqlQwtuqzZF2bqyuu89 RUTuyD6O0C/08bo8QnRJz1HI/q7+kfUR66BUScV3iqbEF7bcCwO5uVi8oyEN4f5h Wy63O32uvPFuu+ZXqWIlgMxJqw65/A8itm2ialVn9/tehw7VB1Kmkn4vUb1HUCf8 TifBLY33iKJ4R7N/o0gVhJ3hcg9lN/xLhd564MOwEfd2Ny4rAzlq2lBF5V1A3hZ6 8RH4+OM4yaZfEFIYrWIO2nS7TpQyIKvbw3M2mpKx1t48z51FYhCMCSN9PB09/Vc+ lHRo8zh+shQ70qxO8RgPdPLRd+RERB1DX57dslhdObIt81BZuGdFDTS+OXzo3opO 0+Cio1n8c/RKoILni7iF4huGuS5/FA5DzpQW53itC7i/Z+H4ey1nZGc9pAvxEPUr 98vIIvwpOUw0xGs8Tm/DmDKqupQCriRk5xiZBOV6EJAidTcnunf3XT3f42pEWK9A NHTsirygIWunHvfbo4Rb608t1MRm3SNKYl7PiwU6RSxQ9tB8nJMyhIj7JvoddyuE EloZ0fvbqhvyljG052tBB05xhOkT113Qblp8Jt5ROn1AtI/YYvc= =qNhG -END PGP SIGNATURE End Message ---
Bug#850780: marked as done (linux-image-4.8.0-2-amd64: can't boot on Acer Aspire V5, stuck on initrd)
Your message dated Tue, 28 Mar 2017 15:53:07 +0100 with message-id <1490712787.2634.19.ca...@decadent.org.uk> and subject line Re: Bug#850780: linux-image-4.8.0-2-amd64: can't boot on Acer Aspire V5, stuck on initrd has caused the Debian Bug report #850780, regarding linux-image-4.8.0-2-amd64: can't boot on Acer Aspire V5, stuck on initrd to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 850780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850780 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.8.15-2 Severity: critical Justification: breaks the whole system I'm still stuck with linux 4.6 on this laptop. Both the current 4.7 and 4.8 images just hangs on "Loading initramfs". There aren't any further messages. It has similarities to #841883, but I'm submitting a separate report just in case. (After all, perhaps 4.8.7-1 fixed the issue for that submitter, but it certainly didn't for me.) I tried using "earlyprintk=vga" like suggested in #841850, but it had no effect. Maybe that option doesn't work if grub2 boots in graphics mode, but I'm not sure how to disable that without causing other boot errors. Maybe you have some ideas? Not sure what other information would be useful from me. I couldn't use reportbug because it currently seems broken (crashes while collecting information). But here's the /proc/cpuinfo for the first cpu core, at least: processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 19 model name : AMD A10-5757M APU with Radeon(tm) HD Graphics stepping: 1 microcode : 0x6001119 cpu MHz : 1400.000 cache size : 2048 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bugs: fxsave_leak sysret_ss_attrs bogomips: 4990.76 TLB size: 1536 4K pages clflush size: 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro --- End Message --- --- Begin Message --- Version: 4.9.13-1 On Tue, 2017-03-28 at 13:01 +0200, Ove Kåven wrote: > Package: src:linux > Followup-For: Bug #850780 > > I've tried booting the current kernels, and the current > linux-image-4.9.0-2-amd64 (version 4.9.13-1) is able to boot on this > system. Thanks for letting us know. Ben. -- Ben Hutchings Experience is directly proportional to the value of equipment destroyed. - Carolyn Scheppner signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#837907: more on NFS client hangs
I have some more information about [what I believe to be] this problem.
We've had similar incidents from several clients, running kernels 3.16.{36,39}
and 4.9 (jessie-backports). I think this rules out a client hardware issue.
The trigger (from the client's perspective) seems to be loss of contact with
the NFS server. The incidents are almost always preceded by one or more
nfs: server not responding, still trying
log entries. Sometimes there is a known server-side explanation (e.g.,
nfsd thread exhaustion), but not always. In any case, the effects persist
well after communication with the server has recovered; "reboot -f" seems
to be necessary for client recovery, as sync() also hangs indefinitely.
Kernel stack traces on the client vary, as do the affected files and
applications; the issue is by no means limited to Firefox or sqlite.
If desired, I can submit a selection of stack traces (as one bug or as several).
I'm looking for suggestions on how to debug this. I'm thinking of turning on
logging with rpcdebug on the the most frequently affected clients, to better
understand the trigger. Is there anything else I should be looking at?
Bug#858897: linux-image-4.10.0-trunk-amd64-unsigned: NETFILTER_XT_MATCH_SOCKET and NF_SOCKET_IPV4 are disabled: IP_TRANSPARENT does not work
Package: src:linux Version: 4.10-1~exp1 Severity: normal NETFILTER_XT_MATCH_SOCKET and NF_SOCKET_IPV4 are disabled in the kernel config. As a result, IP_TRENSPARENT server can not be set up: $ sudo iptables -t mangle -A PREROUTING -p tcp -m socket -j DIVERT > iptables: No chain/target/match by that name. NF_SOCKET_IPV4 is a new config option in the linux-4.10; NETFILTER_XT_MATCH_SOCKET depends on it. -- Package-specific info: ** Version: Linux version 4.10.0-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170221 (Debian 6.3.0-8) ) #1 SMP Debian 4.10-1~exp1 (2017-02-22) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-trunk-amd64 root=UUID=c5078393-d2ff-435d-82e8-e85990b3c9e2 ro net.ifnames=0 console=tty1 console=ttyS1,115200n8 intel_iommu=on intel_pstate=disable nmi_watchdog=nopanic intel_idle.max_cstate=0 idle=poll ** Tainted: POE (12289) * Proprietary module has been loaded. * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: Dell Inc. product_name: PowerEdge R220 product_version: 01 chassis_vendor: Dell Inc. chassis_version: 01 bios_vendor: Dell Inc. bios_version: 1.4.0 board_vendor: Dell Inc. board_name: 05Y15N board_version: A04 ** Loaded modules: team_mode_activebackup(E) team(E) onload(OE) onload_cplane(POE) sfc_char(OE) sfc_resource(OE) sfc_affinity(OE) sfc(OE) iptable_raw(E) iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack(E) libcrc32c(E) iptable_mangle(E) mtd(E) mdio(E) hwmon_vid(E) crc32_generic(E) mii(E) autofs4(E) cpufreq_userspace(E) cpufreq_powersave(E) cpufreq_conservative(E) iptable_filter(E) ip_tables(E) x_tables(E) hmac(E) cbc(E) cts(E) nfsv4(E) dns_resolver(E) rpcsec_gss_krb5(E) nfsd(E) auth_rpcgss(E) nfs_acl(E) nfs(E) lockd(E) grace(E) fscache(E) sunrpc(E) 8021q(E) garp(E) mrp(E) stp(E) llc(E) nls_ascii(E) nls_cp437(E) vfat(E) fat(E) ipmi_watchdog(E) loop(E) intel_rapl(E) x86_pkg_temp_thermal(E) intel_powerclamp(E) coretemp(E) kvm_intel(E) kvm(E) irqbypass(E) crct10dif_pclmul(E) mgag200(E) crc32_pclmul(E) ttm(E) ghash_clmulni_intel(E) drm_kms_helper(E) intel_cstate(E) ppdev(E) drm(E) efi_pstore(E) i2c_algo_bit(E) intel_uncore(E) dcdbas(E) joydev(E) intel_rapl_perf(E) evdev(E) efivars(E) sg(E) pcspkr(E) intel_vbtn(E) acpi_als(E) winbond_cir(E) kfifo_buf(E) battery(E) ie31200_edac(E) sparse_keymap(E) industrialio(E) rc_core(E) parport_pc(E) ipmi_si(E) soc_button_array(E) edac_core(E) ac(E) parport(E) ipmi_devintf(E) acpi_cpufreq(E) ipmi_msghandler(E) video(E) lpc_ich(E) tpm_tis(E) shpchp(E) mfd_core(E) tpm_tis_core(E) button(E) tpm(E) ext4(E) crc16(E) jbd2(E) crc32c_generic(E) fscrypto(E) ecb(E) mbcache(E) hid_generic(E) usbhid(E) hid(E) sd_mod(E) tg3(E) ptp(E) crc32c_intel(E) aesni_intel(E) ahci(E) aes_x86_64(E) libahci(E) crypto_simd(E) libata(E) cryptd(E) xhci_pci(E) pps_core(E) ehci_pci(E) xhci_hcd(E) ehci_hcd(E) glue_helper(E) i2c_i801(E) libphy(E) scsi_mod(E) usbcore(E) usb_common(E) thermal(E) fan(E) fjes(E) ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller [8086:0c08] (rev 06) Subsystem: Dell Xeon E3-1200 v3 Processor DRAM Controller [1028:05e5] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05) (prog-if 30 [XHCI]) Subsystem: Dell 8 Series/C220 Series Chipset Family USB xHCI [1028:05e5] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 05) (prog-if 20 [EHCI]) Subsystem: Dell 8 Series/C220 Series Chipset Family USB EHCI [1028:05e5] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ehci-pci 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Seri
Bug#850780: linux-image-4.8.0-2-amd64: can't boot on Acer Aspire V5, stuck on initrd
Package: src:linux Followup-For: Bug #850780 I've tried booting the current kernels, and the current linux-image-4.9.0-2-amd64 (version 4.9.13-1) is able to boot on this system. Thank you. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (900, 'testing'), (600, 'stable'), (500, 'unstable-debug'), (1, 'experimental-debug'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#858884: nfs-common : mounting is done before network time adjustment
Package: nfs-common Version: 1:1.3.4-2.1 Dear maintainer, here is what I see in journalctl (/users is a Kerberos NFS mount point): Mar 28 09:55:57 file-info2 systemd[1]: Mounted /users. Mar 28 09:55:57 file-info2 systemd[1]: Started /etc/rc.local Compatibility. Mar 28 09:55:57 file-info2 systemd[1]: Reached target Remote File Systems. [...] Mar 28 09:56:26 file-info2 systemd-timesyncd[293]: Synchronized to time server 80.74.64.2:123 (2.debian.pool.ntp.or Mar 28 09:56:26 file-info2 systemd[1]: Time has been changed When mounting NFS shares with Kerberos, it is important that time is synchronized between server and clients. In this case mounting succeeded because the time difference was acceptable. But it may not always be the same (for instance if the client has no battery to maintain time when it is off). So how about ordering NFS mounts after time synchronization during boot ? -- Laurent.
