[Lustre-discuss] OST acting up

[Mohr Jr, Richard Frank (Rick Mohr)]

On Nov 13, 2014, at 10:49 AM, Ron Croonenberg <ronc at lanl.gov>
 wrote:

> I am using Lustre 2.4.2 and have an OST that doesn't seem to be written to.
> 
> When I check the MDS with 'lctl dl' I do not see that OST in the list.
> However when I check the OSS that OST belongs to I can see it is mounted and up;
> 
>  0 UP osd-zfs l2-OST0003-osd l2-OST0003-osd_UUID 5
>  3 UP obdfilter l2-OST0003 l2-OST0003_UUID 5
>  4 UP lwp l2-MDT0000-lwp-OST0003 l2-MDT0000-lwp-OST0003_UUID 5
> 
> 
> Since it isn't written to (the MDS doesn't seem to know about it, I created a directory. The index of that OST is 3  so I did a "lfs setstripe -i 3 -c 1 /mnt/l2-lustre/test-37" to force stuff that is written in that directory to be written on OST03
> 
> However when I issue that command I get:
> 
> -bash-4.1# lfs setstripe -i 3 -c 1 /mnt/l2-lustre/test-37
> error on ioctl 0x4008669a for '/mnt/l2-lustre/test-37' (3): Invalid argument
> error: setstripe: create stripe file '/mnt/l2-lustre/test-37' failed



Does that OSS server only have one OST?  If so, could there be a communication problem between the MDS server and the OSS server?  Is there anything in the log files that indicates the OSS server is trying to connect to the MDS server but fails for some reason?

-- 
Rick Mohr
Senior HPC System Administrator
National Institute for Computational Sciences
http://www.nics.tennessee.edu