Joe Landman
2011-Feb-24 00:08 UTC
[Gluster-users] Does anyone see inaccessible files under NFS client for the distributed volumes?
I just opened a bug on this, #2459. I can reproduce it effectively at
will now. This is over a channel bond into a Nortel switch (not sure
which model)
Basic volume:
gluster volume info fusion
Volume Name: fusion
Type: Distribute
Status: Started
Number of Bricks: 6
Transport-type: tcp
Bricks:
Brick1: dv4-1:/data/brick-md1/fusion
Brick2: dv4-2:/data/brick-md1/fusion
Brick3: dv4-3:/data/brick-md1/fusion
Brick4: dv4-1:/data/brick-md2/fusion
Brick5: dv4-2:/data/brick-md2/fusion
Brick6: dv4-3:/data/brick-md2/fusion
Options Reconfigured:
performance.cache-refresh-timeout: 0
performance.stat-prefetch: 0
auth.allow: *
NFS mounts use noac, so there should be no attribute caching.
doing an
cat /x/y/z/*
produces
cat: /x/y/z/a: Input/output error
cat: /x/y/z/b: Input/output error
cat: /x/y/z/c: Input/output error
cat: /x/y/z/d: Input/output error
I have a partial work around, but this one is troublesome. Anyone
experience anything like this? If so, please contact me offline so we
can compare notes.
Regards,
Joe
--
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics Inc.
email: landman at scalableinformatics.com
web : http://scalableinformatics.com
http://scalableinformatics.com/sicluster
phone: +1 734 786 8423 x121
fax : +1 866 888 3112
cell : +1 734 612 4615
Luis
2011-Feb-24 00:48 UTC
[Gluster-users] Does anyone see inaccessible files under NFS client for the distributed volumes?
What type of bond? Joe Landman <landman at scalableinformatics.com> wrote:>I just opened a bug on this, #2459. I can reproduce it effectively at >will now. This is over a channel bond into a Nortel switch (not sure >which model) > >Basic volume: > >gluster volume info fusion > >Volume Name: fusion >Type: Distribute >Status: Started >Number of Bricks: 6 >Transport-type: tcp >Bricks: >Brick1: dv4-1:/data/brick-md1/fusion >Brick2: dv4-2:/data/brick-md1/fusion >Brick3: dv4-3:/data/brick-md1/fusion >Brick4: dv4-1:/data/brick-md2/fusion >Brick5: dv4-2:/data/brick-md2/fusion >Brick6: dv4-3:/data/brick-md2/fusion >Options Reconfigured: >performance.cache-refresh-timeout: 0 >performance.stat-prefetch: 0 >auth.allow: * > > >NFS mounts use noac, so there should be no attribute caching. > >doing an > > cat /x/y/z/* > >produces > > cat: /x/y/z/a: Input/output error > cat: /x/y/z/b: Input/output error > cat: /x/y/z/c: Input/output error > cat: /x/y/z/d: Input/output error > >I have a partial work around, but this one is troublesome. Anyone >experience anything like this? If so, please contact me offline so we >can compare notes. > >Regards, > >Joe > > >-- >Joseph Landman, Ph.D >Founder and CEO >Scalable Informatics Inc. >email: landman at scalableinformatics.com >web : http://scalableinformatics.com > http://scalableinformatics.com/sicluster >phone: +1 734 786 8423 x121 >fax : +1 866 888 3112 >cell : +1 734 612 4615 >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://gluster.org/cgi-bin/mailman/listinfo/gluster-users