[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bugs #9043] find fails on automounter paths
From: |
James Youngman |
Subject: |
[bugs #9043] find fails on automounter paths |
Date: |
Sun, 21 Nov 2004 09:12:26 -0500 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Epiphany/1.2.9 |
This mail is an automated notification from the bugs tracker
of the project: findutils.
/**************************************************************************/
[bugs #9043] Latest Modifications:
Changes by:
James Youngman <address@hidden>
'Date:
Sun 11/21/2004 at 13:51 (GMT)
What | Removed | Added
---------------------------------------------------------------------------
Resolution | Postponed | Fixed
Fixed Release | None | 4.2.6
/**************************************************************************/
[bugs #9043] Full Item Snapshot:
URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9043>
Project: findutils
Submitted by: VenkateswaraRao
On: Fri 05/21/2004 at 10:25
Category: find
Severity: 5 - Average
Item Group: None
Resolution: Fixed
Privacy: Public
Assigned to: None
Originator Name:
Originator Email:
Status: Open
Release: None
Fixed Release: 4.2.6
Summary: find fails on automounter paths
Original Submission: The stat checks causing the find to quit where:
* The find path is an SUN automounter directory and
* It's not already mounted
<<SNIP>>
~> find /proj/test
find: /proj/test changed during execution of find
~> sudo umount /proj/test
~> gnu find /proj/test/.
/proj/test
/proj/test/file
...
<<>>
Thanks.
Follow-up Comments
------------------
-------------------------------------------------------
Date: Sun 11/21/2004 at 10:38 By: James Youngman <jay>
I think that automountd is the common factor here. When you chdir() into an
aoutomounted directory, that directory is mounted which causes the device
number (and inode of course) to change. This alarms the csanity check that we
do.
-------------------------------------------------------
Date: Mon 11/08/2004 at 21:47 By: James Youngman <jay>
findutils-4.2.4 has some extra diagnostics for this situation, could you
retest with that version and let me know what error message is produced?
Thanks.
(marked postponed, pending a response)
CC List
-------
CC Address | Comment
------------------------------------+-----------------------------
levon --AT-- movementarian --DOT-- org |
For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=9043>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bugs #9043] find fails on automounter paths, James Youngman, 2004/11/21
- [bugs #9043] find fails on automounter paths,
James Youngman <=
- [bugs #9043] find fails on automounter paths, James Youngman, 2004/11/21
- [bugs #9043] find fails on automounter paths, anonymous, 2004/11/21
- [bugs #9043] find fails on automounter paths, James Youngman, 2004/11/21
- [bugs #9043] find fails on automounter paths, James Youngman, 2004/11/21
- [bugs #9043] find fails on automounter paths, anonymous, 2004/11/21
- [bugs #9043] find fails on automounter paths, James Youngman, 2004/11/24
- [bugs #9043] find fails on automounter paths, anonymous, 2004/11/24
- [bugs #9043] find fails on automounter paths, James Youngman, 2004/11/24
- [bugs #9043] find fails on automounter paths, anonymous, 2004/11/26