On Dec 13, 3:12 pm, Ludovic Francois <[EMAIL PROTECTED]> wrote: > On Dec 13, 2:59 pm, "Ludovic Francois" <[EMAIL PROTECTED]> wrote: > > > Do you think it's possible someone overwrote the "label" with a tunefs > > command? > > or the system > > > I already saw it with some other file system.
We recreated Target and Index with the tunefs.lustre command: --8<---------------cut here---------------start------------->8--- [EMAIL PROTECTED] ~]# tunefs.lustre --writeconf --index 0 /dev/mpath/mpath0 checking for existing Lustre data: found CONFIGS/mountdata Reading CONFIGS/mountdata Read previous values: Target: lustre-OST0030 Index: 48 Lustre FS: lustre Mount type: ldiskfs Flags: 0x2 (OST ) Persistent mount opts: errors=remount-ro,extents,mballoc Parameters: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] sys.timeout=80 [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] sys.timeout=80 Permanent disk data: Target: lustre-OST0000 Index: 0 Lustre FS: lustre Mount type: ldiskfs Flags: 0x102 (OST writeconf ) Persistent mount opts: errors=remount-ro,extents,mballoc Parameters: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] sys.timeout=80 [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] sys.timeout=80 Writing CONFIGS/mountdata [EMAIL PROTECTED] ~]# --8<---------------cut here---------------end--------------->8--- But now we have some problems to remount the file system, could you confirm us this command just rewrite the index? Best Regards, Ludo -- Ludovic Francois +33 (0)6 14 77 26 93 System Engineer DataDirect Networks _______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
