From owner-freebsd-bugs  Tue Jan  4 15:30: 6 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id EDBF414D0A
	for <freebsd-bugs@FreeBSD.org>; Tue,  4 Jan 2000 15:30:04 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id PAA48661;
	Tue, 4 Jan 2000 15:30:04 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 64E4714CB8; Tue,  4 Jan 2000 15:20:18 -0800 (PST)
Message-Id: <20000104232018.64E4714CB8@hub.freebsd.org>
Date: Tue,  4 Jan 2000 15:20:18 -0800 (PST)
From: lintux@dds.nl
To: freebsd-gnats-submit@freebsd.org
X-Send-Pr-Version: www-1.0
Subject: gnu/15892: NFS-exported ext2 file system makes Linux crash
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         15892
>Category:       gnu
>Synopsis:       NFS-exported ext2 file system makes Linux crash
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jan  4 15:30:01 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     Wilmer van der Gaast
>Release:        3.2
>Organization:
>Environment:
Hmm... Don't have it running at the moment. Is it important???? Yes.
Well, what I can say at the moment is that it is a custom kernel built
from the original source tree that comes with 3.2

>Description:
I am trying to migrate my Linux system to FreeBSD, and the first few
weeks/months, I want to be able to use both system, so I want to mount
the data-partition in both systems. This is an ext2 file system, and
it works perfectly, but when I export it, also something that doesn't
always work perfectly, and I mount it from Linux, I can do a normal ls
on it, but when i do ls -i or ls -la, I get the following error message
on the Linux box:

__nfs_fhget: inode 196 still busy, i_count=1

Inode 196 is the quota.user file, maybe that's a cause.

It might be a Linux-specific problem, but as it doesn't happen when I
export the file system using Linux, it's also FreeBSD specific.

>How-To-Repeat:
1. Mount the ext2 file system on the FBSD box, maybe you need a file-
   system with quotas
2. Export the file system
3. Mount the filesystem from a Linux box (Kernel 2.2.13)
4. ls -la /mount-point on the file system

It's a good idea to remount the other filesystems read-only on the
Linux box, because the system crashes after the last command. :(

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message