Hi,
I would just like to point out to
http://www.ntfs-3g.org/pjd-fstest.html which includes a very nice
posix test suite. Settings the filesystem to ntfs-3g in the
configuration file should make glusterfs pass all tests (at least
using the stable release of pjd).
If this is not already used in
2009/2/25 Filipe Maia fil...@xray.bmc.uu.se:
Hi,
I would just like to point out to
http://www.ntfs-3g.org/pjd-fstest.html which includes a very nice
posix test suite. Settings the filesystem to ntfs-3g in the
configuration file should make glusterfs pass all tests (at least
using the stable
Krishna,
After moving server and client to a different processes, bug went away.
Production servers worked for 2 weeks with no errors.
Thank you, very much for your help.
BUT :) we found another bug, it looks like previous but not so simple in
understanding. We found some strange bug in our
The first access bug appears to still be occuring with 2.0.0rc2. The FS
is inaccessible on first access, if performed quickly after mounting (e.g.
when shell scripted).
Specifically, in the case of GlusterFS OSR, the init script mounts gluster
to /mnt/newroot, and then tries to bind mount
After upgrading to rc2, I'm getting unify errors for a lot of files. If I
try to read one of these files, I get an I/O error. Here are the
corresponding lines from gluster log:
2009-02-25 13:42:49 E [unify.c:1239:unify_open] unify:
/bio/db/blast/blastp-nr_v9/blastp-nr.19.pni: entry_count is 1
Upon further examination, it looks like maybe unify is expecting that .pni
file to be handled by stripe, as according to the error message, it's
expecting to find the file on more than 1 server. It's supposed to be
handled by dht though, and I've verified that this file exists on just one
server,
Further information- I can't find any rhyme or reason as to why some files
have this problems and others don't. It's not every file on dht or every
file on stripe I don't think I've found any broken files on stripe,
everything that's broken is on dht, but not every dht file is broken.
Please
Dan, can you check if the filename length of those files (just the file
name, not whole path) is 16 or multiple of 16??
Regards,
Amar
2009/2/25 Dan Parsons dpars...@nyip.net
Further information- I can't find any rhyme or reason as to why some files
have this problems and others don't. It's
Yes, all the filenames that don't work are exactly 16 characters long. Does
this mean there's an easy fix? :)
Dan
On Wed, Feb 25, 2009 at 2:07 PM, Amar Tumballi (bulde) a...@gluster.comwrote:
Dan, can you check if the filename length of those files (just the file
name, not whole path) is 16
Avati should be having more idea about this. But if you need this to work
right away, and not harm production, you can revertback to rc1, or add
'option lookup-unhashed yes' in dht volume
On Feb 25, 2009 2:12 PM, Dan Parsons dpars...@nyip.net wrote:
Yes, all the filenames that don't work are
On Fri, Feb 13, 2009 at 6:13 PM, Gordan Bobic gor...@bobich.net wrote:
This doesn't look too good...
Unable to handle kernel paging request at 85f2d790 RIP:
[88b20780] :fuse:fuse_request_init+0x14/0x38
PGD 4b082067 PUD 0
Oops: 0002 [1] SMP
CPU 3
Have you tried the non glfs
11 matches
Mail list logo