search for: localflocks

Are their issues with Samba and Lustre working together? I remember something about turning oplocks off in samba, and while testing samba I noticed this [2010/08/27 17:30:59, 3] lib/util.c:fcntl_getlock(2064) fcntl_getlock: lock request failed at offset 75694080 count 65536 type 1 (Function not implemented) But I also found out about the flock option for lustre. Should I set flock on all

...he application servers have 128GB of memory. I created my OCFS2 filesystems as follows: mkfs.ocfs2 ?T mail ?b 4k ?C 4k ?L <my label> --fs-features=indexed-dirs ?fs-feature-level=max-features /dev/mapper/<my device> And I mount them with these options: _netdev,commit=30,noatime,localflocks,localalloc=32 So my questions are these: 1) Given a billion files sized 2KB ? 50KB, with 50% under 8KB, do I have the optimal OCFS2 filesystem and mount-point configurations? 2) Should I split the files across even more filesystems? Currently I have them split across 16 OCFS2 filesystems....

...locks/sec The cluster config has been updated with: <dlm plock_ownership="1" plock_rate_limit="0"/> <gfs_controld plock_rate_limit="0"/> gfs2_tool getargs /mnt/backup statfs_percent 0 data 2 suiddir 0 quota 0 posix_acl 0 upgrade 0 debug 0 localflocks 0 localcaching 0 ignore_local_fs 0 spectator 0 hostdata jid=1:id=2752514:first=0 locktable lockproto gfs2_tool df -H /mnt/backup: SB lock proto = "lock_dlm" SB lock table = "cybercenter:backup" SB ondisk format = 1801 SB multihost format = 1900 Block size = 4096 Jou...

Dear All, I try to use our cluster though samba share. Everything work fine, but I think, we should have -o flock at lustre mount time. Great, it''s work. But when I want to save a file on the share, I get this on the logs: Jan 31 10:45:24 opteron-ren-11 kernel: LustreError: 24836:0:(file.c:2309:ll_file_flock()) unknown fcntl lock type: 32 Jan 31 10:45:24 opteron-ren-11 kernel:

ocfs2 currently uses the Journaled Block Device (JBD) for its journaling. This is a very stable and tested codebase. However, JBD is limited by architecture to 32bit block numbers. This means an ocfs2 filesystem is limited to 2^32 blocks. With a 4K blocksize, that's 16TB. People want larger volumes. Fortunately, there is now JBD2. JBD2 adds 64bit block number support and some other

The following series of patches comprises the bulk of our outstanding changes for Ocfs2. Aside from the usual set of cleanups and fixes that were inappropriate for 2.6.25, there are a few highlights: The '/sys/o2cb' directory has been moved to '/sys/fs/o2cb'. The new location meshes better with modern sysfs layout. A symbolic link has been placed in the old location so as to