Re: [lustre-discuss] Lustre HSM tool - Lemur

[Indivar Nair]

Thanks, Peter.
Will check the presentation  out.

Regards,


Indivar Nair

On Tue, Jan 23, 2018 at 10:33 PM, Jones, Peter A 
wrote:

> There was a LUG presentation about using it in production -
> http://cdn.opensfs.org/wp-content/uploads/2017/06/
> Thur10-Raso-Barnett-Hammond-LUG2017.pdf - but I have not heard of anyone
> actively doing further development in recent months. However, it is open
> source so it is quite possible that there are people who have done so
> without discussing that work on the mailing lists.
>
> On 2018-01-23, 6:20 AM, "lustre-discuss on behalf of Indivar Nair" <
> lustre-discuss-boun...@lists.lustre.org on behalf of
> indivar.n...@techterra.in> wrote:
>
> Hi ...,
>
> Is Lustre HSM tool - Lemur - Production ready?
> And is the project still alive?
> There has been no commits for the last 10 Months.
> https://github.com/intel-hpdd/lemur
>
> Regards,
>
>
> Indivar Nair
>
>
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Re: [lustre-discuss] Moving MGT to new host

[Michael Watters]

The issue is I don't want to change the NID, I want to *move* the NID
from one server to another along with the IP address. 


On 01/19/2018 04:53 PM, Dilger, Andreas wrote:
> On Jan 18, 2018, at 09:00, Michael Watters  wrote:
>> What is the proper way to move an MGT from one server to another?  I
>> tried moving the disk between VMs and remounting it however the NID for
>> the target never comes up.  Is there a way to add a new NID using a
>> secondary IP with lnetctl?  I don't see a command to do so listed in the
>> man page.
> There is "lctl replace_nids"?
>
> The manual also mentions:
>
> 38.18.4. Examples
>
> Change the MGS's NID address. (This should be done on each target disk,
> since they should all contact the same MGS.)
>
> tunefs.lustre --erase-param --mgsnode= --writeconf /dev/sda
>
> Cheers, Andreas
> --
> Andreas Dilger
> Lustre Principal Architect
> Intel Corporation
>
>
>
>
>
>
>

___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Re: [lustre-discuss] undelete

[E.S. Rosenberg]

Hi everyone,
A small progress report.
I played around with extundelete and ext3grep on a test system, neither was
successful and I think this is due to the fact that they don't support
xattrs.

Autopsy as mentioned shows me the filetree on the MDS but it doesn't show
me the lustre relevant metadata and searching the files blindly on multiple
OSTs is definitely not an option.

Is there any tool to show me the lustre relevant metadata?
Thanks,
Eli

On Tue, Jan 23, 2018 at 4:03 AM, E.S. Rosenberg 
wrote:

> Dragging the old discussion back up
> First of thanks for all the replies last time!
>
> Last time in the end we didn't need to recover but now another user made a
> bigger mistake and we do need to recover data.
> I have shut down our Lustre filesystem and am going to do some simulations
> on a test system trying various undelete tools.
>
> autopsy (sleuthkit) on the metadata shows that at least the structure is
> still there and hopefully we'll be able to recover more.
>
> Has anyone ever done true recovery of Lustre or is it all just theoretical
> knowledge at the moment?
>
> What are the consequences of say undeleting data on OSTs that is then not
> referenced on the MDS? Could I cause corruption of the whole filesystem by
> doing stuff like that?
> (As far as the files themselves go they are most likely all single striped
> since that is our default and we are pre PFL so that should be easier I
> think).
> Thanks,
> Eli
>
>
> On Thu, May 4, 2017 at 2:21 AM, Dilger, Andreas 
> wrote:
>
>> On Apr 27, 2017, at 05:43, E.S. Rosenberg 
>> wrote:
>> >
>> > A user just rm'd a big archive of theirs on lustre, any way to recover
>> it before it gets destroyed by other writes?
>>
>> Just noticed this email.
>>
>> In some cases, an immediate power-off followed by some ext4 recovery
>> tools (e.g. ext3grep) might get you some data back, but that is very
>> uncertain.
>>
>> With ZFS MDT/OST filesystems (or to a lesser extent LVM) it is possible
>> to create periodic snapshots of the filesystems for recovery purposes.  ZFS
>> handles this fairly well performance wise, LVM much less so.  With Lustre
>> 2.10 there are new tools to manage the ZFS snapshots and allow mounting
>> them as a separate Lustre filesystem.
>>
>> Cheers, Andreas
>> --
>> Andreas Dilger
>> Lustre Principal Architect
>> Intel Corporation
>>
>>
>>
>>
>>
>>
>>
>>
>
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Re: [lustre-discuss] Recompiling client from the source doesnot contain lnetctl

