gluster-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gluster-devel] Creating a hard link reports an error in the glusterfsd


From: Kevan Benson
Subject: [Gluster-devel] Creating a hard link reports an error in the glusterfsd log.
Date: Fri, 16 Jan 2009 16:08:40 -0800
User-agent: Thunderbird 2.0.0.19 (X11/20090107)


2009-01-15 12:05:47 E [server-helpers.c:101:server_loc_fill] backuppc: paths differ for inode(25968751): client path = /pc/nfs/350/f%2f/fhome/ftoprank/fbin/fsh. dentry path = /
pc/nfs/350/f%2f/fbin/fsh
2009-01-15 12:05:49 E [server-helpers.c:101:server_loc_fill] backuppc: paths differ for inode(29393217): client path = /pc/nfs/350/f%2f/fvar/flog/frpmpkgs.3. dentry path = /pc/
nfs/350/f%2f/fvar/flog/frpmpkgs
2009-01-15 12:05:49 E [server-helpers.c:101:server_loc_fill] backuppc: paths differ for inode(26283652): client path = /pc/nfs/350/f%2f/fetc/fdev.d/ffd3/attrib. dentry path = /
pc/nfs/350/f%2f/fetc/fdev.d/ffd0/attrib
2009-01-15 12:05:49 E [server-helpers.c:101:server_loc_fill] backuppc: paths differ for inode(29393217): client path = /pc/nfs/350/f%2f/fvar/flog/frpmpkgs.3. dentry path = /pc/
nfs/350/f%2f/fvar/flog/frpmpkgs
2009-01-15 12:05:49 E [server-helpers.c:101:server_loc_fill] backuppc: paths differ for inode(26165446): client path = /pc/nfs/350/f%2f/fetc/fdev.d/ffd3/f10-MAKEDEV.dev. dentry
 path = /pc/nfs/350/f%2f/fetc/fdev.d/ffd0/f10-MAKEDEV.dev
2009-01-15 12:05:49 E [server-helpers.c:101:server_loc_fill] backuppc: paths differ for inode(26283652): client path = /pc/nfs/350/f%2f/fetc/fdev.d/ffd3/attrib. dentry path = /
pc/nfs/350/f%2f/fetc/fdev.d/ffd1/attrib

I'm getting some interesting errors in the glusterfsd log file when hard linking files in some instances. It seems to function fine, but the log reports an error. The files are indeed hard linked, as they are at the same inode.

Sometimes, I can replicate the log messages by creating the link myself with "ln pc/nfs/350/f%2f/fhome/ftoprank/fbin/fsh ./" from within the glusterfs mount point, in other cases I can't (usually after I've reproduced it a few times already for that file though). I'm unable to reproduce it with files I created manually, just the ones BackupPC creates that it already noted problems with in the log file.


--

-Kevan Benson
-A-1 Networks




reply via email to

[Prev in Thread] Current Thread [Next in Thread]