Yes! any crash is treated as bug. But I would like to see the client log file too. The log about extended attribute not supported is due to having filter (which doesn't allow setxattr to succeed). Anyways, it would be great help if you could send the client spec file. Regards, Amar 2008/6/16 Snezhana Bekova <dudo@xxxxxxx>: > > > Hello, > I've started testing glusterfs version 1.4.0qa19. There is problem with > readonly filter. When I try to a make write operation on readonly brick on a > glusterfs client (client side afr), the glustrefs server die. > > This is from the glusterfs client log messages when mounting readonly > volume: > "2008-06-16 17:54:17 C [afr.c:6187:afr_check_xattr_cbk] afr: [CRITICAL]: > 'client-wks1' doesn't support Extended attribute: Read-only file system > 2008-06-16 17:54:17 C [afr.c:6187:afr_check_xattr_cbk] afr: [CRITICAL]: > 'client-wks2' doesn't support Extended attribute: Read-only file system" > > And this is from the glusterfs server log when die: > > Here is a part of the log from glusterfs server that crashed: > "TLA Repo Revision: glusterfs--mainline--3.0--patch-192 > Time : 2008-06-16 17:55:41 > Signal Number : 11 > > /usr/sbin/glusterfsd -f /etc/glusterfs/glusterfs-server.vol -l > /var/log/glusterfs/glusterfsd.log -L > WARNING --pidfile /var/run/glusterfsd.pid > volume server > type protocol/server > option auth.ip.brick-readonly.allow * > option auth.ip.brick-local1.allow * > option auth.ip.brick-local.allow * > option auth.ip.brick-webtmp.allow * > option transport-type tcp > subvolumes brick-local brick-readonly brick-webtmp brick-local1 > end-volume > > volume brick-webtmp > type storage/posix > option directory /var/webtmp > end-volume > > volume brick-readonly > type features/filter > subvolumes brick-local > end-volume > > volume brick-local1 > type storage/posix > option directory /wwwroot/Advert > end-volume > > volume brick-local > type storage/posix > option directory /wwwroot > end-volume > > frame : type(1) op(27) > 2008-06-16 17:55:41 C [common-utils.c:155:gf_print_bytes] : xfer == 27919, > rcvd == 14515[0xffffe420] > > /usr/lib/glusterfs/1.4.0qa19/xlator/features/filter.so(filter_create+0x6c)[0xb7f77f9c] > > /usr/lib/glusterfs/1.4.0qa19/xlator/protocol/server.so(server_create+0x180)[0xb7584440] > > /usr/lib/glusterfs/1.4.0qa19/xlator/protocol/server.so(protocol_server_interpret+0xd6)[0xb7585056] > > /usr/lib/glusterfs/1.4.0qa19/xlator/protocol/server.so(protocol_server_pollin+0xb3)[0xb7585263] > > /usr/lib/glusterfs/1.4.0qa19/xlator/protocol/server.so(notify+0x51)[0xb7585351] > /usr/lib/glusterfs/1.4.0qa19/transport/tcp.so[0xb757c249] > /usr/lib/libglusterfs.so.0[0xb7f6d5c5] > /usr/lib/libglusterfs.so.0(event_dispatch+0x21)[0xb7f6c431] > [glusterfs](main+0x795)[0x804a545] > /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb7e02450] > [glusterfs][0x8049871] > --------- > 2008-06-16 18:13:05 W [glusterfs.c:419:glusterfs_cleanup_and_exit] > glusterfs: shutting down server > 2008-06-16 18:13:05 C [common-utils.c:155:gf_print_bytes] : xfer == 0, rcvd > == 0" > > The underlying file system is ext3 and there is extended attribute support! > The problem not exist on version 1.3.9. > Can you tell me what is wrong? Maybe it is a bug? > > Thanks, > Snezhana > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel > -- Amar Tumballi Gluster/GlusterFS Hacker [bulde on #gluster/irc.gnu.org] http://www.zresearch.com - Commoditizing Super Storage!
