unionfs a little improvement

2010-08-18 Thread Daichi GOTO
erated by VOP_WHITEOUT(). It looks like reasonable and patch is simple and effective I guess. If you unionfs guys or fs guys have some ideas around this patch, please teach me. After some tests and a couple of weeks after, I'll commit ed's patch if there is no objections. --

unionfs a little improvement

2010-08-18 Thread Daichi GOTO
erated by VOP_WHITEOUT(). It looks like reasonable and patch is simple and effective I guess. If you unionfs guys or fs guys have some ideas around this patch, please teach me. After some tests and a couple of weeks after, I'll commit ed's patch if there is no objections. -

fcntl always fails to delete lock file, and PID is always -6464

2010-10-03 Thread Daichi GOTO
.ongs.co.jp 9.0-CURRENT FreeBSD 9.0-CURRENT #6 r213257: Thu Sep 30 10:30:06 JST 2010 r...@parancell.ongs.co.jp:/usr/obj/usr/src/sys/PARANCELL amd64 % My home directory on NFS server. Does anyone have any ideas? -- Daichi GOTO CEO | ONGS Inc. 81-42-316-7945 | dai...@ongs.co.jp | http:/

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-04 Thread Daichi GOTO
On Sun, 3 Oct 2010 22:05:12 -0700 Garrett Cooper wrote: > On Sun, Oct 3, 2010 at 8:37 PM, Daichi GOTO wrote: > > It looks very strange. fcntl() always fails to delete lock file > > and command.l_pid is always -6464. This issue is disclosed in > > porting Google's Ja

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-04 Thread Daichi GOTO
On Mon, 4 Oct 2010 07:19:45 -0700 Garrett Cooper wrote: > >> issues that might be occurring with the software, as per my copy of > >> SUSv4 (see the ERRORS section of fcntl). I would print out the > >> strerror for that case. > >>     Providing a backtrace of the application's execution and the >

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-04 Thread Daichi GOTO
/tmp | grep journal flags soft-updates+journal % And working scene: Windows 2: % chmod u+w /tmp/lockfile % ls -l /tmp/lockfile -rwsr-x--- 1 daichi wheel 0 10月 5 15:22 /tmp/lockfile % ./test_fcntl My pid: 43646 test_fcntl: fcntl[1]: Resource temporarily unavailable PID=43490 has the loc

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-04 Thread Daichi GOTO
stem will have a system ID of > zero. <<< After a successful F_GETLK request, the value of l_whence is > SEEK_SET. > > Thus, after fixing the test app I'm getting a sensical value: -- Daichi GOTO 81-42-316-7945 | dai.

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-05 Thread Daichi GOTO
On Tue, 5 Oct 2010 01:23:02 -0700 Garrett Cooper wrote: > 2010/10/4 Daichi GOTO : > > Thanks nice test tool :)  And at last I got it excepting one mystery! > > > > On Mon, 4 Oct 2010 20:17:08 -0700 > > Garrett Cooper wrote: > >> Following through the same proc

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-07 Thread Daichi GOTO
On Oct 5, 2010, at 4:52 PM, Garrett Cooper wrote: > On Tue, Oct 5, 2010 at 1:55 AM, Daichi GOTO wrote: >> On Tue, 5 Oct 2010 01:23:02 -0700 >> Garrett Cooper wrote: >>> 2010/10/4 Daichi GOTO : >>>> Thanks nice test tool :) And at last I got it excepting o

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-07 Thread Daichi GOTO
On Oct 5, 2010, at 7:09 PM, Garrett Cooper wrote: > On Tue, Oct 5, 2010 at 8:58 AM, Garrett Cooper wrote: >> On Tue, Oct 5, 2010 at 7:52 AM, Garrett Cooper wrote: >>> On Tue, Oct 5, 2010 at 1:55 AM, Daichi GOTO wrote: >>>> On Tue, 5 Oct 2010 01:23:02 -0700 >>

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-11 Thread Daichi GOTO
Sent from my iPad On Oct 11, 2010, at 5:50 PM, John Baldwin wrote: > On Tuesday, October 05, 2010 2:39:26 am Daichi GOTO wrote: >> Next step discussion engaged from this research I guess. >> >> Should we do change FreeBSD's fcntl(2) to return correct l_pid >&g

Mellanox Technologies : ConnectX-3 VPI

2012-08-27 Thread Daichi GOTO
I am wondering if FreeBSD 10-CURRNET could use Mellanox Technologies's ConnectX-3 VPI infiniband devices. Is there anyone who are using ConnectX-3 VPI with FreeBSD? -- Daichi GOTO (daichi) FreeBSD Committer, http://www.FreeBSD.org The Power To

Re: (unionfs) panic: excl->share with r230341 and above

2012-04-08 Thread Daichi GOTO
e from LK_EXCLUSIVE to LK_SHARED > in sys/kern/kern_exec.c, executables on union filesystems no > longer cause a panic. > > ...keith > > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/ma

Re: DTrace on FreeBSD

2012-04-09 Thread Daichi GOTO
mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Daichi GOTO (daichi) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve __

Re: (unionfs) panic: excl->share with r230341 and above

2012-04-09 Thread Daichi GOTO
interlock) r = 0 > >> (0xc57cec28) locked @ > >> /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1835 > >> shared lockmgr ufs (ufs) r = 0 (0xc57cec08) locked @ > >> /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843 > >

Re: DTrace on FreeBSD

2012-04-10 Thread Daichi GOTO
On Tue, 10 Apr 2012 23:14:07 +0100 Sevan / Venture37 wrote: > On 10/04/2012 02:45, Daichi GOTO wrote: > > Hi, > > > > From the DTrace tutorial at AsiaBSDCon 2012, it is a CDDL > > license issue. > > Hi Daichi, > I wonder which clause/aspect of the license is

RFC: unionfs multiple mounts, cross mounts and recursive mounts limits and manegement feature

2011-04-20 Thread Daichi GOTO
new patches are always welcome. I'm considering to get merged into current if there are no issues and problems. -- Daichi GOTO ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, se

Re: RFC: unionfs multiple mounts, cross mounts and recursive mounts limits and manegement feature

2011-04-21 Thread Daichi GOTO
On Thu, 21 Apr 2011 11:03:30 +0400 Alex Zimnitsky wrote: > On Thu, 2011-04-21 at 14:49 +0900, Daichi GOTO wrote: > > > It is adjustable with sysctl value 'vfs.unionfs.recursive_limit' as > > multiple mounts limits. The default value is 1 and it means two-

[Call for Test] unionfs intermediate umount feature

2011-05-10 Thread Daichi GOTO
Hi unionfs users ;) We have developed new unionfs feature, "intermediate umount". You can do like this: # mount_unionfs /test2 /test1 # mount_unionfs /test3 /test1 # df :/test2 x x x xx% /test1 :/test3 x x x xx% /test1 # umount ':/test2' # df :/test3

Re: top -n -o res shows empty output

2018-07-18 Thread Daichi GOTO
sts.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Daichi GOTO CEO | ONGS Inc. 81-42-316-7945 | dai...@ongs.co.jp | http://www.ongs.co.jp LinkedIn: http://linkedin.com/in/daichigoto __