Hi all,
I've got question (problem?) regarding samba exporting gpfs filesystem.
My setup is very simple - gpfs client machine with gpfs filesystem
mounted and samba server running on the top of it. I compiled samba with
gpfs support, here is my smb.conf section:
[homes]
comment = Home Directories
browseable = no
writable = yes
fileid:mapping = fsname
use mmap = no
vfs objects = gpfs
gpfs:sharemodes = yes
I can access home dir as user with no single problem, but when it comes
to locking file (for reading it, when client does 'get file', for
example), here is what happens:
smb: \> get opt.err
NT_STATUS_SHARING_VIOLATION opening remote file \opt.err
[2008/04/22 14:49:53, 4] smbd/open.c:open_file_ntcreate(1605)
calling open_file with flags=0x0 flags2=0x0 mode=0744, access_mask =
0x120089, open_access_mask = 0x120089
[2008/04/22 14:49:53, 10] smbd/open.c:fd_open(67)
fd_open: name opt.err, flags = 00 mode = 0744, fd = 26.
[2008/04/22 14:49:53, 2] smbd/open.c:open_file(391)
marcin opened file opt.err read=Yes write=No (numopen=1)
[2008/04/22 14:49:53, 10] locking/posix.c:get_windows_lock_ref_count(545)
get_windows_lock_count for file opt.err = 0
[2008/04/22 14:49:53, 10] locking/posix.c:delete_windows_lock_ref_count(559)
delete_windows_lock_ref_count for file opt.err
[2008/04/22 14:49:53, 5] smbd/files.c:file_free(454)
freed files structure 7191 (0 used)
[2008/04/22 14:49:53, 3] smbd/error.c:error_packet_set(106)
error packet at smbd/reply.c(1458) cmd=45 (SMBopenX)
NT_STATUS_SHARING_VIOLATION
When I disable gpfs support in smb.conf, i.e. when I've got:
[homes]
comment = Home Directories
browseable = no
writable = yes
only there, it works, although, as far as I understand, I'm at risk of
corrupting data. I can't find any extensive materials about that, so I'd
would be very grateful for enlightening me here.
Question - how to set it up? Samba is the latest one (3.0.28a), file
used for transferring is not locked for sure. All directories with no
gpfs config options in smb.conf work right.
Regards,
Marcin Mogielnicki
