The main issue is that tune2fs changing the superblock while the journal is not
recovered means any changes will be lost. It is hard to get this 100% correct,
since it is possible to set some tunable on the mounted superblock, and
replaying the journal in that case would be bad.
Running ''e2fsck /dev/xxxx'' (no options) should be enough to
replay the journal, without doing a full filesystem scan.
Cheers, Andreas
On 2010-08-16, at 11:20, David Noriega <tsk133 at my.utsa.edu> wrote:
> Still very new to lustre, and now I''m going over the failover
part. I
> use tune2fs to set MMP, but I would get this warning about
> needs_recovery, do a journal replay or else the setting will be lost.
> With dumpe2fs I could see the needs_recovery flag was set on all of
> the OST/MDT. Reading over the recovery part, nothing really matching
> what was going on here, I elected to use e2fsck -fn then e2fsck -fp on
> all of the OST/MDT, now the needs_recovery flag is gone and I was able
> to set MMP to on. So my question is, what did I do to get this sort
> of thing to happen? And how to avoid it?
>
> David
>
> --
> Personally, I liked the university. They gave us money and facilities,
> we didn''t have to produce anything! You''ve never been out
of college!
> You don''t know what it''s like out there! I''ve
worked in the private
> sector. They expect results. -Ray Ghostbusters
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss