On Tuesday 26 June 2007 17:59:49 you wrote: > > I still do not understand why tunefs.lustre couldn't detect the indices > > itslf. The filesystems have been created with tools from lustre-1.4.9 and > > with kernel modules from lustre-1.4.10. > > Did you get the message "ost with unknown index" at the first tunefs? > The logic for all this is in mkfs_lustre.c read_local_files(). It > should be able to identify the > ost index from the last_rcvd files created in Lustre 1.4.6 on. A reason
I just looked into the sources myself and found the problem. Well, not really a problem of the code, but my ignorance. I only installed e2fsck.static-cfs to be able to run filesystem checks, but otherwise kept the ubuntu-default e2fsprogs. Looking into read_local_files() I see that debugfs is used to dump the last_rcvd file. Using debugs of ubuntus e2fsprogs a last_rcvd file is created which seems to consist of zeros and random data (first many many zeros and then something I can't identify). After installing e2fsprogs-cfs I could update OST2 properly to lustre-1.6 and also properly connect it to the MDS. And now a big warning: Even though tune2fs.lustre failed on OST1, it seems to have modified the filesystem. As on OST2 I could convert it to lustre-1.6 with the proper tools, but when I tried to mount it, it failed and in dmesg I got these messsages [ 2521.326416] LDISKFS-fs error (device md3): ldiskfs_add_entry: bad entry in directory #75022340: rec_len % 4 != 0 - offset=0, inode=537537071, rec_len=2346, name_len=102 [ 2521.341692] Aborting journal on device md3. [ 2521.346044] Remounting filesystem read-only I already got this when I converted last time, but thought the filesystem might have been damaged before. May suggest to add to tunefs.lustre some tests if the proper e2fsprogs have been installed? Thanks, Bernd -- Bernd Schubert Q-Leap Networks GmbH _______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
