[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#387420: marked as done (linux-image-2.6.17-2-k7: NFS misbehaviour when mounting dir from FreeBSD NFS server)

Your message dated Tue, 3 Oct 2006 09:34:31 -0600
with message-id <[🔎] 20061003153431.GB25030@colo>
and subject line Bug#387420: Bug #387420 can probably be closed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: linux-image-2.6.17-2-k7
Version: 2.6.17-8
Severity: normal


Hi all,

I am running a FreeBSD NFS server (5.4-RELEASE) sharing $HOME and some 
other directories to my Debian Linux clients.

Since kernel version 2.6.16 (so up to 2.6.15 everything works like
expected) I have the following problem:

When editing a file located on the NFS server, for example a text
file using vi, and that file belongs to another user but is
group-writeable (bits 77X), I get the error message "Operation not permitted."
when trying to save and the size of that file changes to 0 bytes (very dangerous !).

What does work is something like "echo bla >> file/on/nfsshare/test.txt",
so appending data to an existing file using redirect.

After trying to edit that file again using vi it ends up again in
the above error messages and the file size changes back to 0 bytes.

I can reproduce this behaviour with kernel 2.6.16, .17 and .18-rc7.

With 2.6.8 (from Sarge) - and I also tested 2.6.14 and 2.6.15 - it
works flawless.

Let me know if you need any further details.

Kind regards, Joerg.



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages linux-image-2.6.17-2-k7 depends on:
ii  module-init-tools             3.2.2-3    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-18  Yet Another mkInitRD

Versions of packages linux-image-2.6.17-2-k7 recommends:
ii  libc6-i686                   2.3.6.ds1-4 GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.17-2-k7/postinst/old-system-map-link-2.6.17-2-k7: true
  linux-image-2.6.17-2-k7/preinst/overwriting-modules-2.6.17-2-k7: true
  linux-image-2.6.17-2-k7/postinst/create-kimage-link-2.6.17-2-k7: true
  linux-image-2.6.17-2-k7/preinst/failed-to-move-modules-2.6.17-2-k7:
  linux-image-2.6.17-2-k7/preinst/bootloader-initrd-2.6.17-2-k7: true
  linux-image-2.6.17-2-k7/preinst/abort-overwrite-2.6.17-2-k7:
  linux-image-2.6.17-2-k7/postinst/old-dir-initrd-link-2.6.17-2-k7: true
  linux-image-2.6.17-2-k7/preinst/abort-install-2.6.17-2-k7:
  linux-image-2.6.17-2-k7/preinst/initrd-2.6.17-2-k7:
  linux-image-2.6.17-2-k7/postinst/depmod-error-initrd-2.6.17-2-k7: false
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.17-2-k7/prerm/removing-running-kernel-2.6.17-2-k7: true
  linux-image-2.6.17-2-k7/postinst/kimage-is-a-directory:
  linux-image-2.6.17-2-k7/prerm/would-invalidate-boot-loader-2.6.17-2-k7: true
  linux-image-2.6.17-2-k7/preinst/already-running-this-2.6.17-2-k7:
  linux-image-2.6.17-2-k7/postinst/old-initrd-link-2.6.17-2-k7: true
  linux-image-2.6.17-2-k7/postinst/depmod-error-2.6.17-2-k7: false
  linux-image-2.6.17-2-k7/preinst/lilo-initrd-2.6.17-2-k7: true
  linux-image-2.6.17-2-k7/postinst/bootloader-error-2.6.17-2-k7:
  linux-image-2.6.17-2-k7/preinst/lilo-has-ramdisk:
  linux-image-2.6.17-2-k7/postinst/bootloader-test-error-2.6.17-2-k7:
  linux-image-2.6.17-2-k7/preinst/elilo-initrd-2.6.17-2-k7: true

--- End Message ---
--- Begin Message --- 
In-Reply-To: <[🔎] 452244C6.50109@morbitzer.de>

On Tue, Oct 03, 2006 at 01:08:54PM +0200, Joerg Morbitzer wrote:
> 
> Hi,
> 
> I just upgraded my FreeBSD NFS-Server from version 5.4-RELEASE to 5.5-RELEASE-p4 and the NFS 
> problems are gone now.
> 
> So it was either a FreeBSD problem or a correlation between changes in recent Linux kernels and 
> FreeBSD version 5.4.
> 
> So the bug #387420 can be closed I think.

Closing then, thanks for the follow-up Joerg.

-- 
dann frazier

--- End Message ---
Reply to: