Re: [Lustre-discuss] Announce: Lustre 2.0.0 is available!

[Mag Gam]

thanks.

Either way, congrats! and keep up the good work



On Thu, Sep 9, 2010 at 11:37 AM, Andreas Dilger
 wrote:
> On 2010-09-09, at 4:53, Mag Gam  wrote:
>> For the future releases, will the client ever be part of the stock
>> kernel?
>
> There are no current plans to do this, due to the huge amount of work needed, 
> and the fact that it probably wouldn't be accepted without removing all of 
> the portability API needed to work on Windows, MacOS, Solaris.
>
>> What is the status of SNS? This is an important feature for
>> many people and it seems people are are shying away from Lustre and
>> going to other solutions solely based on this feature.
>
> I hear your comments, but it isn't on the immediate horizon. There is 
> groundwork for this done in the HSM project, and them it will be possible to 
> begin to work on this feature.
>
>> On Thu, Aug 26, 2010 at 1:54 PM, Terry Rutledge
>>  wrote:
>>>  Hi all,
>>>
>>> The entire Lustre team is pleased to announce the GA Release of Lustre
>>> 2.0.0.
>>> This represents the first release of the main Lustre trunk in a number
>>> of years.
>>> The team has spent extraordinary efforts over the last year preparing this
>>> release for GA. This release has had the most extensive pre-release testing
>>> of any previous Lustre release.
>>>
>>> We are excited for the community to try this release and offer feedback.
>>>
>>> Our next 2.x release is planned for later this year and details will follow
>>> at a later date.
>>>
>>> Quick Reference:
>>> Lustre 2.0.0 is available on the Oracle Download Center Site.
>>> http://www.oracle.com/technetwork/indexes/downloads/sun-az-index-095901.html#L
>>>
>>> The Lustre 2.0 Operations Manual:
>>> http://dlc.sun.com/pdf/821-2076-10/821-2076-10.pdf
>>>
>>> The Release Notes:
>>> http://dlc.sun.com/pdf/821-2077-10/821-2077-10.pdf
>>>
>>> The change log:
>>> http://wiki.lustre.org/index.php/Change_Log_2.0
>>>
>>> As always, you can report issues via Bugzilla:
>>> https://bugzilla.lustre.org/
>>>
>>> To access earlier releases of Lustre, please check the box
>>> "See previous products(P)", then click "L" or scroll down to
>>> "Lustre", the current and all previous releases (1.8.0 - 1.8.4)
>>> will be displayed.
>>>
>>> Happy downloading!
>>>
>>> -- The Lustre Team --
>>>
>>>
>>> ___
>>> Lustre-discuss mailing list
>>> Lustre-discuss@lists.lustre.org
>>> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>>>
>> ___
>> Lustre-discuss mailing list
>> Lustre-discuss@lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

Re: [Lustre-discuss] Problem with LNET and openibd on Lustre 1.8.4 while rebooting

[Mike Hanby]

That's odd, I have 1.8.1.1 and use _netdev for both my Infiniband and GigE 
clients, both mount successfully.

For IB clients:
10.1.11...@o2ib:/lustre/lustre   lustre  _netdev 0 0

And GigE clients:
10.1.10.20...@tcp:/lustre  /lustre   lustre  _netdev 0 0

-Original Message-
From: lustre-discuss-boun...@lists.lustre.org 
[mailto:lustre-discuss-boun...@lists.lustre.org] On Behalf Of Nirmal Seenu
Sent: Thursday, September 09, 2010 2:58 PM
To: Ken Hornstein
Cc: lustre-discuss@lists.lustre.org
Subject: Re: [Lustre-discuss] Problem with LNET and openibd on Lustre 1.8.4 
while rebooting

I guess the trick is to use _netdev as an option in the mount command or the 
/etc/fstab entry as Andreas mentioned.

I used to have the _netdev option when I was using Lustre over ethernet which 
made the automounts work correctly and I didn't have the LNET problem.

With infiniband(openibd) the _netdev option doesn't mount lustre correctly and 
I had to mount lustre from rc.local after the infiniband networks comes up.

Nirmal

