RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 603707 - cifs: busy file renames across directories should fail with error
Summary: cifs: busy file renames across directories should fail with error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Jeff Layton
QA Contact: yanfu,wang
URL:
Whiteboard:
Depends On:
Blocks: 591938 603706
TreeView+ depends on / blocked
 
Reported: 2010-06-14 12:18 UTC by Jeff Layton
Modified: 2014-06-18 07:40 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 603706
Environment:
Last Closed: 2010-11-11 15:53:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 RHEL Program Management 2010-06-14 12:43:01 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 3 Aristeu Rozanski 2010-07-01 16:23:08 UTC 
Patch(es) available on kernel-2.6.32-42.el6
Comment 6 yanfu,wang 2010-09-02 03:28:47 UTC 
I verified on rhel6-snaphshot13 but still got 'Text file busy' error using the reproducer:

[root@amd-dinar-03 test]# uname -a
Linux amd-dinar-03.lab.bos.redhat.com 2.6.32-70.el6.i686 #1 SMP Wed Aug 25 10:10:17 EDT 2010 i686 i686 i386 GNU/Linux

win2k3 share dir is temp:
[root@amd-dinar-03 test]# mount
...
//10.66.65.54/temp/ on /mnt/test type cifs (rw,mand)

[root@amd-dinar-03 test]# ls -l        
total 0
-rwxr-xr-x. 1 root root 3890 Jan 24  2011 aa
drwxr-xr-x. 1 root root    0 Jan 24  2011 done
[root@amd-dinar-03 test]# mv aa done/bb
mv: cannot move `aa' to `done/bb': Text file busy
Comment 7 Jeff Layton 2010-09-02 10:47:19 UTC 
That's expected. The error is expected when the file is open and you try to rename it across directories. The bug was that the file would be renamed but would stay in the original directory.
Comment 8 Ric Wheeler 2010-09-02 13:43:06 UTC 
This works as we expect it to work. Can we please sync up on the test case and make sure that this is resolved?

Thanks!
Comment 9 Denise Dumas 2010-09-02 13:50:37 UTC 
Based on above comments, moving back to on-qa
Comment 10 yanfu,wang 2010-09-03 07:20:50 UTC 
verified on i386 and x86_64 on rhel6-snaphshot13, the results same as comment #6 and comment #7.
Comment 11 releng-rhel@redhat.com 2010-11-11 15:53:38 UTC 
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Note You need to log in before you can comment on or make changes to this bug.