OT:
Can we create a wiki page or some other form of knowledge pooling on
benchmarking lustre?
Right now I'm using slides from 2009 as my source which may not be ideal...
http://wiki.lustre.org/images/4/40/Wednesday_shpc-2009-benchmarking.pdf
OT2:
Did I miss the release announcement or was 2.10 n
I do apologize. This was my error – I seem to have sent it to lustre-devel
twice when I intended to send it to both lustre-devel and lustre-discuss.
On 8/7/17, 5:56 AM, "lustre-discuss on behalf of E.S. Rosenberg"
mailto:lustre-discuss-boun...@lists.lustre.org>
on behalf of esr+lus...@mail.hebr
Hey all,
I am looking to upgrade from lustre 2.8 to 2.10. I see that
there are no pre-built RPMs for 2.10 on RHEL6.x families.
Did I miss them, or will I need to build from source (or
upgrade to Centos 7)?
Thanks much!
Best,
---Steve
___
lustre-d
If I'm not mistaken they haven't provided RPMs for RHEL6.x since 2.9...
HTH,
Eli
On Mon, Aug 7, 2017 at 4:33 PM, Steve Barnet
wrote:
> Hey all,
>
> I am looking to upgrade from lustre 2.8 to 2.10. I see that
> there are no pre-built RPMs for 2.10 on RHEL6.x families.
>
> Did I miss them, or wi
Hello,
We've upgraded to 2.10 and I've been playing with progressive file layouts. To
begin, I'm just setting a test directory to use the following PFL.
lfs setstripe \
-E 4M -c 1 -S 1M -i -1 \
-E 256M -c 4 -S 1M -i -1 \
-E -1 -c 8 -S 4M -i -1 .
I then created some files in the
Correct – RHEL 6.x support appeared for the last time in the community 2.8
release. However, there has been some interest in seeing some kind of support
for RHEL 6.x in the 2.10 LTS releases so I think it likely that at least
support for clients will be reintroduced in a future 2.10.x maintenanc
We created a test system that was installed with CentOS 6.x and Lustre 2.8
filled with some data and subsequently reinstalled with CentOS 7.x and
Lustre 2.9
Everything seems to have gone fine but I am actually curious if anyone else
did this pretty invasive upgrade? (Hoping to upgrade in the not-t
I'm going to be testing an upgrade of a filled 2.9/0.6.5.7/CentOS6.x LFS to
2.10/0.7/CentOS6.9. I will report back results to the mailing list when it
is completed.
--Jeff
On Mon, Aug 7, 2017 at 06:50 E.S. Rosenberg
wrote:
> We created a test system that was installed with CentOS 6.x and Lustre
There were actually several:
On an OSS:
[447314.138709] BUG: unable to handle kernel NULL pointer dereference at
0020
[543262.189674] BUG: unable to handle kernel NULL pointer dereference
at (null)
[16397.115830] BUG: unable to handle kernel NULL pointer dereference
at
Perhaps this is the same as LU-9825?
On 8/7/17, 6:42 AM, "lustre-discuss on behalf of Vicker, Darby (JSC-EG311)"
wrote:
>Hello,
>
>We've upgraded to 2.10 and I've been playing with progressive file layouts.
>To begin, I'm just setting a test directory to use the following PFL.
>
>lfs se
Lustre wiki has sidebars on Testing and Monitoring, you may start Benchmarking.
there was Benchmarking Group in OpenSFS.
wiki: http://wiki.opensfs.org/Benchmarking_Working_Group
mail list: http://lists.opensfs.org/listinfo.cgi/openbenchmark-opensfs.org
It is actually question to the list what is
Hello,
I have a new Lustre cluster based on Lustre 2.10.0/ZFS 0.7.0 on Centos 7.3
Lustre FS creation went smooth.
When I tryed then to mount from the clients, Lustre is not able to mount
any of the OSTs.
It stops at MGS/MDT level.
this is from the client side:
mount.lustre: mount 192.168..48.254
trying to debug more this problem looks like tcp port 9888 is closed on
the MDS.
this is weird. lnet module is running. There is no firewall and OSSs and
MDS are on the same subnet.
but I Cannot connect to port 9888.
There is anything which changed in Lustre 2.10.0 related to lnet and TCP
ports tha
Lustre file system names cannot exceed 8 characters in length, but “scratch12”
is 9 characters. Try changing the fsname to a smaller string. You can do this
with tunefs.lustre on all the storage targets, but I can’t remember if you need
to use --erase-params and recreate all the options. Alterna
I’ve created a Benchmarking process outline and tools overview here:
http://wiki.lustre.org/Category:Benchmarking
This has been recently updated and is based on notes I’ve maintained at Intel
over the years.
Malcolm Cowe
High Performance Data Division
Intel Corporation | www.intel.com
From:
thanks, yes I noticed that Issued and I changed hte name. I Also rebuild
the FS but now it does not work for another unknown reason:
Aug 7 19:05:38 psana1510 kernel: [289134.511260] Lustre:
:0:(client.c:2114:ptlrpc_expire_one_request()) @@@ Request sent has
failed due to network error: [sent
it is like if my /etc/modprobe.d/lustre.conf gets completely ignored
when lnet module is loaded
On 8/7/17 7:05 PM, Cowe, Malcolm J wrote:
> Lustre file system names cannot exceed 8 characters in length, but
> “scratch12” is 9 characters. Try changing the fsname to a smaller string. You
> can do
I figure out the problem was a wrong setting client side.
On 8/7/17 8:09 PM, Riccardo Veraldi wrote:
> it is like if my /etc/modprobe.d/lustre.conf gets completely ignored
> when lnet module is loaded
>
> On 8/7/17 7:05 PM, Cowe, Malcolm J wrote:
>> Lustre file system names cannot exceed 8 charact
Had another where the client rebooted.
Here is the full dmesg from that:
/*[181902.731655] BUG: unable to handle kernel NULL pointer
dereference at (null)*//*
*//*[181902.731710] IP: []
_raw_spin_unlock+0xa/0x30*//*
*//*[181902.731749] PGD 0*//*
*//*[181902.731766] O
19 matches
Mail list logo