On 09/09/2010 02:44 PM, Ken Hornstein wrote:
>> lustre does get unmounted before NFS filesystem as seen in the log message...
>> the problem is due to the fact that LNET is still up when openibd gets
>> removed.
>
> Huh, I'm wondering how it ever worked "right" before.  Certainly on the 
> systems
> I have at 1.8.1.1, I always had to have a Lustre start/stop script which did
> a lustre_rmmod as part of the stop sequence.
>
> --Ken
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

Re: [Lustre-discuss] Problem with LNET and openibd on Lustre 1.8.4 while rebooting

[Nirmal Seenu]

I guess the trick is to use _netdev as an option in the mount command or the 
/etc/fstab entry as Andreas mentioned.

I used to have the _netdev option when I was using Lustre over ethernet which 
made the automounts work correctly and I didn't have the LNET problem.

With infiniband(openibd) the _netdev option doesn't mount lustre correctly and 
I had to mount lustre from rc.local after the infiniband networks comes up.

Nirmal

On 09/09/2010 02:44 PM, Ken Hornstein wrote:
>> lustre does get unmounted before NFS filesystem as seen in the log message...
>> the problem is due to the fact that LNET is still up when openibd gets
>> removed.
>
> Huh, I'm wondering how it ever worked "right" before.  Certainly on the 
> systems
> I have at 1.8.1.1, I always had to have a Lustre start/stop script which did
> a lustre_rmmod as part of the stop sequence.
>
> --Ken
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

Re: [Lustre-discuss] Problem with LNET and openibd on Lustre 1.8.4 while rebooting

[Ken Hornstein]

>lustre does get unmounted before NFS filesystem as seen in the log message...
>the problem is due to the fact that LNET is still up when openibd gets 
>removed.

Huh, I'm wondering how it ever worked "right" before.  Certainly on the systems
I have at 1.8.1.1, I always had to have a Lustre start/stop script which did
a lustre_rmmod as part of the stop sequence.

--Ken
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

Re: [Lustre-discuss] Problem with LNET and openibd on Lustre 1.8.4 while rebooting

[Nirmal Seenu]

lustre does get unmounted before NFS filesystem as seen in the log message... 
the problem is due to the fact that LNET is still up when openibd gets 
removed.

Nirmal

On 09/09/2010 02:28 PM, Andreas Dilger wrote:
> On 2010-09-09, at 10:56, Nirmal Seenu wrote:
>> I just upgraded my lustre version from 1.8.1.1 to 1.8.4 and I can't reboot 
>> my lustre clients cleanly anymore. I am using the latest RHEL kernel and
>> the openibd that comes part of that RHEL kernel + patchless lustre client 
>> installed from the tar ball.
>>
>> The lustre client gets unmounted cleanly but the system deadlocks once the 
>> openibd driver is removed. I had to modify the openibd stop script to
>> include "umount lustre" and "lustre_rmmod" as a work around.
>
> If you put "_netdev" in the lustre mount options, the shutdown scripts  
> should unmount it before trying to stop the networking.
>
>
>> The following is the error message that I get when I try to reboot the 
>> lustre client:
>>
>> Scientific Linux SLF release 5.3 (Lederman)
>> Kernel 2.6.18-194.11.1.el5 on an x86_64
>>
>> INIT:Shutting down smartd: [  OK  ]
>> Stopping atd: [  OK  ]
>> Shutting down process accounting:  [  OK  ]
>> Stopping xinetd: [  OK  ]
>> Stopping autofs:  Stopping automount: [  OK  ]
>> [  OK  ]
>> Stopping acpi daemon: [  OK  ]
>> Shutting down ntpd: [  OK  ]
>> Unmounting network block filesystems:  LustreError: 
>> 3697:0:(ldlm_request.c:1025:ldlm_cli_cancel_req()) Got rc -108 from cancel 
>> RPC: canceling anyway
>> LustreError: 3697:0:(ldlm_request.c:1587:ldlm_cli_cancel_list()) 
>> ldlm_cli_cancel_list: -108
>> Lustre: client 81020f145400 umount complete
>> [  OK  ]
>> Unmounting NFS filesystems:  [  OK  ]
>> Stopping system message bus: [  OK  ]
>> Stopping RPC idmapd: [  OK  ]
>> Stopping NFS locking: [  OK  ]
>> Stopping NFS statd: [  OK  ]
>> Stopping portmap: [  OK  ]
>> Stopping PC/SC smart card daemon (pcscd): [  OK  ]
>> Shutting down kernel logger: [  OK  ]
>> Shutting down system logger: [  OK  ]
>> Unloading OpenIB kernel modules:NET: Unregistered protocol family 27
>>
>> Failed to unload rdma_cm
>>
>> Failed to unload ib_cm
>>
>> Failed to unload iw_cm
>> LustreError: 131-3: Received notification of device removal
>> Please shutdown LNET to allow this to proceed
>> INFO: task rmmod:4151 blocked for more than 120 seconds.
>> "echo 0>  /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>> rmmod D 810227061420 0  4151   3795 
>> (NOTLB)
>>   81021c8ddce8 0082 000f 0292
>>   00ef 0001 81020ecdd100 8102271ef040
>>   004a957c4bd9 0095dc57 81020ecdd2e8 000480076646
>> Call Trace:
>>   [] wait_for_completion+0x79/0xa2
>>   [] default_wake_function+0x0/0xe
>>   [] mutex_lock+0xd/0x1d
>>   [] :rdma_cm:cma_remove_one+0x171/0x1a2
>>   [] do_flush_tlb_all+0x0/0x6a
>>   [] :ib_core:ib_unregister_device+0x30/0xdb
>>   [] :ib_mthca:__mthca_remove_one+0x30/0x11a
>>   [] mutex_lock+0xd/0x1d
>>   [] :ib_mthca:mthca_remove_one+0x18/0x25
>>   [] pci_device_remove+0x24/0x3a
>>   [] __device_release_driver+0x9f/0xe9
>>   [] driver_detach+0xad/0x101
>>   [] bus_remove_driver+0x6f/0x92
>>   [] driver_unregister+0xd/0x16
>>   [] pci_unregister_driver+0x2a/0x79
>>   [] :ib_mthca:mthca_cleanup+0x10/0x16
>>   [] sys_delete_module+0x196/0x1c5
>>   [] system_call+0x7e/0x83
>>
>>
>> Nirmal
>> ___
>> Lustre-discuss mailing list
>> Lustre-discuss@lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
>
> Cheers, Andreas
> --
> Andreas Dilger
> Lustre Technical Lead
> Oracle Corporation Canada Inc.
>
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

