Re: [Lustre-discuss] e2fsck and related errors during recovering

2011-04-07 Thread Andreas Dilger 
Yes, upgrading to the latest e2fsprogs is generally safe. 

Cheers, Andreas

On 2011-04-06, at 8:18 PM, Larry tsr...@gmail.com wrote:

 Is it helpful updating the e2fsprogs to the newest version? I have
 ever had a problem during e2fsck, after updating the e2fsprogs, it's
 ok.
 
 On Thu, Apr 7, 2011 at 2:29 AM, Andreas Dilger adil...@whamcloud.com wrote:
 Having the actual error messages makes this kind of problem much easier to 
 solve.
 
 At a guess, if the journal was removed by e2fsck you can re-add it with 
 tune2fs -J size=400 /dev/{mdsdev}.
 
 As for lfsck, if you still need to run it, you need to make sure the same 
 version of e2fsprogs is on all OSTs and MDS.
 
 Cheers, Andreas
 
 On 2011-04-06, at 1:26 AM, Werner Dilling dill...@zdv.uni-tuebingen.de 
 wrote:
 
 Hello,
 after a crash of our lustre system (1.6.4) we have problems repairing the 
 filesystem. Running the 1.6.4 e2fsck failed on the mds filesystem so we 
 tried with the latest 1.8 version which succeeded. But trying to mount mds 
 as ldiskfs filesystem failed with the standard error message: bad 
 superblock on 
 We tried to get more info and the file command
 file -s -L /dev/ produced ext2 filesystem instead of ext3 filesystem 
 which we got from all ost-filesystems.
 We were able to produce the mds-database which is needed to get info for 
 lfs fsck. But using this database to create the ost databases failed with 
 the error message: error getting mds_hdr (large number:8) in /tmp/msdb: 
 Cannot allocate memory ..
 So I assume the msdb is in bad shape and my question is how we can proceed. 
 I assume we have to create a correct version of the mds-filesystem and how 
 to do this is unknown. Any help and info is appreciated.
 
 Thanks
 w.dilling
 
 
 
 ___
 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

[Lustre-discuss] e2fsck and related errors during recovering

2011-04-06 Thread Werner Dilling 

Hello,
after a crash of our lustre system (1.6.4) we have problems repairing  
the filesystem. Running the 1.6.4 e2fsck failed on the mds filesystem  
so we tried with the latest 1.8 version which succeeded. But trying to  
mount mds as ldiskfs filesystem failed with the standard error  
message: bad superblock on 

We tried to get more info and the file command
file -s -L /dev/ produced ext2 filesystem instead of ext3  
filesystem which we got from all ost-filesystems.
We were able to produce the mds-database which is needed to get info  
for lfs fsck. But using this database to create the ost databases  
failed with the error message: error getting mds_hdr (large number:8)  
in /tmp/msdb: Cannot allocate memory ..
So I assume the msdb is in bad shape and my question is how we can  
proceed. I assume we have to create a correct version of the  
mds-filesystem and how to do this is unknown. Any help and info is  
appreciated.


Thanks
w.dilling





smime.p7s
Description: S/MIME Signatur
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

Re: [Lustre-discuss] e2fsck and related errors during recovering

2011-04-06 Thread Andreas Dilger 
Having the actual error messages makes this kind of problem much easier to 
solve.

At a guess, if the journal was removed by e2fsck you can re-add it with 
tune2fs -J size=400 /dev/{mdsdev}.

As for lfsck, if you still need to run it, you need to make sure the same 
version of e2fsprogs is on all OSTs and MDS. 

Cheers, Andreas

On 2011-04-06, at 1:26 AM, Werner Dilling dill...@zdv.uni-tuebingen.de wrote:

 Hello,
 after a crash of our lustre system (1.6.4) we have problems repairing the 
 filesystem. Running the 1.6.4 e2fsck failed on the mds filesystem so we tried 
 with the latest 1.8 version which succeeded. But trying to mount mds as 
 ldiskfs filesystem failed with the standard error message: bad superblock on 
 
 We tried to get more info and the file command
 file -s -L /dev/ produced ext2 filesystem instead of ext3 filesystem 
 which we got from all ost-filesystems.
 We were able to produce the mds-database which is needed to get info for lfs 
 fsck. But using this database to create the ost databases failed with the 
 error message: error getting mds_hdr (large number:8) in /tmp/msdb: Cannot 
 allocate memory ..
 So I assume the msdb is in bad shape and my question is how we can proceed. I 
 assume we have to create a correct version of the mds-filesystem and how to 
 do this is unknown. Any help and info is appreciated.
 
 Thanks
 w.dilling
 
 
 
 ___
 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] e2fsck and related errors during recovering

2011-04-06 Thread Larry 
Is it helpful updating the e2fsprogs to the newest version? I have
ever had a problem during e2fsck, after updating the e2fsprogs, it's
ok.

On Thu, Apr 7, 2011 at 2:29 AM, Andreas Dilger adil...@whamcloud.com wrote:
 Having the actual error messages makes this kind of problem much easier to 
 solve.

 At a guess, if the journal was removed by e2fsck you can re-add it with 
 tune2fs -J size=400 /dev/{mdsdev}.

 As for lfsck, if you still need to run it, you need to make sure the same 
 version of e2fsprogs is on all OSTs and MDS.

 Cheers, Andreas

 On 2011-04-06, at 1:26 AM, Werner Dilling dill...@zdv.uni-tuebingen.de 
 wrote:

 Hello,
 after a crash of our lustre system (1.6.4) we have problems repairing the 
 filesystem. Running the 1.6.4 e2fsck failed on the mds filesystem so we 
 tried with the latest 1.8 version which succeeded. But trying to mount mds 
 as ldiskfs filesystem failed with the standard error message: bad superblock 
 on 
 We tried to get more info and the file command
 file -s -L /dev/ produced ext2 filesystem instead of ext3 filesystem 
 which we got from all ost-filesystems.
 We were able to produce the mds-database which is needed to get info for lfs 
 fsck. But using this database to create the ost databases failed with the 
 error message: error getting mds_hdr (large number:8) in /tmp/msdb: Cannot 
 allocate memory ..
 So I assume the msdb is in bad shape and my question is how we can proceed. 
 I assume we have to create a correct version of the mds-filesystem and how 
 to do this is unknown. Any help and info is appreciated.

 Thanks
 w.dilling



 ___
 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