[bugs #8455] anomaly on large xfs filesystems

[Andreas Metzler]

This mail is an automated notification from the bugs tracker
 of the project: findutils.




/**************************************************************************/
[bugs #8455] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=8455>
Project: findutils
Submitted by: Andreas Metzler
On: Mon 04/05/04 at 15:29

Category:  find
Severity:  5 - Average
Item Group:  None
Resolution:  None
Assigned to:  None
Originator Name:  
Originator Email:  
Status:  Open
Release:  None
Fixed Release:  None


Summary:  anomaly on large xfs filesystems

Original Submission:  This is a copy of <http://bugs.debian.org/241538>.
Andrew Reid writes:
--------------------------
Version: 4.1.20-3

I am having a rather strange difficulty with the "find" command.

For many paths on my system, including all paths in my
account, I get:

> # find <path> -print
> find: <path>: Value too large for defined data type

The failure occurs in some directories but not others, as described
below.

The set-up of the machine is such that user home directories can be
accessed by multiple routes from the start of the file system.  I am
not certain that this is relevant, but describe it here for
completeness.
 
Users' actual home directories are divided into several numbered
"home" directories from the root, like this: /u/home<n>/<user>/

All user home directories are accessible via symlinks from
/u/users/<user> -> /u/home<n>/<user>

There is also a symlink at the root of the filesystem, 

/users -> /u/users

The client is an x86 machine.  The filesystems are remotely mounted
"xfs" file systems, mounted via NFS from an SGI file server.  Each
home<n> subdirectory is separately mounted on the client by way of an
automounter.  Most of these reside on separate disks on the server,
except for home1 and home2, which share a physical disk on the server.
The problem occurs for some of the /u/home<n>/ directories, but not
others.

All of these directories are exported identically (to each other) from
the file server, and imported identically by the client.  There are
hardware differences between the mounted disks, which correlate with
the "find" problem -- home directories which occupy 48GB disks and use
more than 28GB of them seem to have this problem.  The problem is also
common to all of the largest filesystems.

On a Debian "stable" client, importing the same file systems from the
same file server, running the same kernel, but using "find" from
version 4.1.7-2 of findutils, the problem does not occur.

On all systems, these calls work.
# find /u -maxdepth 1     
# find /u/users -maxdepth 1
 
On the problem system in the problem directories, these calls:
# find /u/home<n> -maxdepth 1
fail with the "Value too large" error -- this path argument
is the direct path to the home directory.

Although the filesystem and automounter configuration on these
machines is not trivial, it is nevertheless identical between "stable"
and "testing" machines, and the "find" bug occurs only on the
"testing" machines.  There is circumstantial evidence that the problem
involves large xfs filesystems. 
--------------------------

He later provided me with the ltrace I am attaching.
      thanks, cu andreas



CC List
-------

CC Address                          | Comment
------------------------------------+-----------------------------
andrewreid<andrew --DOT-- reid --AT-- nist --DOT-- gov> | Bug forwarded to 
upstream authors



File Attachments
-------------------

-------------------------------------------------------
Date: Mon 04/05/04 at 15:29  Name: findbug.ltrace  Size: 30KB   By: ametzler
ltrace output
http://savannah.gnu.org/bugs/download.php?item_id=8455&amp;item_file_id=1169






For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=8455>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/