Re: [Lustre-discuss] Problem with LNET and openibd on Lustre 1.8.4 while rebooting

[Andreas Dilger]

On 2010-09-09, at 10:56, Nirmal Seenu wrote:
> I just upgraded my lustre version from 1.8.1.1 to 1.8.4 and I can't reboot my 
> lustre clients cleanly anymore. I am using the latest RHEL kernel and 
> the openibd that comes part of that RHEL kernel + patchless lustre client 
> installed from the tar ball.
> 
> The lustre client gets unmounted cleanly but the system deadlocks once the 
> openibd driver is removed. I had to modify the openibd stop script to 
> include "umount lustre" and "lustre_rmmod" as a work around.

If you put "_netdev" in the lustre mount options, the shutdown scripts  should 
unmount it before trying to stop the networking.


> The following is the error message that I get when I try to reboot the lustre 
> client:
> 
> Scientific Linux SLF release 5.3 (Lederman)
> Kernel 2.6.18-194.11.1.el5 on an x86_64
> 
> INIT:Shutting down smartd: [  OK  ]
> Stopping atd: [  OK  ]
> Shutting down process accounting:  [  OK  ]
> Stopping xinetd: [  OK  ]
> Stopping autofs:  Stopping automount: [  OK  ]
> [  OK  ]
> Stopping acpi daemon: [  OK  ]
> Shutting down ntpd: [  OK  ]
> Unmounting network block filesystems:  LustreError: 
> 3697:0:(ldlm_request.c:1025:ldlm_cli_cancel_req()) Got rc -108 from cancel 
> RPC: canceling anyway
> LustreError: 3697:0:(ldlm_request.c:1587:ldlm_cli_cancel_list()) 
> ldlm_cli_cancel_list: -108
> Lustre: client 81020f145400 umount complete
> [  OK  ]
> Unmounting NFS filesystems:  [  OK  ]
> Stopping system message bus: [  OK  ]
> Stopping RPC idmapd: [  OK  ]
> Stopping NFS locking: [  OK  ]
> Stopping NFS statd: [  OK  ]
> Stopping portmap: [  OK  ]
> Stopping PC/SC smart card daemon (pcscd): [  OK  ]
> Shutting down kernel logger: [  OK  ]
> Shutting down system logger: [  OK  ]
> Unloading OpenIB kernel modules:NET: Unregistered protocol family 27
> 
> Failed to unload rdma_cm
> 
> Failed to unload ib_cm
> 
> Failed to unload iw_cm
> LustreError: 131-3: Received notification of device removal
> Please shutdown LNET to allow this to proceed
> INFO: task rmmod:4151 blocked for more than 120 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> rmmod D 810227061420 0  4151   3795 
> (NOTLB)
>  81021c8ddce8 0082 000f 0292
>  00ef 0001 81020ecdd100 8102271ef040
>  004a957c4bd9 0095dc57 81020ecdd2e8 000480076646
> Call Trace:
>  [] wait_for_completion+0x79/0xa2
>  [] default_wake_function+0x0/0xe
>  [] mutex_lock+0xd/0x1d
>  [] :rdma_cm:cma_remove_one+0x171/0x1a2
>  [] do_flush_tlb_all+0x0/0x6a
>  [] :ib_core:ib_unregister_device+0x30/0xdb
>  [] :ib_mthca:__mthca_remove_one+0x30/0x11a
>  [] mutex_lock+0xd/0x1d
>  [] :ib_mthca:mthca_remove_one+0x18/0x25
>  [] pci_device_remove+0x24/0x3a
>  [] __device_release_driver+0x9f/0xe9
>  [] driver_detach+0xad/0x101
>  [] bus_remove_driver+0x6f/0x92
>  [] driver_unregister+0xd/0x16
>  [] pci_unregister_driver+0x2a/0x79
>  [] :ib_mthca:mthca_cleanup+0x10/0x16
>  [] sys_delete_module+0x196/0x1c5
>  [] system_call+0x7e/0x83
> 
> 
> Nirmal
> ___
> Lustre-discuss mailing list
> Lustre-discuss@lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss


