Re: [Lustre-discuss] OST crash recovery problem

2008-08-26 Thread Heiko Schroeter
Am Dienstag, 26. August 2008 15:35:38 schrieb Jeremy Mann: > Mag Gam wrote: > > LOL... I am in the same situation, I want to see what problems other > > people have so I can try to help them and I can further avoid it. I am > > a big proponent of "your problems are my problems" :-) > > When we firs

Re: [Lustre-discuss] OST crash recovery problem

2008-08-26 Thread Heiko Schroeter
Am Dienstag, 26. August 2008 15:20:01 schrieb Mag Gam: I did respond to the list (and myself) of this unresolved issue and the rerack last week (19.8). Unfortunatly i dont' have time to do more investigations because we moved on to our productive system and i had to get things going. And _this_

Re: [Lustre-discuss] OST crash recovery problem

2008-08-26 Thread Jeremy Mann
Mag Gam wrote: > LOL... I am in the same situation, I want to see what problems other > people have so I can try to help them and I can further avoid it. I am > a big proponent of "your problems are my problems" :-) When we first implemented Lustre, I had several learning curves with OSTs going d

Re: [Lustre-discuss] OST crash recovery problem

2008-08-26 Thread Mag Gam
LOL... I am in the same situation, I want to see what problems other people have so I can try to help them and I can further avoid it. I am a big proponent of "your problems are my problems" :-) On Tue, Aug 26, 2008 at 9:03 AM, Heiko Schroeter <[EMAIL PROTECTED]> wrote: > > Since the new setup e

Re: [Lustre-discuss] OST crash recovery problem

2008-08-26 Thread Heiko Schroeter
Since the new setup everything is running fine. Why ? Except my backbone, which keeps on etching when something is not quite figured out ;-) When this sort of breakdown happens again i do have a blank undersigned 'Blitz Holliday' form ready in my desk Seriously, i also would like to kno

Re: [Lustre-discuss] OST crash recovery problem

2008-08-26 Thread Mag Gam
Darn, We are curious what happened now. On Mon, Aug 25, 2008 at 9:35 AM, Heiko Schroeter <[EMAIL PROTECTED]> wrote: > Am Montag, 25. August 2008 13:54:46 schrieb Johann Lombardi: > > Sorry, the system had to be setup from scratch as we couldn't find a solution. > This has already happen. > > The m

Re: [Lustre-discuss] OST crash recovery problem

2008-08-25 Thread Heiko Schroeter
Am Montag, 25. August 2008 13:54:46 schrieb Johann Lombardi: Sorry, the system had to be setup from scratch as we couldn't find a solution. This has already happen. The mounts were done manually. Unfortunatly i did not memorize exactly the output of 'lctl dl'. Thanks anyway for your effort. Reg

Re: [Lustre-discuss] OST crash recovery problem

2008-08-25 Thread Johann Lombardi
On Thu, Aug 14, 2008 at 08:40:05AM +0200, Heiko Schroeter wrote: > What needs to be done in such a case ? > I tried to move the mountpoint because of the "file exists" message but that > does not help. > > Aug 13 11:18:54 sadosrd20 LustreError: 7247:0:(genops.c:246:class_newdev()) > Device scia-

[Lustre-discuss] OST crash recovery problem

2008-08-19 Thread Heiko Schroeter
Hello, Replying to myself. No we couldn't get lustre up again and had to reinstall from scratch. :-( Keeping fingers crossed now we are running the productive system What bugs us is this part of the message on the MDS: Aug 13 11:18:54 sadosrd20 LustreError: 15c-8: [EMAIL PROTECTED]: The c

[Lustre-discuss] OST crash recovery problem

2008-08-13 Thread Heiko Schroeter
Hello again, any idea what can be done in such a case ? Regards Heiko Hello, after a crash (hardware failure) of an OST with two lustre partitions one partition (/dev/sdb) cannot be remounted after restart. The second (/dev/sdc) partition mounts fine. What needs to be done in such a case ? I

[Lustre-discuss] OST crash recovery problem

2008-08-13 Thread Heiko Schroeter
Hello, after a crash (hardware failure) of an OST with two lustre partitions one partition (/dev/sdb) cannot be remounted after restart. The second (/dev/sdc) partition mounts fine. What needs to be done in such a case ? I tried to move the mountpoint because of the "file exists" message but tha