Bug 8607 - rename ("foo", "nonemptybar") on NFS gets EBUSY with Linux Kernel
Summary: rename ("foo", "nonemptybar") on NFS gets EBUSY with Linux Kernel
Status: RESOLVED INVALID
Alias: None
Product: gdb
Classification: Unclassified
Component: external (show other bugs)
Version: unknown
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-08 19:18 UTC by ac131313
Modified: 2014-09-12 22:50 UTC (History)
4 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ac131313 2004-01-08 19:18:01 UTC 
[Converted from Gnats 1502]

Apparently:

$ mkdir foo
$ mkdir bar
$ $ cat ~/tmp/rename.c 
#include <stdio.h>
#include <errno.h>
main ()
{
  errno = 0;
  rename ("foo", "bar");
  printf ("errno %d\n", errno);
}
$ cc rename.c -o rename
$ ./rename
errno 16

Reports EBUSY on an NFS file system, and (the more correct) ENOTEMPTY on a local file system.

Apparently still present in current 2.6 Linux Kernel.

Release:
unknown
Comment 1 ac131313 2004-01-12 15:08:37 UTC 
From: Andrew Cagney <ac131313@redhat.com>
To: gdb-gnats@sources.redhat.com
Cc:  
Subject: Re: external/1502: rename ("foo", "nonemptybar") on NFS gets EBUSY
 with Linux Kernel
Date: Mon, 12 Jan 2004 10:08:37 -0500

 Missing step in example:
 
 $ mkdir foo
 $ mkdir bar
 $ touch bar/baz            ****
 $ cat ...
 
 The attempt to rename of a directory to a non-empty directory should 
 return something like ENOTEMPTY but returns EBUSY on NFS.
Comment 2 Andrew Cagney 2004-02-12 03:39:53 UTC 
State-Changed-From-To: open->feedback
State-Changed-Why: somebody elses problem
Comment 3 Sergio Durigan Junior 2014-09-12 22:50:37 UTC 
Not a GDB related bug.  Closing as INVALID.