Cheers, Andreas
--
Andreas Dilger
Lustre Technical Lead
Oracle Corporation Canada Inc.

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

[Lustre-discuss] Problem with LNET and openibd on Lustre 1.8.4 while rebooting

[Nirmal Seenu]

I just upgraded my lustre version from 1.8.1.1 to 1.8.4 and I can't reboot my 
lustre clients cleanly anymore. I am using the latest RHEL kernel and 
the openibd that comes part of that RHEL kernel + patchless lustre client 
installed from the tar ball.

The lustre client gets unmounted cleanly but the system deadlocks once the 
openibd driver is removed. I had to modify the openibd stop script to 
include "umount lustre" and "lustre_rmmod" as a work around.

The following is the error message that I get when I try to reboot the lustre 
client:

Scientific Linux SLF release 5.3 (Lederman)
Kernel 2.6.18-194.11.1.el5 on an x86_64

INIT:Shutting down smartd: [  OK  ]
Stopping atd: [  OK  ]
Shutting down process accounting:  [  OK  ]
Stopping xinetd: [  OK  ]
Stopping autofs:  Stopping automount: [  OK  ]
[  OK  ]
Stopping acpi daemon: [  OK  ]
Shutting down ntpd: [  OK  ]
Unmounting network block filesystems:  LustreError: 
3697:0:(ldlm_request.c:1025:ldlm_cli_cancel_req()) Got rc -108 from cancel RPC: 
canceling anyway
LustreError: 3697:0:(ldlm_request.c:1587:ldlm_cli_cancel_list()) 
ldlm_cli_cancel_list: -108
Lustre: client 81020f145400 umount complete
[  OK  ]
Unmounting NFS filesystems:  [  OK  ]
Stopping system message bus: [  OK  ]
Stopping RPC idmapd: [  OK  ]
Stopping NFS locking: [  OK  ]
Stopping NFS statd: [  OK  ]
Stopping portmap: [  OK  ]
Stopping PC/SC smart card daemon (pcscd): [  OK  ]
Shutting down kernel logger: [  OK  ]
Shutting down system logger: [  OK  ]
Unloading OpenIB kernel modules:NET: Unregistered protocol family 27

Failed to unload rdma_cm

Failed to unload ib_cm

