On Tuesday 26 June 2007 17:59:49 Nathaniel Rutman wrote: > Bernd Schubert wrote: > > On Monday 25 June 2007 20:15:09 Nathaniel Rutman wrote: > >> Bernd Schubert 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 > it might not is if the last_rcvd > file was originally created in an earlier version of Lustre and upgraded > to 1.4.6+. If you could send me the original > last_rcvd, I'd be glad to take a look -- too bad I told you to erase it > before :(
No problem, these are only test and development systems, so its easy to
reproduce from scratch.
[EMAIL PROTECTED]:~# tunefs.lustre --ost [EMAIL PROTECTED] /dev/md3
checking for existing Lustre data: found last_rcvd
tunefs.lustre: Unable to read /tmp/diraaRDyB/mountdata (No such file or
directory).
Trying last_rcvd
Reading last_rcvd
Feature compat=0, incompat=0
OST with unknown index
Read previous values:
Target:
Index: unassigned
Lustre FS: lustre
Mount type: ldiskfs
Flags: 0x212
(OST needs_index upgrade1.4 )
Persistent mount opts:
Parameters:
tunefs.lustre FATAL: Can't find the target index, specify with --index
tunefs.lustre: exiting with 22 (Invalid argument)
I've attached the last_rcvd file from ost1.
Cheers,
Bernd
--
Bernd Schubert
Q-Leap Networks GmbH
last_rcvd
Description: Binary data
_______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
