Did a ulimit -s unlimited.

Dies the same way when trying to backup the /coyote/dsk3/ fs - Producer
Thread........




Richard Sims <rbs AT BU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/29/2005 01:53 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: [ADSM-L] Large Linux clients






On Mar 29, 2005, at 1:39 PM, Zoltan Forray/AC/VCU wrote:

> Here ya go. Pretty much no limits. I am open to suggestions on values
> to
> change that might help !

I did recommend addressing the Stacksize to try to head off the
defect...

>
> FWIW, this is RH8 as a Beowulf cluster, so NO, I can not upgrade the
> OS.
>
> Also, while on the subject, I read the "requirements" on the 5.3.x
> client,
> that says it has only been tested on RH AS 3. Anyone try the V5.3
> client
> on RH8 ?
>
> [root@coyote root]# ulimit -a
> core file size        (blocks, -c) 0
> data seg size         (kbytes, -d) unlimited
> file size             (blocks, -f) unlimited
> max locked memory     (kbytes, -l) unlimited
> max memory size       (kbytes, -m) unlimited
> open files                    (-n) 1024
> pipe size          (512 bytes, -p) 8
> stack size            (kbytes, -s) 8192
                                      ^^^^
                           That's FAR from unlimited.

> cpu time             (seconds, -t) unlimited
> max user processes            (-u) 4092
> virtual memory        (kbytes, -v) unlimited
>
>
>
> Richard Sims <rbs AT BU DOT EDU>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 03/29/2005 01:11 PM
> Please respond to
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
> To
> ADSM-L AT VM.MARIST DOT EDU
> cc
>
> Subject
> Re: [ADSM-L] Large Linux clients
>
>
>
>
>
>
> On Mar 29, 2005, at 12:37 PM, Zoltan Forray/AC/VCU wrote:
>
>> ...However, then I try to backup the tree at the third-level (e.g.
>> /coyote/dsk3/), the client pretty much siezes immediately and
>> dsmerror.log
>> says "B/A Txn Producer Thread, fatal error, Signal 11".  The server
>> shows
>> the session as "SendW" and nothing going else going on....
>
> Zoltan -
>
> Signal 11 is a segfault - a software failure.
> The client programming has a defect, which may be incited by a problem
> in that area of the file system (so have that investigated). A segfault
> can be induced by memory constraint, which in this context would most
> likely be Unix Resource Limits, so also enter the command 'limit' in
> Linux csh or tcsh and potentially boost the stack size ('unlimit
> stacksize'). This is to say that the client was probably invoked under
> artificially limited environmentals.
>
>     Richard Sims