Failed to unload iw_cm
LustreError: 131-3: Received notification of device removal
Please shutdown LNET to allow this to proceed
INFO: task rmmod:4151 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
rmmod D 810227061420 0  4151   3795 (NOTLB)
  81021c8ddce8 0082 000f 0292
  00ef 0001 81020ecdd100 8102271ef040
  004a957c4bd9 0095dc57 81020ecdd2e8 000480076646
Call Trace:
  [] wait_for_completion+0x79/0xa2
  [] default_wake_function+0x0/0xe
  [] mutex_lock+0xd/0x1d
  [] :rdma_cm:cma_remove_one+0x171/0x1a2
  [] do_flush_tlb_all+0x0/0x6a
  [] :ib_core:ib_unregister_device+0x30/0xdb
  [] :ib_mthca:__mthca_remove_one+0x30/0x11a
  [] mutex_lock+0xd/0x1d
  [] :ib_mthca:mthca_remove_one+0x18/0x25
  [] pci_device_remove+0x24/0x3a
  [] __device_release_driver+0x9f/0xe9
  [] driver_detach+0xad/0x101
  [] bus_remove_driver+0x6f/0x92
  [] driver_unregister+0xd/0x16
  [] pci_unregister_driver+0x2a/0x79
  [] :ib_mthca:mthca_cleanup+0x10/0x16
  [] sys_delete_module+0x196/0x1c5
  [] system_call+0x7e/0x83


Nirmal
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

Re: [Lustre-discuss] Announce: Lustre 2.0.0 is available!

[Andreas Dilger]

On 2010-09-09, at 4:53, Mag Gam  wrote:
> For the future releases, will the client ever be part of the stock
> kernel?

There are no current plans to do this, due to the huge amount of work needed, 
and the fact that it probably wouldn't be accepted without removing all of the 
portability API needed to work on Windows, MacOS, Solaris. 

> What is the status of SNS? This is an important feature for
> many people and it seems people are are shying away from Lustre and
> going to other solutions solely based on this feature.

I hear your comments, but it isn't on the immediate horizon. There is 
groundwork for this done in the HSM project, and them it will be possible to 
begin to work on this feature. 

> On Thu, Aug 26, 2010 at 1:54 PM, Terry Rutledge
>  wrote:
>>  Hi all,
>> 
>> The entire Lustre team is pleased to announce the GA Release of Lustre
>> 2.0.0.
>> This represents the first release of the main Lustre trunk in a number
>> of years.
>> The team has spent extraordinary efforts over the last year preparing this
>> release for GA. This release has had the most extensive pre-release testing
>> of any previous Lustre release.
>> 
>> We are excited for the community to try this release and offer feedback.
>> 
>> Our next 2.x release is planned for later this year and details will follow
>> at a later date.
>> 
>> Quick Reference:
>> Lustre 2.0.0 is available on the Oracle Download Center Site.
>> http://www.oracle.com/technetwork/indexes/downloads/sun-az-index-095901.html#L
>> 
>> The Lustre 2.0 Operations Manual:
>> http://dlc.sun.com/pdf/821-2076-10/821-2076-10.pdf
>> 
>> The Release Notes:
>> http://dlc.sun.com/pdf/821-2077-10/821-2077-10.pdf
>> 
>> The change log:
>> http://wiki.lustre.org/index.php/Change_Log_2.0
>> 
>> As always, you can report issues via Bugzilla:
>> https://bugzilla.lustre.org/
>> 
>> To access earlier releases of Lustre, please check the box
>> "See previous products(P)", then click "L" or scroll down to
>> "Lustre", the current and all previous releases (1.8.0 - 1.8.4)
>> will be displayed.
>> 
>> Happy downloading!
>> 
>> -- The Lustre Team --
>> 
>> 
>> ___
>> Lustre-discuss mailing list
>> Lustre-discuss@lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>> 
> ___
> Lustre-discuss mailing list
> Lustre-discuss@lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

Re: [Lustre-discuss] Announce: Lustre 2.0.0 is available!

[Andreas Dilger]

On a related note, there are already patches for SLES11SP1 in bugzilla (for 
1.8) and for RHEL 6 (for 2.0) that should be used as the basis for this. 

Cheers, Andreas

On 2010-09-09, at 5:11, "Brian J. Murrell"  wrote:

