, is this reproducible? Could you reproduce it on a machine
for which you could share the dump? Or perhaps tell me how you reproduced
it? To answer your question: yes, further analysis is needed. ;)
- Bryan
On Tue, Dec 16, 2014 at 3:10 PM, Youzhong Yang via smartos-discuss
smartos
Hello again,
I tried to test samba with inotify under relatively heavy load, it panicked
the machine.
Does the stack give a hint about what's going wrong? I have the crash dump
but I cannot upload it since it may contain some production data. If
further analysis is needed, please advise.
, is this reproducible? Could you reproduce it on a machine
for which you could share the dump? Or perhaps tell me how you reproduced
it? To answer your question: yes, further analysis is needed. ;)
- Bryan
On Tue, Dec 16, 2014 at 3:10 PM, Youzhong Yang via smartos-discuss
smartos
...
- Bryan
On Wed, Dec 10, 2014 at 8:00 AM, Youzhong Yang via smartos-discuss
smartos-discuss@lists.smartos.org wrote:
Hello again,
I downloaded smartos latest image (joyent_20141127T173954Z) and tested
inotify using it.
Two issues were observed:
1. ioctl(fd, FIONREAD
Hello again,
I downloaded smartos latest image (joyent_20141127T173954Z) and tested
inotify using it.
Two issues were observed:
1. ioctl(fd, FIONREAD, ...) does not work as expected. It does not return
the number of bytes that are available to be read on an inotify instance.
2. In an OS zone,
in in the specified argument. I'll
get that fixed today...
- Bryan
On Wed, Dec 10, 2014 at 8:00 AM, Youzhong Yang via smartos-discuss
smartos-discuss@lists.smartos.org wrote:
Hello again,
I downloaded smartos latest image (joyent_20141127T173954Z) and tested
inotify using it.
Two
, Dec 10, 2014 at 8:00 AM, Youzhong Yang via smartos-discuss
smartos-discuss@lists.smartos.org wrote:
Hello again,
I downloaded smartos latest image (joyent_20141127T173954Z) and tested
inotify using it.
Two issues were observed:
1. ioctl(fd, FIONREAD, ...) does not work as expected. It does
Yeah, that's what I need. Thanks Robert.
On Tue, Dec 9, 2014 at 11:04 AM, Robert Mustacchi r...@joyent.com wrote:
On 12/9/14 8:02 , Youzhong Yang via smartos-discuss wrote:
Hi All,
I cherry-picked this cool inotify implementation (
https://github.com/joyent/illumos-joyent/commit
commits/changes do not
introduce any issues.
Thanks Keith.
On Tue, Dec 9, 2014 at 11:06 AM, Keith Wesolowski
keith.wesolow...@joyent.com wrote:
On Tue, Dec 09, 2014 at 11:02:03AM -0500, Youzhong Yang via
smartos-discuss wrote:
I cherry-picked this cool inotify implementation (
https
Hi Marcel,
I really appreciate your input. We will try to find out what is wrong in
connmgr_get() which caused port leaking.
In the meantime, we want to change clnt_cots_do_bindresvport from 1 to 0
through mdb so that new connection will start using non-reserved port,
Hello,
We are having a very strange issue on one of servers. The issue is that
fcntl locking over NFS returns 'no locks available' immediately.
dtrace shows that bindresvport() returns error code 125 (EADDRINUSE):
# dtrace -n 'fbt:rpcmod:bindresvport:return /arg1 != 0/ {stack();
printf(ret =
On Wed, Jul 30, 2014 at 2:08 PM, Youzhong Yang via smartos-discuss
smartos-discuss@lists.smartos.org wrote:
Hi All,
The man page of epoll_ctl says:
The data field specifies the datum to be associated with the
event and will be returned via epoll_wait(3C). The events field
4
I certainly don't doubt that there's a bug here -- I just don't think
it's quite as broad as you're implying; could you point me to the core file
for Samba and/or instructions as to how to reproduce the issue?
- Bryan
On Wed, Jul 30, 2014 at 2:08 PM, Youzhong Yang via smartos
, Youzhong Yang via smartos-discuss
smartos-discuss@lists.smartos.org wrote:
Hi All,
The man page of epoll_ctl says:
The data field specifies the datum to be associated with the
event and will be returned via epoll_wait(3C). The events field
denotes both the desired
Hi All,
The man page of epoll_ctl says:
The data field specifies the datum to be associated with the
event and will be returned via epoll_wait(3C). The events field
denotes both the desired events (when specified via epoll_ctl())
and the events that have
Hi All,
We have problem using the LSI 3108 card, just wondering if anyone here has
any success story using this card in production.
Here is the FM version info and error we got in /var/adm/messages:
BIOS Version : 6.13.00_4.14.05.00_0x06010600
Ctrl-R Version : 5.01-0004
FW Version
Thanks Dan.
We ordered these Supermicro X9DRW-CF/CTF boxes which have ROMB LSI 3108 on
the motherboard and got stuck. We will probably add 9211-8i HBA cards to
the machines and get them move forward.
Thanks,
Youzhong
On Thu, Jul 17, 2014 at 11:15 AM, Dan McDonald dan...@omniti.com wrote:
Wesolowski
keith.wesolow...@joyent.com wrote:
On Thu, Jul 17, 2014 at 11:59:16AM -0400, Youzhong Yang via
smartos-discuss wrote:
We ordered these Supermicro X9DRW-CF/CTF boxes which have ROMB LSI 3108
on
the motherboard and got stuck. We will probably add 9211-8i HBA cards to
the machines
Thanks for helping us solve this issue.
In our use case, we need the NULL_RPC timeout to be at least lower than the
client LOCK request timeout…otherwise our client Mac processes stall/fail
–that’s the real pain point we need to solve.
We don’t see any use that in which the illumos server
Hi All,
On one of our servers running SmartOS, the 'iostat' hung and there're a
bunch of stuck 'iostat' commands.
It seems everyone of them has the same kernel stack:
stack pointer for thread ffbe78d0f3a0: ff0173d84380
[ ff0173d84380 _resume_from_idle+0xf4() ]
ff0173d843b0
20 matches
Mail list logo
