On 2010-03-25, at 06:33, Stephen Willey wrote:
> We're using autofs so the Lustre may be mounted instantly before the
> command using it is run. We believe it may be because the client
> has not yet established connections to all the OSTs when mount
> returns and the following command is run
Christopher J. Morrone wrote:
> Cliff White wrote:
>
>> I don't know what your constraints are, but should note that this sort
>> of information (number of OSTs) can be obtained rather trivially from
>> any lustre client via shell prompt, to wit:
>> # lctl dl |grep OST |wc -l
>> 2
>> or:
>> # ls
Scott Barber wrote:
> Background:
> MDS and OSTs are all running CentOS 5.4 / x86_64 /
> 2.6.18-128.7.1.el5_lustre.1.8.1.1
> 2 types of clients
> - CentOS 5.4 / x86_64 / 2.6.18-128.7.1.el5_lustre.1.8.1.1
> - Ubuntu 8.04.1 / i686 / 2.6.22.19 patchless
>
> A few days ago one of the OSSs hit an LBU
On Mar 25, 2010, at 6:25 PM, Christopher J. Morrone wrote:
> Cliff White wrote:
>
>> I don't know what your constraints are, but should note that this sort
>> of information (number of OSTs) can be obtained rather trivially from
>> any lustre client via shell prompt, to wit:
>> # lctl dl |grep
Cliff White wrote:
> I don't know what your constraints are, but should note that this sort
> of information (number of OSTs) can be obtained rather trivially from
> any lustre client via shell prompt, to wit:
> # lctl dl |grep OST |wc -l
> 2
> or:
> # ls /proc/fs/lustre/osc | grep OST |wc -l
> 2
Background:
MDS and OSTs are all running CentOS 5.4 / x86_64 /
2.6.18-128.7.1.el5_lustre.1.8.1.1
2 types of clients
- CentOS 5.4 / x86_64 / 2.6.18-128.7.1.el5_lustre.1.8.1.1
- Ubuntu 8.04.1 / i686 / 2.6.22.19 patchless
A few days ago one of the OSSs hit an LBUG. The syslog looked like:
http://pa
On 2010-03-22, at 12:39, Wojciech Turek wrote:
> FYI I have working OpenSUSE Lustre patchless client using kernel
> 2.6.31.12-0.1-xen and lustre-1.8.2 source. I used info from bug
> 21500 and
> http://www.mail-archive.com/lustre-discuss@lists.lustre.org/msg05655.html
Note that the 2.6.31 kern
On 2010-03-25, at 15:12, Andreas Dilger wrote:
>> The llapi_* functions are great, I see how to set the stripe count
>> and size. I wasn't sure if there was also a function to query about
>> the configuration, eg number of OST's deployed?
>
> There isn't directly such a function, but indirectly thi
On 2010-03-24, at 18:39, burlen wrote:
> System limits are sometimes provided in a header, I wasn't sure if
> Lustre adopted that approach.
Well, having static limits in a header doesn't help if the limits are
dynamic.
> The llapi_* functions are great, I see how to set the stripe count
> a
On Thu, Mar 25, 2010 at 10:07:03AM -0700, burlen wrote:
> > I don't know what your constraints are, but should note that this sort
> > of information (number of OSTs) can be obtained rather trivially from
> > any lustre client via shell prompt, to wit:
> True, but parsing the output of a c "syste
> I don't know what your constraints are, but should note that this sort
> of information (number of OSTs) can be obtained rather trivially from
> any lustre client via shell prompt, to wit:
True, but parsing the output of a c "system" call is something I hoped
to avoid. It might not be portable
We're seeing errors which we believe are down to automount returning too early
from a Lustre mount.
We're using autofs so the Lustre may be mounted instantly before the command
using it is run. We believe it may be because the client has not yet
established connections to all the OSTs when mou
On Wed, 2010-03-24 at 18:45 -0400, Joe Landman wrote:
>
> This seems to have worked on an unpatched kernel. Thanks. I presume we
> need the OFED 1.4.2 stack installed before for o2ib kernel build?
Specifically, you need kernel-ib-devel or it's equivalent -- that is,
the OFED kernel headers.
burlen wrote:
> System limits are sometimes provided in a header, I wasn't sure if
> Lustre adopted that approach. The llapi_* functions are great, I see how
> to set the stripe count and size. I wasn't sure if there was also a
> function to query about the configuration, eg number of OST's depl
14 matches
Mail list logo