> On Thu, 2010-09-09 at 11:54 +0200, Patrick Winnertz wrote: 
>> Hey,
> 
> Hi Patrick,
> 
>> I've seen from the lustre support matrix that only the RHEL5 kernel is 
>> supported on the server side and not any longer a SLES kernel.
> 
> Yes, that's true.
> 
>> Is it planned 
>> to reintegrate a current SLES kernel as server or will lustre be focused on 
>> RHEL?
> 
> There are no plans that I know of to reintegrate SLES and yes RHEL/OEL
> is the future for servers in the 2.x product line.
> 
> Of course, we always welcome patches.
> 
> Cheers,
> b.
> 
> ___
> Lustre-discuss mailing list
> Lustre-discuss@lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

Re: [Lustre-discuss] Oss Error and 0 byte files

[Kevin Van Maren]

I believe grant leak is still possible with 1.8.4, but many of the holes 
are plugged.

Kevin


Gabriele Paciucci wrote:
> the bug 22755 is fixed in 1.8.4
>
> http://wiki.lustre.org/index.php/Use:Change_Log_1.8
>
>
>
>
> On 09/09/2010 11:55 AM, Gianluca Tresoldi wrote:
>> Yes, client gets ENOSP,I see now.
>>
>> Anyway: ThankYou Very Much for your reply ;)
>>
>>
>> On 09/08/10 17:29, Kevin Van Maren wrote:
>>> It might be related to bug 22755, but there the client gets ENOSPC
>>>
>>>
>>> On Sep 8, 2010, at 8:02 AM, Gianluca Tresoldi 
>>> >> > wrote:
>>>
 Hello everyone

 I've an installation with Lustre 1.8.2, Centos 5, x86_64 and  I 
 encountered this problem:

 After several months of smooth operation, client begin to write 
 empty files without log error,from their point of view writing was 
 successful.

 OSS wrote, in their log, several lines like:
 Sep  8 12:40:31 tgoss-0200 kernel: LustreError: 
 5816:0:(filter_io.c:183:filter_grant_space_left()) lfs01-OST: 
 cli 20d94382-3300-f12e-65d1-c0f1743e1e20/8106a4e30a00 grant 
 39956230144 > available 39956226048 and pending 0

 I checked the availability of space and inodes, but this is not the 
 problem.

 the problem goes away by rebooting ost.

 This is the second time I have, first at july 2010, second 
 september 2010.

 Any ideas?It's a bug?

 Thanks
 -- 
 Gianluca Tresoldi

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

Re: [Lustre-discuss] Oss Error and 0 byte files

[Gabriele Paciucci]

the bug 22755 is fixed in 1.8.4

http://wiki.lustre.org/index.php/Use:Change_Log_1.8




On 09/09/2010 11:55 AM, Gianluca Tresoldi wrote:
> Yes, client gets ENOSP,I see now.
>
> Anyway: ThankYou Very Much for your reply ;)
>
>
> On 09/08/10 17:29, Kevin Van Maren wrote:
>> It might be related to bug 22755, but there the client gets ENOSPC
>>
>>
>> On Sep 8, 2010, at 8:02 AM, Gianluca Tresoldi 
>> > > wrote:
>>
>>> Hello everyone
>>>
>>> I've an installation with Lustre 1.8.2, Centos 5, x86_64 and  I 
>>> encountered this problem:
>>>
>>> After several months of smooth operation, client begin to write 
>>> empty files without log error,from their point of view writing was 
>>> successful.
>>>
>>> OSS wrote, in their log, several lines like:
>>> Sep  8 12:40:31 tgoss-0200 kernel: LustreError: 
>>> 5816:0:(filter_io.c:183:filter_grant_space_left()) lfs01-OST: 
>>> cli 20d94382-3300-f12e-65d1-c0f1743e1e20/8106a4e30a00 grant 
>>> 39956230144 > available 39956226048 and pending 0
>>>
>>> I checked the availability of space and inodes, but this is not the 
>>> problem.
>>>
>>> the problem goes away by rebooting ost.
>>>
>>> This is the second time I have, first at july 2010, second september 
>>> 2010.
>>>
>>> Any ideas?It's a bug?
>>>
>>> Thanks
>>> -- 
>>> Gianluca Tresoldi
>>> ***SysAdmin***
>>> ***Demon's Trainer***
>>> Tuttogratis Italia Spa
>>> E-mail: gianluca.treso...@tuttogratis.com 
>>> 
>>> http://www.tuttogratis.it
>>> Tel Centralino 02-57313101
>>> Tel Diretto 02-57313136
>>>  Be open...
>>>  Confidentiality Notice & Disclaimer *
>>> This message, together with any attachments, is for the confidential
>>> and exclusive use of the addressee(s). If you receive it in error,
>>> please delete the message and its attachments from your system
>>> immediately and notify us by return e-mail.
>>> Do not disclose, copy, circulate or use any information contained in
>>> this e-mail.
>>> *
>>> ___
>>> Lustre-discuss mailing list
>>> Lustre-discuss@lists.lustre.org 
>>> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
>
> -- 
> Gianluca Tresoldi
> ***SysAdmin***
> ***Demon's Trainer***
> Tuttogratis Italia Spa
> E-mail: gianluca.treso...@tuttogratis.com
> http://www.tuttogratis.it
> Tel Centralino 02-57313101
> Tel Diretto 02-57313136
> Be open...
>  Confidentiality Notice & Disclaimer *
> This message, together with any attachments, is for the confidential
> and exclusive use of the addressee(s). If you receive it in error,
> please delete the message and its attachments from your system
> immediately and notify us by return e-mail.
> Do not disclose, copy, circulate or use any information contained in
> this e-mail.
> *
>
>
> ___
> Lustre-discuss mailing list
> Lustre-discuss@lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>