[E.S. Rosenberg]

Slightly OT:
As mentioned in the mail I sent today liblnetconfig.so.2.0.0 is missing
from the debs available on
https://downloads.hpdd.intel.com/public/lustre/lustre-2.10.2/ubuntu1604/client/

Regards,
Eli

On Tue, Jan 23, 2018 at 8:35 PM, Alexander I Kulyavtsev 
wrote:

> Andreas,
> It will be extremely helpful to have "rpmbuild --rebuild" to build lustre
> [client] rpm with the same content and functionality as lustre[-client] rpm
> from distro.
> The client rpm is rebuild most often for different kinds of worker nodes
> and I see several mails on this list reporting lnetctl is not there.
>
> enable-dlc/disable-dlc flag is not described in manual or lustre wiki (
> http://wiki.lustre.org/Compiling_Lustre) .
>
> Arman,
> for the record:
> To get lnetctl into the client rpm on slf6.8 I was need to use flags:
> rpmbuild  --rebuild --without servers --with lnet-dlc --with
> lustre-utils ./lustre-2.10.2-1.src.rpm
>
> This adds files below to lustre-client-*.rpm wrt build without these flags:
> > /etc/lnet.conf
> > /usr/lib64/liblnetconfig.a
> > /usr/lib64/liblnetconfig.so
> > /usr/lib64/liblnetconfig.so.2
> > /usr/lib64/liblnetconfig.so.2.0.0
> > /usr/sbin/lnetctl
>
> I did not try "--with lnet-dlc" alone but using only --with lustre-utils
> was not enough.
> Probably --enable-utils and --enable-dlc configure arguments can be used
> for the same effect.
> Using flags lnet-dlc and lustre-utils  is in addition to requirement to
> have libyaml-devel installed on build host.
>
> Alex.
>
> > On Nov 30, 2017, at 2:22 PM, Dilger, Andreas 
> wrote:
> >
> > You should also check the config.log to see if it properly detected
> libyaml being installed and enabled “USE_DLC” for the build:
> >
> > configure:35728: checking for yaml_parser_initialize in -lyaml
> > configure:35791: result: yes
> > configure:35801: checking whether to enable dlc
> > configure:35815: result: yes
> >
> > Cheers, Andreas
> >
> > On Nov 29, 2017, at 05:28, Arman Khalatyan  wrote:
> >
> >> even in the extracted source code the lnetctl does not compile.
> >> running make in the utils folder it is producing wirecheck,lst and
> >> routerstat, but not lnetctl.
> >> After running "make lnetctl" in the utils folder
> >> /tmp/lustre-2.10.2_RC1/lnet/utils
> >>
> >> it produces the executable.
> >>
> >>
> >> On Wed, Nov 29, 2017 at 11:52 AM, Arman Khalatyan 
> wrote:
> >>> Hi Andreas,
> >>> I just checked the yaml-devel it is installed:
> >>> yum list installed | grep yaml
> >>> libyaml.x86_64 0.1.4-11.el7_0
> @base
> >>> libyaml-devel.x86_64   0.1.4-11.el7_0
> @base
> >>>
> >>> and still no success:
> >>> rpm -qpl rpmbuild/RPMS/x86_64/*.rpm| grep lnetctl
> >>> /usr/share/man/man8/lnetctl.8.gz
> >>> /usr/src/debug/lustre-2.10.2_RC1/lnet/include/lnet/lnetctl.h
> >>>
> >>> are there any other dependencies ?
> >>>
> >>> Thanks,
> >>> Arman.
> >>>
> >>> On Wed, Nov 29, 2017 at 6:46 AM, Dilger, Andreas
> >>>  wrote:
>  On Nov 28, 2017, at 07:58, Arman Khalatyan  wrote:
> >
> > Hello,
> > I would like to recompile the client from the rpm-source but looks
> > like the packaging on the jenkins is wrong:
> >
> > 1) wget https://build.hpdd.intel.com/job/lustre-b2_10/arch=x86_64,
> build_type=client,distro=el7,ib_stack=inkernel/
> lastSuccessfulBuild/artifact/artifacts/SRPMS/lustre-2.10.2_RC1-1.src.rpm
> > 2) rpmbuild --rebuild --without servers lustre-2.10.2_RC1-1.src.rpm
> > after the successful build the rpms doesn't contain the lnetctl but
> > the help only
> > 3) cd /root/rpmbuild/RPMS/x86_64
> > 4) rpm -qpl ./*.rpm| grep lnetctl
> > /usr/share/man/man8/lnetctl.8.gz
> > /usr/src/debug/lustre-2.10.2_RC1/lnet/include/lnet/lnetctl.h
> >
> > The   lustre-client-2.10.2_RC1-1.el7.x86_64.rpm on the jenkins
> > contains the lnetctl
> > Maybe I should add more options to rebuild the client + lnetctl?
> 
>  You need to have libyaml-devel installed on your build node.
> 
>  Cheers, Andreas
>  --
>  Andreas Dilger
>  Lustre Principal Architect
>  Intel Corporation
> 
> 
> 
> 
> 
> 
> 
> > ___
> > lustre-discuss mailing list
> > lustre-discuss@lists.lustre.org
> > http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
>
> ___
> lustre-discuss mailing list
> lustre-discuss@lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
>
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Re: [lustre-discuss] Recompiling client from the source doesnot contain lnetctl

[Alexander I Kulyavtsev]

Andreas,
It will be extremely helpful to have "rpmbuild --rebuild" to build lustre 
[client] rpm with the same content and functionality as lustre[-client] rpm 
from distro.
The client rpm is rebuild most often for different kinds of worker nodes and I 
see several mails on this list reporting lnetctl is not there.

enable-dlc/disable-dlc flag is not described in manual or lustre wiki 
(http://wiki.lustre.org/Compiling_Lustre) .

Arman,
for the record:
To get lnetctl into the client rpm on slf6.8 I was need to use flags:
rpmbuild  --rebuild --without servers --with lnet-dlc --with 
lustre-utils ./lustre-2.10.2-1.src.rpm

This adds files below to lustre-client-*.rpm wrt build without these flags:
> /etc/lnet.conf
> /usr/lib64/liblnetconfig.a
> /usr/lib64/liblnetconfig.so
> /usr/lib64/liblnetconfig.so.2
> /usr/lib64/liblnetconfig.so.2.0.0
> /usr/sbin/lnetctl

I did not try "--with lnet-dlc" alone but using only --with lustre-utils was 
not enough.
Probably --enable-utils and --enable-dlc configure arguments can be used for 
the same effect.
Using flags lnet-dlc and lustre-utils  is in addition to requirement to have 
libyaml-devel installed on build host.

Alex.

> On Nov 30, 2017, at 2:22 PM, Dilger, Andreas  wrote:
> 
> You should also check the config.log to see if it properly detected libyaml 
> being installed and enabled “USE_DLC” for the build:
> 
> configure:35728: checking for yaml_parser_initialize in -lyaml
> configure:35791: result: yes
> configure:35801: checking whether to enable dlc
> configure:35815: result: yes
> 
> Cheers, Andreas
> 
> On Nov 29, 2017, at 05:28, Arman Khalatyan  wrote:
> 
>> even in the extracted source code the lnetctl does not compile.
>> running make in the utils folder it is producing wirecheck,lst and
>> routerstat, but not lnetctl.
>> After running "make lnetctl" in the utils folder
>> /tmp/lustre-2.10.2_RC1/lnet/utils
>> 
>> it produces the executable.
>> 
>> 
>> On Wed, Nov 29, 2017 at 11:52 AM, Arman Khalatyan  wrote:
>>> Hi Andreas,
>>> I just checked the yaml-devel it is installed:
>>> yum list installed | grep yaml
>>> libyaml.x86_64 0.1.4-11.el7_0  @base
>>> libyaml-devel.x86_64   0.1.4-11.el7_0  @base
>>> 
>>> and still no success:
>>> rpm -qpl rpmbuild/RPMS/x86_64/*.rpm| grep lnetctl
>>> /usr/share/man/man8/lnetctl.8.gz
>>> /usr/src/debug/lustre-2.10.2_RC1/lnet/include/lnet/lnetctl.h
>>> 
>>> are there any other dependencies ?
>>> 
>>> Thanks,
>>> Arman.
>>> 
>>> On Wed, Nov 29, 2017 at 6:46 AM, Dilger, Andreas
>>>  wrote:
 On Nov 28, 2017, at 07:58, Arman Khalatyan  wrote:
> 
> Hello,
> I would like to recompile the client from the rpm-source but looks
> like the packaging on the jenkins is wrong:
> 
> 1) wget 
> https://build.hpdd.intel.com/job/lustre-b2_10/arch=x86_64,build_type=client,distro=el7,ib_stack=inkernel/lastSuccessfulBuild/artifact/artifacts/SRPMS/lustre-2.10.2_RC1-1.src.rpm
> 2) rpmbuild --rebuild --without servers lustre-2.10.2_RC1-1.src.rpm
> after the successful build the rpms doesn't contain the lnetctl but
> the help only
> 3) cd /root/rpmbuild/RPMS/x86_64
> 4) rpm -qpl ./*.rpm| grep lnetctl
> /usr/share/man/man8/lnetctl.8.gz
> /usr/src/debug/lustre-2.10.2_RC1/lnet/include/lnet/lnetctl.h
> 
> The   lustre-client-2.10.2_RC1-1.el7.x86_64.rpm on the jenkins
> contains the lnetctl
> Maybe I should add more options to rebuild the client + lnetctl?
 
 You need to have libyaml-devel installed on your build node.
 
 Cheers, Andreas
 --
 Andreas Dilger
 Lustre Principal Architect
 Intel Corporation
 
 
 
 
 
 
 
> ___
> lustre-discuss mailing list
> lustre-discuss@lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Re: [lustre-discuss] Lustre HSM tool - Lemur

[Jones, Peter A]

There was a LUG presentation about using it in production - 
http://cdn.opensfs.org/wp-content/uploads/2017/06/Thur10-Raso-Barnett-Hammond-LUG2017.pdf
 - but I have not heard of anyone actively doing further development in recent 
months. However, it is open source so it is quite possible that there are 
people who have done so without discussing that work on the mailing lists.

On 2018-01-23, 6:20 AM, "lustre-discuss on behalf of Indivar Nair" 
mailto:lustre-discuss-boun...@lists.lustre.org>
 on behalf of indivar.n...@techterra.in> 
wrote:

Hi ...,

Is Lustre HSM tool - Lemur - Production ready?
And is the project still alive?
There has been no commits for the last 10 Months.
https://github.com/intel-hpdd/lemur

Regards,


Indivar Nair
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

[lustre-discuss] Some deb issues for 2.10.2

[E.S. Rosenberg]

Hi all,
Today I played a bit with Lustre 2.10.2 using the debs for Ubuntu 16.04
client and I was trying to use lnetctl which returned the following error:
lnetctl: error while loading shared libraries: liblnetconfig.so.2: cannot
open shared object file: No such file or directory

The reason for this initially seemed to be that I had not installed
lustre-dev which listed liblnetctl.so as part of its' content.
However it turns out that this liblnetctl.so is just a dead symlink to
liblnetctl.so.2.0.0

So it seems to me there are 2 issues with the debs:
1. liblnetctl.so seems to be missing
2. liblnetctl.so should either be in lustre-utils or lustre-utils should
depend on lustre-dev so that I can't install one without the other

Thanks,
Eli
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

[lustre-discuss] Lustre HSM tool - Lemur

[Indivar Nair]

Hi ...,

Is Lustre HSM tool - Lemur - Production ready?
And is the project still alive?
There has been no commits for the last 10 Months.
https://github.com/intel-hpdd/lemur

Regards,


Indivar Nair
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org