Please don't reply to lustre-devel. Instead, comment in Bugzilla by using the following link: https://bugzilla.lustre.org/show_bug.cgi?id=11520
(In reply to comment #18) > Ruth, have you had a chance to fix up the LAST_ID value for this OST (per the > process in lustre-discuss)? This can be completed on the order of 20-30 > minutes, and I would hate to find out that your system has been down for > additional days for something that should only take a short time to fix. I'd > be > happy to assist you via phone or IRC if there are any questions about the > process or interpreting the state of the filesystem. Another fix attempt is scheduled for tomorrow. I realize that fixing last_id is a short effort, but they aren't confident that this is the only thing wrong with that OST and their plan is to reformat it. If anything changes I'll let you know. The information about how to edit last_id was unfortunately about a day late, after the file system was already being used read only for users to copy data off. Thanks for the offer. Ruth _______________________________________________ Lustre-devel mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-devel