-- 
_Gabriele Paciucci_ http://www.linkedin.com/in/paciucci

Pursuant to legislative Decree n. 196/03 you are hereby informed that this 
email contains confidential information intended only for use of addressee. If 
you are not the addressee and have received this email by mistake, please send 
this email to the sender. You may not copy or disseminate this message to 
anyone. Thank You.

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

Re: [Lustre-discuss] What's the correct sequence to umount multiple lustre file system

[Brian J. Murrell]

On Thu, 2010-09-09 at 18:11 +0800, KMing wrote:
> Any recommendation about the sequence to umount multiple lustre file
> system with combined MGS/MDT or separate MGS, MDT. Thanks.

This question actually answers itself if you think about it logically.

If you unmount OSTs first, you leave the possibility of a client getting
object references to OSTs which are no longer able to answer.  So leave
the OSTs mounted to help drain any remaining requests and unmount the
MDT first.  Once the MDT is unmounted, unmount the OSTs.  The MGS is not
involved in unmounting so it can be unmounted at any time.

b.



signature.asc
Description: This is a digitally signed message part
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

Re: [Lustre-discuss] Announce: Lustre 2.0.0 is available!

[Brian J. Murrell]

On Thu, 2010-09-09 at 11:54 +0200, Patrick Winnertz wrote: 
> Hey,

Hi Patrick,

> I've seen from the lustre support matrix that only the RHEL5 kernel is 
> supported on the server side and not any longer a SLES kernel.

Yes, that's true.

> Is it planned 
> to reintegrate a current SLES kernel as server or will lustre be focused on 
> RHEL?

There are no plans that I know of to reintegrate SLES and yes RHEL/OEL
is the future for servers in the 2.x product line.

Of course, we always welcome patches.

Cheers,
b.



signature.asc
Description: This is a digitally signed message part
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

Re: [Lustre-discuss] Announce: Lustre 2.0.0 is available!

[Mag Gam]

 This is great news!

 For the future releases, will the client ever be part of the stock
kernel? What is the status of SNS? This is an important feature for
many people and it seems people are are shying away from Lustre and
 going to other solutions solely based on this feature.


On Thu, Aug 26, 2010 at 1:54 PM, Terry Rutledge
 wrote:
>  Hi all,
>
> The entire Lustre team is pleased to announce the GA Release of Lustre
> 2.0.0.
> This represents the first release of the main Lustre trunk in a number
> of years.
> The team has spent extraordinary efforts over the last year preparing this
> release for GA. This release has had the most extensive pre-release testing
> of any previous Lustre release.
>
> We are excited for the community to try this release and offer feedback.
>
> Our next 2.x release is planned for later this year and details will follow
> at a later date.
>
> Quick Reference:
> Lustre 2.0.0 is available on the Oracle Download Center Site.
> http://www.oracle.com/technetwork/indexes/downloads/sun-az-index-095901.html#L
>
> The Lustre 2.0 Operations Manual:
> http://dlc.sun.com/pdf/821-2076-10/821-2076-10.pdf
>
> The Release Notes:
> http://dlc.sun.com/pdf/821-2077-10/821-2077-10.pdf
>
> The change log:
> http://wiki.lustre.org/index.php/Change_Log_2.0
>
> As always, you can report issues via Bugzilla:
> https://bugzilla.lustre.org/
>
> To access earlier releases of Lustre, please check the box
> "See previous products(P)", then click "L" or scroll down to
> "Lustre", the current and all previous releases (1.8.0 - 1.8.4)
> will be displayed.
>
> Happy downloading!
>
> -- The Lustre Team --
>
>
> ___
> Lustre-discuss mailing list
> Lustre-discuss@lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

