[Lustre-discuss] Lustre-discuss Digest, Vol 33, Issue 2
Chen, Helen Y
hycsw at sandia.gov
Thu Oct 2 09:33:02 PDT 2008
----- Original Message -----
From: lustre-discuss-bounces at lists.lustre.org <lustre-discuss-bounces at lists.lustre.org>
To: lustre-discuss at lists.lustre.org <lustre-discuss at lists.lustre.org>
Sent: Thu Oct 02 02:02:53 2008
Subject: Lustre-discuss Digest, Vol 33, Issue 2
Send Lustre-discuss mailing list submissions to
lustre-discuss at lists.lustre.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.lustre.org/mailman/listinfo/lustre-discuss
or, via email, send a message with subject or body 'help' to
lustre-discuss-request at lists.lustre.org
You can reach the person managing the list at
lustre-discuss-owner at lists.lustre.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Lustre-discuss digest..."
Today's Topics:
1. Re: Lustre-discuss Digest, Vol 32, Issue 29 (Chen, Helen Y)
2. Lustre file system and DNS (Minh Hien)
3. Lustre file system and DNS (Minh Hien)
4. Re: recovery_status inactive (Papp Tamas)
5. Re: recovery_status inactive (Papp Tamas)
6. Re: recovery_status inactive (Papp Tamas)
7. lustre/drbd/heartbeat setup [was: drbd async mode]
(Heiko Schroeter)
----------------------------------------------------------------------
Message: 1
Date: Wed, 1 Oct 2008 15:54:00 -0600
From: "Chen, Helen Y" <hycsw at sandia.gov>
Subject: Re: [Lustre-discuss] Lustre-discuss Digest, Vol 32, Issue 29
To: "'lustre-discuss at lists.lustre.org'"
<lustre-discuss at lists.lustre.org>
Message-ID:
<F9F38212E2D77948B1CD89D239A7C07B0F12A5D327 at ES01SNLNT.srn.sandia.gov>
Content-Type: text/plain; charset=utf-8
----- Original Message -----
From: lustre-discuss-bounces at lists.lustre.org <lustre-discuss-bounces at lists.lustre.org>
To: lustre-discuss at lists.lustre.org <lustre-discuss at lists.lustre.org>
Sent: Sun Sep 28 03:14:32 2008
Subject: Lustre-discuss Digest, Vol 32, Issue 29
Send Lustre-discuss mailing list submissions to
lustre-discuss at lists.lustre.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.lustre.org/mailman/listinfo/lustre-discuss
or, via email, send a message with subject or body 'help' to
lustre-discuss-request at lists.lustre.org
You can reach the person managing the list at
lustre-discuss-owner at lists.lustre.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Lustre-discuss digest..."
Today's Topics:
1. How to change default stripe count (Mike Feuerstein)
2. Re: How to change default stripe count (Andreas Dilger)
3. Re: How to change default stripe count (Mike Feuerstein)
4. e2fsprogs Failed dependencies of GLIBC_2.4, libdb-4.3.so and
rtld(GNU_HASH) (Chirag Raval)
5. e2fsprogs Failed dependencies of GLIBC_2.4, libdb-4.3.so and
rtld(GNU_HASH) (Chirag Raval)
----------------------------------------------------------------------
Message: 1
Date: Fri, 26 Sep 2008 16:41:02 -0500
From: "Mike Feuerstein" <mike at cray.com>
Subject: [Lustre-discuss] How to change default stripe count
To: <lustre-discuss at lists.lustre.org>
Message-ID:
<925346A443D4E340BEB20248BAFCDBDF0794059E at CFEVS1-IP.americas.cray.com>
Content-Type: text/plain; charset="us-ascii"
I suspect that tunefs.lustre is used to change the stripe count for an
existing file system
from Lustre default to some other value, but I'm not sure if I do this
at the MDT or on each OST device.
tunefs.lustre -fsname=[NAME] param lov.stripe_count=4 ??
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080926/ad2960ec/attachment-0001.html
------------------------------
Message: 2
Date: Sat, 27 Sep 2008 00:22:55 -0600
From: Andreas Dilger <adilger at sun.com>
Subject: Re: [Lustre-discuss] How to change default stripe count
To: Mike Feuerstein <mike at cray.com>
Cc: lustre-discuss at lists.lustre.org
Message-ID: <20080927062255.GL10950 at webber.adilger.int>
Content-Type: text/plain; charset=us-ascii
On Sep 26, 2008 16:41 -0500, Mike Feuerstein wrote:
> I suspect that tunefs.lustre is used to change the stripe count for an
> existing file system
>
> from Lustre default to some other value, but I'm not sure if I do this
> at the MDT or on each OST device.
>
> tunefs.lustre -fsname=[NAME] param lov.stripe_count=4 ??
A much easier method with newer filesystems is to just set the striping
on the root directory like "lfs setstripe -c 4 /mnt/lustre" and that
will internally generate the above command and set the default striping.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
------------------------------
Message: 3
Date: Sat, 27 Sep 2008 12:02:16 -0500
From: "Mike Feuerstein" <mike at cray.com>
Subject: Re: [Lustre-discuss] How to change default stripe count
To: "Andreas Dilger" <adilger at sun.com>
Cc: lustre-discuss at lists.lustre.org
Message-ID:
<925346A443D4E340BEB20248BAFCDBDF0794067D at CFEVS1-IP.americas.cray.com>
Content-Type: text/plain; charset="us-ascii"
This sounds elegant, but is it persistent?
If not, what is the more reigorous method?
Mike
-----Original Message-----
From: Andreas.Dilger at sun.com [mailto:Andreas.Dilger at sun.com] On Behalf
Of Andreas Dilger
Sent: Saturday, September 27, 2008 12:23 AM
To: Mike Feuerstein
Cc: lustre-discuss at lists.lustre.org
Subject: Re: [Lustre-discuss] How to change default stripe count
On Sep 26, 2008 16:41 -0500, Mike Feuerstein wrote:
> I suspect that tunefs.lustre is used to change the stripe count for an
> existing file system
>
> from Lustre default to some other value, but I'm not sure if I do this
> at the MDT or on each OST device.
>
> tunefs.lustre -fsname=[NAME] param lov.stripe_count=4 ??
A much easier method with newer filesystems is to just set the striping
on the root directory like "lfs setstripe -c 4 /mnt/lustre" and that
will internally generate the above command and set the default striping.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
------------------------------
Message: 4
Date: Sun, 28 Sep 2008 14:44:31 +0530
From: "Chirag Raval" <raval.chirag at spsoftindia.com>
Subject: [Lustre-discuss] e2fsprogs Failed dependencies of GLIBC_2.4,
libdb-4.3.so and rtld(GNU_HASH)
To: <lustre-discuss at lists.lustre.org>
Message-ID: <000201c9214a$9e41f8f0$dac5ead0$@chirag at spsoftindia.com>
Content-Type: text/plain; charset="us-ascii"
Hi All,
I am Downloading and Installing Lustre-1.6.5-1 of RHEL 4 on CentOS 4.5
following are the details
######
[root at mds ~]# uname -a
Linux mds.sun.com 2.6.9-55.ELsmp #1 SMP Wed May 2 14:28:44 EDT 2007 i686
i686 i386 GNU/Linux
########
[root at mds # ls -l
total 34172
-rw-r--r-- 1 root root 827340 Jul 31 17:11
e2fsprogs-1.40.7.sun3-0redhat.i386.rpm
-rw-r--r-- 1 root root 13035057 Jul 31 17:14
kernel-lustre-smp-2.6.9-67.0.7.EL_lustre.1.6.5.1.i686.rpm
-rw-r--r-- 1 root root 3637635 Jul 31 17:12
lustre-1.6.5.1-2.6.9_67.0.7.EL_lustre.1.6.5.1smp.i686.rpm
-rw-r--r-- 1 root root 853691 Jul 31 17:12
lustre-ldiskfs-3.0.4-2.6.9_67.0.7.EL_lustre.1.6.5.1smp.i686.rpm
-rw-r--r-- 1 root root 16573723 Jul 31 17:14
lustre-modules-1.6.5.1-2.6.9_67.0.7.EL_lustre.1.6.5.1smp.i686.rpm
When i install "e2fsprogs-1.40.7.sun3-0redhat.i386.rpm" it gives me an error
as below
[root at mds RHEL 4]# rpm -ivh e2fsprogs-1.40.7.sun3-0redhat.i386.rpm
error: Failed dependencies:
libc.so.6(GLIBC_2.4) is needed by e2fsprogs-1.40.7.sun3-0redhat.i386
libdb-4.3.so is needed by e2fsprogs-1.40.7.sun3-0redhat.i386
rtld(GNU_HASH) is needed by e2fsprogs-1.40.7.sun3-0redhat.i386
All other rpm gets installed
my glibc Details
[root at mds RHEL 4] # rpm -q glibc
glibc-2.3.4-2.36
[root at mds RHEL 4] # rpm -q glibc-common
glibc-common-2.3.4-2.36
Can someone guide me on this.
Chirag
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080928/2fcb9248/attachment-0001.html
------------------------------
Message: 5
Date: Sun, 28 Sep 2008 14:46:58 +0530
From: "Chirag Raval" <chirag at spsoftindia.com>
Subject: [Lustre-discuss] e2fsprogs Failed dependencies of GLIBC_2.4,
libdb-4.3.so and rtld(GNU_HASH)
To: <lustre-discuss at lists.lustre.org>
Message-ID: <000d01c9214a$f981f530$ec85df90$@com>
Content-Type: text/plain; charset="us-ascii"
Hi All,
I am Downloading and Installing Lustre-1.6.5-1 of RHEL 4 on CentOS 4.5
following are the details
######
[root at mds ~]# uname -a
Linux mds.sun.com 2.6.9-55.ELsmp #1 SMP Wed May 2 14:28:44 EDT 2007 i686
i686 i386 GNU/Linux
########
[root at mds # ls -l
total 34172
-rw-r--r-- 1 root root 827340 Jul 31 17:11
e2fsprogs-1.40.7.sun3-0redhat.i386.rpm
-rw-r--r-- 1 root root 13035057 Jul 31 17:14
kernel-lustre-smp-2.6.9-67.0.7.EL_lustre.1.6.5.1.i686.rpm
-rw-r--r-- 1 root root 3637635 Jul 31 17:12
lustre-1.6.5.1-2.6.9_67.0.7.EL_lustre.1.6.5.1smp.i686.rpm
-rw-r--r-- 1 root root 853691 Jul 31 17:12
lustre-ldiskfs-3.0.4-2.6.9_67.0.7.EL_lustre.1.6.5.1smp.i686.rpm
-rw-r--r-- 1 root root 16573723 Jul 31 17:14
lustre-modules-1.6.5.1-2.6.9_67.0.7.EL_lustre.1.6.5.1smp.i686.rpm
When i install "e2fsprogs-1.40.7.sun3-0redhat.i386.rpm" it gives me an error
as below
[root at mds RHEL 4]# rpm -ivh e2fsprogs-1.40.7.sun3-0redhat.i386.rpm
error: Failed dependencies:
libc.so.6(GLIBC_2.4) is needed by e2fsprogs-1.40.7.sun3-0redhat.i386
libdb-4.3.so is needed by e2fsprogs-1.40.7.sun3-0redhat.i386
rtld(GNU_HASH) is needed by e2fsprogs-1.40.7.sun3-0redhat.i386
All other rpm gets installed
my glibc Details
[root at mds RHEL 4] # rpm -q glibc
glibc-2.3.4-2.36
[root at mds RHEL 4] # rpm -q glibc-common
glibc-common-2.3.4-2.36
Can someone guide me on this.
Chirag
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080928/18493c19/attachment.html
------------------------------
_______________________________________________
Lustre-discuss mailing list
Lustre-discuss at lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss
End of Lustre-discuss Digest, Vol 32, Issue 29
**********************************************
------------------------------
Message: 2
Date: Thu, 2 Oct 2008 00:23:51 -0700 (PDT)
From: Minh Hien <minhhien261 at yahoo.com>
Subject: [Lustre-discuss] Lustre file system and DNS
To: lustre-discuss at lists.lustre.org
Message-ID: <276445.4304.qm at web54005.mail.re2.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Dear all,
We had implemented a lustre file system sometimes ago. Lately, we changed DNS server. We have replaced the /etc/resolv.conf on every node to a new DNS. It seems working fine. However, we want to prevent any other issues which may be originated from this change in the future.
As I know, as long as lustre could resolve the DNS name, there should not be any other issues. Am I correct to say so or there may be some hidden problems?
Thanks for your clarifications
Best Regards,
Karen
------------------------------
Message: 3
Date: Thu, 2 Oct 2008 00:23:51 -0700 (PDT)
From: Minh Hien <minhhien261 at yahoo.com>
Subject: [Lustre-discuss] Lustre file system and DNS
To: lustre-discuss at lists.lustre.org
Message-ID: <276445.4304.qm at web54005.mail.re2.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Dear all,
We had implemented a lustre file system sometimes ago. Lately, we changed DNS server. We have replaced the /etc/resolv.conf on every node to a new DNS. It seems working fine. However, we want to prevent any other issues which may be originated from this change in the future.
As I know, as long as lustre could resolve the DNS name, there should not be any other issues. Am I correct to say so or there may be some hidden problems?
Thanks for your clarifications
Best Regards,
Karen
------------------------------
Message: 4
Date: Thu, 02 Oct 2008 09:51:45 +0200
From: Papp Tamas <tompos at martos.bme.hu>
Subject: Re: [Lustre-discuss] recovery_status inactive
To: Wojciech Turek <wjt27 at cam.ac.uk>
Cc: Lustre discuss <lustre-discuss at lists.lustre.org>
Message-ID: <48E47D91.9010008 at martos.bme.hu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Wojciech Turek wrote:
> Hi,
>
> COMPLETE means that this particular OST was in recovery and recovery is
> now finished.
> To force recovery just unmount OST and then mount it again. If unmounted
> OST had any clients connected after mounting it back it will start
> recovery process to let all the clients reconnect to it. When OST is in
> recovery status it will refuse all new connections from the clients
> which means that file system that this OST is a part of will not be
> accessible until recovery finishes. Recovery will finish either when all
> previously connected clients will reconnect or it will timout after a
> certain amount of time. If one of the clients that was connected to the
> OST will crash or loose power etc. before it will get a chance to
> reconnect then recovery will have to time. If you know that OST will not
> recover all previously connected clients because one of them isn't there
> any more you can avoid waiting for recovery to timeout and you can abort
> recovery manually.
> lctl --device <OST_device_number> abort_recovery
> You can find OST_device_number by running 'lctl dl' command
> You will see line like this
> 7 UP obdfilter ddn_data-OST0009 ddn_data-OST0009_UUID 1159
> Number 7 is the number of the OST device.
>
> All this is in the lustre operation manual, so please read it.
>
Of course I've read the manual many times.
The problem is not with COMPLETE recovery_status, but INACTIVE.
I haven't found any info about it in the manual.
I wanted to force the recovery without unmounting the OST just for give
a try.
Anyway it seems to working right now, I hope, it's OK.
Thanks,
tamas
------------------------------
Message: 5
Date: Thu, 02 Oct 2008 09:51:45 +0200
From: Papp Tamas <tompos at martos.bme.hu>
Subject: Re: [Lustre-discuss] recovery_status inactive
To: Wojciech Turek <wjt27 at cam.ac.uk>
Cc: Lustre discuss <lustre-discuss at lists.lustre.org>
Message-ID: <48E47D91.9010008 at martos.bme.hu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Wojciech Turek wrote:
> Hi,
>
> COMPLETE means that this particular OST was in recovery and recovery is
> now finished.
> To force recovery just unmount OST and then mount it again. If unmounted
> OST had any clients connected after mounting it back it will start
> recovery process to let all the clients reconnect to it. When OST is in
> recovery status it will refuse all new connections from the clients
> which means that file system that this OST is a part of will not be
> accessible until recovery finishes. Recovery will finish either when all
> previously connected clients will reconnect or it will timout after a
> certain amount of time. If one of the clients that was connected to the
> OST will crash or loose power etc. before it will get a chance to
> reconnect then recovery will have to time. If you know that OST will not
> recover all previously connected clients because one of them isn't there
> any more you can avoid waiting for recovery to timeout and you can abort
> recovery manually.
> lctl --device <OST_device_number> abort_recovery
> You can find OST_device_number by running 'lctl dl' command
> You will see line like this
> 7 UP obdfilter ddn_data-OST0009 ddn_data-OST0009_UUID 1159
> Number 7 is the number of the OST device.
>
> All this is in the lustre operation manual, so please read it.
>
Of course I've read the manual many times.
The problem is not with COMPLETE recovery_status, but INACTIVE.
I haven't found any info about it in the manual.
I wanted to force the recovery without unmounting the OST just for give
a try.
Anyway it seems to working right now, I hope, it's OK.
Thanks,
tamas
------------------------------
Message: 6
Date: Thu, 02 Oct 2008 09:55:35 +0200
From: Papp Tamas <tompos at martos.bme.hu>
Subject: Re: [Lustre-discuss] recovery_status inactive
To: Lustre discuss <lustre-discuss at lists.lustre.org>
Message-ID: <48E47E77.6060908 at martos.bme.hu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Papp Tamas wrote:
I think something wrong with the listserver, I only sent one email:)
tamas
------------------------------
Message: 7
Date: Thu, 2 Oct 2008 10:02:37 +0200
From: Heiko Schroeter <schroete at iup.physik.uni-bremen.de>
Subject: [Lustre-discuss] lustre/drbd/heartbeat setup [was: drbd async
mode]
To: Lustre discuss <lustre-discuss at lists.lustre.org>
Message-ID: <200810021002.37279.schroete at iup.physik.uni-bremen.de>
Content-Type: text/plain; charset="iso-8859-1"
Hello,
at last a first version of our setup scenario is ready.
Please consider this as a general guideline. It may contain errors.
We know that some things are done differently in the lustre community i.e.
placing MDS and MDT on seperate machines.
Please let me know if you find bugs or if things can be improved.
"There is more than one way."
Regards
Heiko
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lustre_drbd_hearbeat_setup.pdf
Type: application/pdf
Size: 421143 bytes
Desc: not available
Url : http://lists.lustre.org/pipermail/lustre-discuss/attachments/20081002/1651c518/attachment.pdf
------------------------------
_______________________________________________
Lustre-discuss mailing list
Lustre-discuss at lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss
End of Lustre-discuss Digest, Vol 33, Issue 2
*********************************************
More information about the lustre-discuss
mailing list