Re: [Condor-users] Warnings in 7.4.2 not seen in version 7.2.x

[Matthew Farrellee <matt@xxxxxxxxxx>]

You may need "echo -e", there should be a "queue" in the output.

Best,


matt

On 07/20/2010 08:07 AM, James Osborne wrote:
> Dear Matt
> 
> Thanks for picking this up...
> 
>>
>> It looks like there's no param to quiet that warning.
>>
>>    http://condor-git.cs.wisc.edu/?p=condor.git;a=blob;f=src/
>> condor_submit.V6/
>> submit.cpp;h=857b53fb4e14a59635ff213eaef81be17720ccc2;hb=refs/heads/
>> V7_4-branch#l4620
>>
>> You should only be getting that warning if the statfs or statvfs 
>> calls are failing.
>>
>> Will you first check and see if debug output says anything about 
>> "detect_nfs", e.g. "statfs(/home/username/SWUS/job-log.txt) failed: 
> ???/???"?
> 
> as root, I compiled stat.c to a.out
> 
> # ./a.out /home/uername/SWUS/job-log.txt
> f_type(/home/username/SWUS/job-log.txt) = 0x6969
> # man 2 statfs | grep 0x6969
> NFS_SUPER_MAGIC       0x6969
> 
>>
>>    http://condor-git.cs.wisc.edu/?p=condor.git;a=blob;f=src/
>> condor_util_lib/
>> fs_util.c;h=509520e2da1e364c7fde92a78fa0e59bdb06b72c;hb=refs/heads/
>> V7_4-branch#l158
>>
>> Try: echo "cmd=/bin/true\nlog=/home/username/SWUS/job-log.txt
>> \nqueue" | _CONDOR_TOOL_DEBUG=D_ALWAYS condor_submit -debug -dump 
> /dev/null
> 
> as me I copied the user's file into my home directory and ran
> 
> # echo "cmd=/bin/true\nlog=/home/me/job-log.txt\nqueue" | 
> _CONDOR_TOOL_DEBUG=D_ALWAYS condor_submit -debug -dump /dev/null
> 
> Storing job ClassAd(s)
> ERROR: "(stdin)" doesn't contain any "queue" commands -- no jobs queued
> 
> Is something missing from that command ?
> 
>>
>> If the debug output doesn't do the trick, will you include 
>> information about what binaries you are using, 
> 
> # condor_version
> $CondorVersion: 7.4.2 Mar 29 2010 BuildID: 227044 $
> $CondorPlatform: I386-LINUX_RHEL5 $
> 
>> on which platforms, 
> 
> 64-bit version of CentOS 5.4 as a virtual machine running on VMware ESX 
> 4.0 at latest patch level.  VM has 4gb of RAM assigned and is limited to 1 
> core of an Intel E5472 processor.  Previous version was on the same 
> virtual machine running CondorVersion 7.2.4
> 
>> and maybe information of what statfs returns when pointed at /home/
>> username/SWUS? 
> 
> # ./a.out /home/username/SWUS
> f_type(/home/username/SWUS) = 0x6969
> 
> As far as I recall the 17TB /home storage array (shared with a parallel 
> cluster) is based on XFS, however for a definitive answer I would have to 
> defer to our sysadmin who is currently on leave.
> 
>> See the statfs.c below. Seems like it would be useful
>> to ship a diagnostic tool to gather such information. I wonder if 
>> the VDT has one.
>>
>> Best,
>>
>>
>> matt
>>
>> $ cat statfs.c
>> #include <stdio.h>
>> #include <sys/vfs.h>
>>
>> int
>> main(int argc, char **argv)
>> {
>>    struct statfs buf;
>>    if (statfs(argv[1], &buf)) {
>>       perror("statfs");
>>       return 1;
>>    }
>>
>>    printf("f_type(%s) = 0x%X\n", argv[1], buf.f_type);
>>    return 0;
>> }
>> $ gcc statfs.c 
>> $ ./a.out /tmp
>> f_type(/tmp) = 0xEF53
>> $ man 2 statfs | grep 0xEF53
>>               EXT2_SUPER_MAGIC      0xEF53
>>               EXT3_SUPER_MAGIC      0xEF53
>