[Lustre-discuss] What's the correct sequence to umount multiple lustre file system

[KMing]

Any recommendation about the sequence to umount multiple lustre file system 
with combined MGS/MDT or separate MGS, MDT. Thanks.

Ming
  ___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

Re: [Lustre-discuss] Announce: Lustre 2.0.0 is available!

[Patrick Winnertz]

Hey,

> The team has spent extraordinary efforts over the last year preparing this
> release for GA. This release has had the most extensive pre-release testing
> of any previous Lustre release.
I've seen from the lustre support matrix that only the RHEL5 kernel is 
supported on the server side and not any longer a SLES kernel. Is it planned 
to reintegrate a current SLES kernel as server or will lustre be focused on 
RHEL?


Greetings
Patrick

-- 
Patrick Winnertz
Tel.: +49 (0)21 61 - 46 43-0
Fax:  +49 (0)21 61 - 46 43-100

credativ GmbH, HRB Mönchengladbach 12080
Hohenzollernstr. 133, 41061 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

Re: [Lustre-discuss] Oss Error and 0 byte files

[Gianluca Tresoldi]

  
  
Yes, client gets ENOSP,I see now.

Anyway: ThankYou Very Much for your reply ;)


On 09/08/10 17:29, Kevin Van Maren wrote:

  It might be related to bug 22755, but there the client gets
ENOSPC
   

On Sep 8, 2010, at 8:02 AM, Gianluca Tresoldi 
wrote:

  
  
 Hello everyone
  
  I've an installation with Lustre 1.8.2, Centos 5, x86_64 and 
  I encountered this problem:
  
  After several months of smooth operation, client begin to
  write empty files without log error,from their point of view
  writing was successful.
  
  OSS wrote, in their log, several lines like:
  Sep  8 12:40:31 tgoss-0200 kernel: LustreError:
  5816:0:(filter_io.c:183:filter_grant_space_left())
  lfs01-OST: cli
  20d94382-3300-f12e-65d1-c0f1743e1e20/8106a4e30a00 grant
  39956230144 > available 39956226048 and pending 0
  
  I checked the availability of space and inodes, but this is
  not the problem.
  
  the problem goes away by rebooting ost.
  
  This is the second time I have, first at july 2010, second
  september 2010.
  
  Any ideas?It's a bug?
  
  Thanks
  -- 
Gianluca Tresoldi
***SysAdmin***
***Demon's Trainer***
Tuttogratis Italia Spa
E-mail: gianluca.treso...@tuttogratis.com
http://www.tuttogratis.it
Tel Centralino 02-57313101
Tel Diretto 02-57313136
Be

open...
*** Confidentiality Notice & Disclaimer
  *
  This message, together with any attachments, is for the
  confidential
  and exclusive use of the addressee(s). If you receive it
  in error,
  please delete the message and its attachments from your
  system
  immediately and notify us by return e-mail.
  Do not disclose, copy, circulate or use any information
  contained in
  this e-mail.
 

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

  



-- 
  Gianluca Tresoldi
  ***SysAdmin***
  ***Demon's Trainer***
  Tuttogratis Italia Spa
  E-mail: gianluca.treso...@tuttogratis.com
  http://www.tuttogratis.it
  Tel Centralino 02-57313101
  Tel Diretto 02-57313136
  Be
  open...
  *** Confidentiality Notice & Disclaimer
*
This message, together with any attachments, is for the
confidential
and exclusive use of the addressee(s). If you receive it in
error,
please delete the message and its attachments from your system
immediately and notify us by return e-mail.
Do not disclose, copy, circulate or use any information
contained in
this e-mail.
  

  

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