[Gluster-users] GlusterFS 3.1.2 with "No such file" & "Invalid argument" errors

[Pan, Henry]

Dear Gluster Gurus,

My eDiscovery app got 6 billions small files. Any suggestion to transfer them quickly into GlusterFS without "No such file" & "Invalid argument" errors?

Thanks & Good w/e

Henry PAN
Sr. Data Storage Engineer
Iron Mountain
(650) 962-6184 (o)
(650) 930-6544 (c)
Henry.pan at ironmountain.com


-----Original Message-----
From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of gluster-users-request at gluster.org
Sent: Friday, January 28, 2011 12:00 PM
To: gluster-users at gluster.org
Subject: Gluster-users Digest, Vol 33, Issue 50

Send Gluster-users mailing list submissions to
	gluster-users at gluster.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
or, via email, send a message with subject or body 'help' to
	gluster-users-request at gluster.org

You can reach the person managing the list at
	gluster-users-owner at gluster.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gluster-users digest..."


Today's Topics:

   1. 3.1.2 with "No such file" and "Invalid argument"	errors
      (Steve Wilson)


----------------------------------------------------------------------

Message: 1
Date: Fri, 28 Jan 2011 12:49:03 -0500
From: Steve Wilson <stevew at purdue.edu>
Subject: [Gluster-users] 3.1.2 with "No such file" and "Invalid
	argument"	errors
To: Gluster General Discussion List <gluster-users at gluster.org>
Message-ID: <4D43018F.1020607 at purdue.edu>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

I'm running a pair of replicated/distributed GlusterFS 3.1.2 servers, 
each with 8 bricks.  Here's the command I used to create the data volume:

    gluster volume create post replica 2 transport tcp
    pablo:/gluster/01/brick stanley:/gluster/01/brick \
    pablo:/gluster/02/brick stanley:/gluster/02/brick \
    pablo:/gluster/03/brick stanley:/gluster/03/brick \
    pablo:/gluster/04/brick stanley:/gluster/04/brick \
    pablo:/gluster/05/brick stanley:/gluster/05/brick \
    pablo:/gluster/06/brick stanley:/gluster/06/brick \
    pablo:/gluster/07/brick stanley:/gluster/07/brick \
    pablo:/gluster/08/brick stanley:/gluster/08/brick

The clients mount the volume using the gluster FUSE client, again 
version 3.1.2.  Since GlusterFS doesn't yet support exporting 
sub-directories directly (it does now for NFS, though, I believe), I 
mount the volume as:
     /net/.post-volume
and then bind mount a couple of lower sub-directories as:
     /net/post (bound to /net/.post-volume/home)
     /net/post-scratch (bound to /net/.post-volume/scratch)

I am using this volume for user home directories.

That's the background information... now for the problem.  There are 
certain files that are almost guaranteed to go missing after less than a 
few hours of a user starting up a login session.  We use Ubuntu with GDM 
as a login greeter and both KDE and Gnome desktops.  Here are a few of 
the files that usually go missing:

    ls: .dmrc: No such file or directory
    ls: .pine-debug2: Invalid argument
    ls: .xsession-errors.old: No such file or directory
    ls: .recently-used.xbel: No such file or directory

Taking .dmrc, for example, I can stop the volume, then remove all 
occurrences of this file on all the bricks on both servers.  Then start 
up the volume again, start the user session again, and after a period of 
time (I'm not sure how long), the file comes up missing again.  When the 
file is missing, this is what it looks like on the bricks themselves:

server 1:

    root at stanley:/gluster# ls -l ./07/brick/home/stevew/.dmrc
    ---------T 1 stevew sysmgr 0 2011-01-28 08:24
    ./07/brick/home/stevew/.dmrc
    root at stanley:/gluster# ls -l ./02/brick/home/stevew/.dmrc
    -rw-r--r-- 1 stevew sysmgr 25 2011-01-28 08:25
    ./02/brick/home/stevew/.dmrc

server 2:

    root at pablo:/gluster# ls -l ./07/brick/home/stevew/.dmrc
    ---------T 1 stevew sysmgr 0 2011-01-28 08:24
    ./07/brick/home/stevew/.dmrc
    root at pablo:/gluster# ls -l ./02/brick/home/stevew/.dmrc
    -rw-r--r-- 1 stevew sysmgr 25 2011-01-28 08:25
    ./02/brick/home/stevew/.dmrc


Pertinent log messages are:

server 1:

    net-.post-volume.log:[2011-01-28 08:16:28.899544] W
    [fuse-bridge.c:2432:fuse_xattr_cbk] glusterfs-fuse: 6318974:
    GETXATTR() /home/stevew/.dmrc => -1 (Invalid argument)


server 2:

    net-.post-volume.log:[2011-01-28 08:10:58.74848] W
    [fuse-bridge.c:2432:fuse_xattr_cbk] glusterfs-fuse: 2428788:
    GETXATTR() /home/stevew/.dmrc => -1 (No such file or directory)


Any thoughts or ideas?

Thanks!

Steve
-- 

Steven M. Wilson, Systems and Network Manager
Markey Center for Structural Biology
Purdue University
(765) 496-1946


------------------------------

_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users


End of Gluster-users Digest, Vol 33, Issue 50
*********************************************



The information contained in this email message and its attachments is intended only for the private and confidential use of the recipient(s) named above, unless the sender expressly agrees otherwise. Transmission of email over the Internet is not a secure communications medium. If you are requesting or have requested the transmittal of personal data, as defined in applicable privacy laws by means of email or in an attachment to email, you must select a more secure alternate means of transmittal that supports your obligations to protect such personal data. If the reader of this message is not the intended recipient and/or you have received this email in error, you must take no action based on the information in this email and you are hereby notified that any dissemination, misuse or copying or disclosure of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by email and delete the original message.